Actually implementing this, there is no need for a Colocation object. This object already exists in the form of org.jboss.system.Registry (it should needs adding to the client jar where it will be empty on a client).
Also, looking at org.jboss.proxy.ejb.ProxyFactory This looks wrong. It creates and binds the proxy in start(), but doesn't remove it until destroy(). I can see circumstances where it or a subclass/dependency needs some service that is no longer there. Anything in done start() should be reversed in stop()! View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3859351#3859351 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3859351 ------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://productguide.itmanagersjournal.com/ _______________________________________________ JBoss-Development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
