3 Replies Latest reply on Apr 5, 2006 3:01 PM by bdecoste

Why aren't EJB3 Naming Contexts removed after undeployment?

asack Apr 4, 2006 4:46 PM

Question says it all. Currently I have a bunch of STSBs all with a @Stateless ( name = "blah" ) which generates a blah/local in my JNDI namespace. When I undeploy the jar file, the NamingContext is still bound. Why is this?

1. Re: Why aren't EJB3 Naming Contexts removed after undeployme

bdecoste Apr 5, 2006 11:04 AM (in response to asack)

The NamingContext should no longer be bound. I have opened a JIRA task for this issue.

http://jira.jboss.com/jira/browse/EJBTHREE-507
Actions
2. Re: Why aren't EJB3 Naming Contexts removed after undeployme

asack Apr 5, 2006 1:58 PM (in response to asack)

"bdecoste" wrote:
The NamingContext should no longer be bound. I have opened a JIRA task for this issue.

http://jira.jboss.com/jira/browse/EJBTHREE-507

Thank you...I have a follow question....regarding JNDI bindings...
Actions
3. Re: Why aren't EJB3 Naming Contexts removed after undeployme

bdecoste Apr 5, 2006 3:01 PM (in response to asack)

What's your follow on question?
Actions

Go to original post