Handling xpath deletion event[fireXpathEvent(XpathEvent xpathEvent)]
to remove the child DConfigBean. We need to handle this event as we
are not getting the call *removeDConfigBean()* for removed beans.

File Modified: EjbJarRoot.java  revision: 1.33

Move issues from temprorary component.

[Build 20041124]

This fix is causing a BeanNotFoundException on delete (see below).  After a
discussion with Peter, it seems the problem is that now the j2eeserver problem
this worked around is fixed, so removeDConfigBean is being called twice.

javax.enterprise.deploy.spi.exceptions.BeanNotFoundException: No match for bean
at 'org.netbeans.modules.j2ee.deployment.config.StandardDDImpl@1b22cc7', xpath =
'/ejb-jar/enterprise-beans/entity'.
	at
org.netbeans.modules.j2ee.sun.share.configBean.Base.removeDConfigBean(Base.java:476)
	at
org.netbeans.modules.j2ee.sun.share.configBean.EjbJarRoot.removeDConfigBean(EjbJarRoot.java:319)
[catch] at
org.netbeans.modules.j2ee.deployment.config.ConfigBeanStorage.remove(ConfigBeanStorage.java:89)
	at
org.netbeans.modules.j2ee.deployment.config.ConfigBeanStorage.removeChild(ConfigBeanStorage.java:178)
	at
org.netbeans.modules.j2ee.deployment.config.ConfigBeanStorage.fireEvent(ConfigBeanStorage.java:141)
	at
org.netbeans.modules.j2ee.deployment.config.DDCommon.fireEvent(DDCommon.java:231)
	at
org.netbeans.modules.j2ee.deployment.config.DDCommon.fireEvent(DDCommon.java:238)
....

I will look at it...  I have some recent changes/experience in the dcb tree...

The removeDConfigBean method is now being called twice, once directly from the
j2eeserver (this call can be seen in the stack trace above) and second time from
the EjbJarRoot.fireXpathEvent - this call should be removed.

Vince - I already emailed Rajeshwar about this one so make sure you sync up with
him if you do anything.  There is nothing to explore really, the original "fix"
for this problem needs to be removed because it isn't correct and no longer
applies.  The real problem has been fixed.

I tried deleting the whole listener to test if the issue really was resolved.  I
still ended up with the ejb in the sun-ejb-jar.xml....  Should we just remove
the call to removeDConfigBean from the listener but keep the rest, or transfer
the "extra" stuff in the listener into the removeDConfigBean impl?

If you mean the xpath listener, please do not delete the whole thing, as that is
where the implementation of the fix for issue 54867 is.

Commented out the call to removeDConfigBean() that was in the listener.  This seeems to be doing the 
right thing.  Ludo has updated the scrambled NBM already.

build 20050706