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 39197 - j2eeserver module is not calling removeDConfigBean when beans need to be destroyed.
Summary: j2eeserver module is not calling removeDConfigBean when beans need to be dest...
Status: RESOLVED FIXED
Alias: None
Product: serverplugins
Classification: Unclassified
Component: Infrastructure (show other bugs)
Version: 3.x
Hardware: PC Windows XP
: P2 blocker (vote)
Assignee: Nam Nguyen
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2004-01-24 03:15 UTC by _ pcw
Modified: 2006-06-05 00:39 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description _ pcw 2004-01-24 03:15:34 UTC
Steps:

0. run IDE w/ console window showing (runide.exe)
1. Create a web module and add a servlet.
2. Display the configuration editor (depending on
status of 39196 and when you open the editor, the
servlet may or may not be displayed.  if it is
not, you can restart the ide and it will be.)
3. Now delete the servlet.
4. In the console, there will messages showing
that a XpathEvent.BEAN_REMOVED event was sent but
the api 'DConfigBean.removeDConfigBean()' was not
called to remove it.
5. Also, the DConfigBean will not be removed from
the visible configuration tree in the editor.
Comment 1 Nam Nguyen 2004-01-26 05:26:46 UTC
Agreed that since the tree structure is controlled by tool, its tools
responsibility to handle add/delete child beans.  The code to remove
child config bean is in place but there is a bug causing remove not
triggered and I will fix it soon.
Comment 2 Nam Nguyen 2004-01-26 20:53:59 UTC
Fixed.  J2eeserver now calling DConfigBean.removeDConfigBean, which
will generate a BeanNotFoundException which I believe because S1AS
plugin already removed it in Peter's work-around.