I'm experimenting and I want to know if rebinding an EJB3's JNDI location a bad thing?
I want to manage my EJB3 proactively and one of the issues is JNDI namespace collisions (foreign deployments interacting with my stuff that have similar names). I have some code that rebinds a STSB EJB3's JNDI location. That works, but unfortunately the bean never gets removed from JNDI during undeployment (I will guess its because I changed it underneath at @PostConstruct time). I initially tried to use the @PreDestroy lifecycle callback but that won't work either. since apparently STSBs never get destroyed during runtime. Am I just barking up the wrong tree here? I would rather proactively manage namespace than rely on @RemoteBinding/LocalBinding annotations. -aps View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3930822#3930822 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3930822 ------------------------------------------------------- This SF.Net email is sponsored by xPML, a groundbreaking scripting language that extends applications into web and mobile media. Attend the live webcast and join the prime developer group breaking into this new coding territory! http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642 _______________________________________________ JBoss-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/jboss-user
