You shouldn't care: if you know JMS, you know enough. Behind the scenes, a servlet on each jboss (the server), is present.
The client uses a special InitialContext. When you lookup something in that context, the client jboss code marshalls the lookup name into a http request and sends it to the servlet on the jboss machine. The servlet decodes this, and understands "aha somemone looks for object x". It then looks in it's real jndi for that object, and it returns (in the http respone) something like "okay, i have this object, it has this interface" if it's there. The jboss client code receives the okay, and makes a proxy, that implements this interface. Next, your app code calls some method on that proxy. That proxy also marshalls this method invocation into a http request, and sends it to the servlet. The servlet receives that request and understands "aha someone wants to call method y on jndi-object z". It invokes that method on the real object z, and marshalls the return value into the http response. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3869330#3869330 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3869330 ------------------------------------------------------- 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-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/jboss-user
