> The > invocation protocol for all stateless session beans should be > defined at a container related level, not a particular
Negative, detached invokers. In the future you will configure your client at the JMX level. Saying "for this client give me this interface, this stack of client interceptors and this invoker and bind the result under this JNDI name" is JBoss4.0. In the case of EJBs this is what the container factory does. Therefore the invocation protocol is purely a client issue, the container doesn't care. The fact that we used to put the invocation protocol in the container stack was just a limitation of the 2.x design. > instance of a session bean. Right now we have functionally > related items defined in very different and it makes > describing the config logic somewhat confusing. Really there > is a fair amount of wacked shit in our dtds that needs to be > normalized and cleaned up. I will agree with the "confusing". What do you propose? Did you see the XSLT proposal from David? We should take a whack at it. Marcf ------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf _______________________________________________ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
