If you need to maintain the hierarchy on the client side, I don's see a problem with that. Until now I didn't need it, but close() is a good use case for it.
The easiest way to do is with another interceptor. FactoryInterceptor would be a misnomer in the current situation, since the delegates are not constructed by it, but come from server. Actually, there is a FactoryInterceptor in the Session's interceptor stack, which only creates Messages so far. The first name that comes to mind is HierarchyInterceptor, but's got to be a better one ... anonymous wrote : In the new JBoss messaging, the client side interceptor stack is created on the server side and sent back to the client so the approach of maintaining the hierarchy on the server side won't seem to work (and also is more stuff to shift across the network), since each call to createSessionDelegate would end up with it's own copy of it's parent JMSInvocationHandler being sent back. I don't exactly understand what are you trying to say here. JMSInvocationHandler being sent back? Why? There is a hierarchy of ServerDelegates on the server. It is not useful for the close logic, since the closing valve must be on the client. About reusing code: just do it. Mention the original author in the header. About Eclipse: I don't use it. Maybe Adrian can help you here? View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3872671#3872671 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3872671 ------------------------------------------------------- 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://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click _______________________________________________ JBoss-Development mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/jboss-development
