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 57848 - Deletion of resource-ref in ejb-jar.xml not propagated to sun-ejb-jar.xml
Summary: Deletion of resource-ref in ejb-jar.xml not propagated to sun-ejb-jar.xml
Status: RESOLVED WONTFIX
Alias: None
Product: serverplugins
Classification: Unclassified
Component: Sun Appserver 8 (show other bugs)
Version: 5.x
Hardware: All Linux
: P4 blocker (vote)
Assignee: _ pcw
URL:
Keywords:
Depends on:
Blocks: 57684
  Show dependency tree
 
Reported: 2005-04-13 17:41 UTC by Sherold Dev
Modified: 2007-09-17 21:54 UTC (History)
0 users

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 Sherold Dev 2005-04-13 17:41:55 UTC 
If you add resource-ref to ejb-jar.xml the resource-ref will be added to 
sun-ejb-jar.xml as well. However, if you remove the resource-ref from the
ejb-jar.xml the resource-ref will NOT be removed from sun-ejb-jar.xml. The
problem is visible only if the sun-ejb-jar.xml is opened in the text xml editor.

The respective DConfig bean is removed properly, but because of the j2eeserver
does not get event of that change (BaseEjb.RESOURCE_REF_LIST_CHANGED) it does
not know that these changes are needed to be saved.

See issue 57684.
Comment 1 _ pcw 2005-12-06 16:42:55 UTC 
This issue as written is fixed.

There is a related edge case remaining which is somewhat more difficult to
describe but has to do with adding and removing, then adding again the
resource-ref under certain circumstances.  I am working on fixing this remaining
case.  It is related to the way the implementation initialized default
properties of configuration entries.
Comment 2 _ pcw 2005-12-06 20:05:19 UTC 
The edge case that remains is this:

1. Create ejb module with session bean that has resource-ref.
2. Open sun-ejb-jar gui editor  and enter a value for default-resource-principal
for the resource ref.  Save and close.
3. Open ejb-jar.xml and sun-ejb-jar.xml as text.  Easier to see this if you
split them so you can view both editors at the same time.
4. Block select the entire resource-ref in ejb-jar.xml and delete it.  You will
see the corresponding resource-ref disappear from sun-ejb-jar.xml.
5. Now <undo> the delete action.  The resource-ref will reappear in ejb-jar.xml
but will not reappear in sun-ejb-jar.xml.
Comment 3 _ pcw 2005-12-13 07:24:05 UTC 
The remaining edgecase is pretty esoteric so I don't think this issue warrants a
fix-in-50 tag anymore.  I'm removing the tag and deferring fixing the final edge
case til the next version because we're in hard code freeze now.  If anyone
disagrees, feel free to upgrade to P2 w/ justification.
Comment 4 _ ludo 2006-06-06 22:47:36 UTC 
P4: too esoteric use case. Good for QE!
Comment 5 Jiri Prox 2007-09-17 21:36:19 UTC 
Obsolete milestone, please reevaluate
Comment 6 _ pcw 2007-09-17 21:54:11 UTC 
I don't think this issue applies to the NB6 config editor rewrite.  Closing as WONTFIX.