Lo all, I have been Googling for ages but can't find the right answer so thought I would post my problem on here:
1) I deploy an EAR File (Deploys ok)
2) In the Global JNDI Namespace it shows:
+- Deploy (class: org.jnp.interfaces.NamingContext)
| +- A (class: org.jnp.interfaces.NamingContext)
| | +- b (proxy: $Proxy66 implements interface com.erudine.jmx.IBehaviourEngine,interface org.jboss.ejb3.JBossProxy)
3) Delete the EAR File (JBoss console shows 'Undeployed.... ~.ear)
4) In the Global JNDI Namespace it shows:
+- Deploy (class: org.jnp.interfaces.NamingContext)
| +- A (class: org.jnp.interfaces.NamingContext)
How come it is still in the JNDI Namespace when it has undeployed?
Does anyone know how I can get it removed from here? As it is causing me re-deployment problems.
Thanks guys
P.S I found this bug but it is closed, http://jira.jboss.com/jira/browse/EJBTHREE-507?page=all
1) I deploy an EAR File (Deploys ok)
2) In the Global JNDI Namespace it shows:
+- Deploy (class: org.jnp.interfaces.NamingContext)
| +- A (class: org.jnp.interfaces.NamingContext)
| | +- b (proxy: $Proxy66 implements interface com.erudine.jmx.IBehaviourEngine,interface org.jboss.ejb3.JBossProxy)
3) Delete the EAR File (JBoss console shows 'Undeployed.... ~.ear)
4) In the Global JNDI Namespace it shows:
+- Deploy (class: org.jnp.interfaces.NamingContext)
| +- A (class: org.jnp.interfaces.NamingContext)
How come it is still in the JNDI Namespace when it has undeployed?
Does anyone know how I can get it removed from here? As it is causing me re-deployment problems.
Thanks guys

P.S I found this bug but it is closed, http://jira.jboss.com/jira/browse/EJBTHREE-507?page=all