[jboss-dev-forums] [Design of POJO Server] - Re: Implicit container dependencies

[weston.price@jboss.com]

Feasibly those admin objects that are hosted remotely should be bound into our local JNDI tree with a proxy/wrapper for the remote admin object. 

The generic jms project is a good example of this integration approach.

Note, this is effectively what the JmsJNDIProvider does today, or at least it can do. What we do in the case of a remote destination is bind to JNDI tree of the remote resource directly, or we force some sort of bridge layer (ie the WASMQ integration stuff on the Wiki). 

While this works, it effectively removes any dependency control we might have until the actual point of activation where we attempt the lookup on the destination. 



View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4032436#4032436

Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4032436