"bstansberry(a)jboss.com" wrote : The HAPartition bean is just doing this in stopService(): | | ctx = new InitialContext(); | ctx.unbind(boundName); | | In startService() it's more complicated, but essentially creates a new default InitialContext and does a rebind. So, no accessing a different dependency in stopService(). | | The bean has a depends on jboss:service=NamingService. | | ( BTW, maybe we should have a notion of implicit services applied to multiple inner-services i.e. a wrapping tag applied to multiple inner-service definitions so that it would be possible to assign global "services" (or default services) en masse. Things like the naming service for example, while a singleton today, might not be a a singleton anymore tomorrow (if we want to make JBoss AS 5.x a "multi-tenant" implementation i.e. SaaS hosting infrastructure for example). ) View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4124048#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...