This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.

Bug 64008 - Resource rename function does not really change the resource name
Summary: Resource rename function does not really change the resource name
Status: RESOLVED WONTFIX
Alias: None
Product: serverplugins
Classification: Unclassified
Component: Sun Appserver 8 (show other bugs)
Version: 5.x
Hardware: All All
: P3 blocker (vote)
Assignee: Nitya Doraisamy
URL:
Keywords:
Depends on: 95140
Blocks:
  Show dependency tree
 
Reported: 2005-09-09 21:13 UTC by judytang
Modified: 2007-06-22 12:24 UTC (History)
1 user (show)

See Also:
Issue Type: DEFECT
Exception Reporter:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description judytang 2005-09-09 21:13:19 UTC 
I am using NetBeans 5 (8/10) build, and Appserver 8.1 PE UR2 for testing.

Steps to recreate:

(1) Create a project
(2) At EJB module node, click on Server Resources node -> New -> File ->
Sun Resources - > JDBC Resources
(3) Create JDBC resources select create new JDBC connection pool option,
it creats JDBC resource and pool. 
(4) click on JDBC resource -> rename -> rename the jdbc resource node
(5) click on JDBC resource -> properties -> the JNDI name is not changed

Same issue exists for the connection pool.

I wonder if the rename means to change the JNDI name or not ?

As a user I feel it should that is why I open this issure, so it can be
looked into again.
Comment 1 judytang 2005-09-09 21:36:22 UTC 
Would like to add, I used the test spec which was used in the previous release,
it says after rename the resource, register it again, it should work.

But when I tried the same thing, since the JNDI name did not get change during
the rename, I got error message saying the resource is already there.
Comment 2 Vince Kraemer 2005-09-28 21:43:35 UTC 
May be flaw in test spec.  In 3.6 (which is the release that the spec applies
to), the resources were not exposed files. [The user did not create them in the
scope of a project's source]

This changed in 4.0, but the spec may need to be updated to reflect these changes.
Comment 3 Jaroslav Pospisil 2006-03-13 13:49:37 UTC 
TM 5.0->TBD
Comment 4 Nitya Doraisamy 2006-08-29 06:24:33 UTC 
Will be part of resource wizard rewrite in future
Comment 5 Vince Kraemer 2007-02-10 02:04:17 UTC 
this is will be closed by the work in 95140. link the two together
Comment 6 Vince Kraemer 2007-05-15 17:50:00 UTC 
so the tm for this issue is 6.0?
Comment 7 Nitya Doraisamy 2007-06-22 12:20:42 UTC 
Update to the server resource creation strategy now results in a sun-resources.xml

Rename is not supported
Comment 8 Nitya Doraisamy 2007-06-22 12:22:43 UTC 
Needs to be marked as WONTFIX as functionality is no longer applicable
Comment 9 Nitya Doraisamy 2007-06-22 12:24:31 UTC 
Rename no longer supported