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 67627 - Config editor does not properly switch stateless and stateful session bean types when sent corresponding event.
Summary: Config editor does not properly switch stateless and stateful session bean ty...
Status: RESOLVED FIXED
Alias: None
Product: serverplugins
Classification: Unclassified
Component: Sun Appserver 8 (show other bugs)
Version: 5.x
Hardware: All All
: P3 blocker (vote)
Assignee: _ pcw
URL:
Keywords:
Depends on: 95131
Blocks:
  Show dependency tree
 
Reported: 2005-10-26 23:46 UTC by _ pcw
Modified: 2007-07-20 21:18 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 _ pcw 2005-10-26 23:46:49 UTC 
Create an ejb module with a stateful session bean.
open the multiview editor for ejb-jar.xml and note that you can change the type
of the bean from stateful to stateless (and back of course).

If you open the config editor on sun-ejb-jar.xml though, then go back to
ejb-jar.xml and make this change (stateful -> stateless), the config editor will
reflect the change.  Ditto for CMP -> BMP entity beans (or vice versa).

A workaround should be to close the config editor, open sun-ejb-jar.xml as text,
add, then remove a space somewhere and save it, then reopen the configuration
editor.
Comment 1 _ pcw 2005-10-26 23:50:57 UTC 
The reason for this is that the plugin implemented stateful vs. stateless
session beans (and CMP vs. BMP entity beans) as separate classes rather than
aspects of the same class.

However in ejb-jar.xml, the distinction between each pair is a child DDBean of
.../session or .../entity in ejb-jar.xml, thus one can switch between the
members of each pair with the corresponding DConfigBean bound to the EJB only
receiving a DDBean change event.  In our implementation, we would have to
destroy and recreate a new DConfigBean which cannot be done with existing JSR-88
API.  This will require a DConfigBean architecture refactoring to fix (not as
difficult as that sounds) but should cause NO visible changes (e.g. UI).
Comment 2 _ pcw 2005-12-13 07:29:09 UTC 
This is too complex to fix during hard code freeze.  The workaround is to make
the changes to ejb-jar.xml, as described (ignoring the exceptions), then block
select the text for the entire ejb in ejb-jar.xml, cut it as one action, then
paste it back.  This should cause the appserver plugin to create the correct
DConfigBean for the ejb with it's new setting.

As far as I know, no customer has ever tried to change an ejb this way anyway.
Comment 3 Vince Kraemer 2007-02-10 02:17:59 UTC 
link related issues
Comment 4 Vince Kraemer 2007-05-15 17:53:06 UTC 
tm change
Comment 5 _ pcw 2007-07-20 21:18:44 UTC 
Fixed by virtue of new editor design.