The second param in the Client's method public Object invoke(Object param, Map metadata)
can server two purposes. The first is to provide transport specific information. For example, the client may wish to provide HTTP headers in their request (or even specify if should be a GET or a POST). org.jboss.remoting.transport.http.HTTPInvokerClientTestCase shows an example of this. The second is to pass along extra data to the invocation handler on the server side. This is unbounded, so can be anything (similar to the handback object passed when registering a NotificationListener in JMX). The first param is the one that matters as it provides the actual payload data; meaning this is what you want passed as the main invocation data. There are few different types of Invocations you use; one of which is the org.jboss.remoting.invocation.NameBasedInvocation, which provides the method name, parameters, and their types (just like when making a JMX invocation). View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3860381#3860381 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3860381 ------------------------------------------------------- The SF.Net email is sponsored by: Beat the post-holiday blues Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek. It's fun and FREE -- well, almost....http://www.thinkgeek.com/sfshirt _______________________________________________ JBoss-Development mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/jboss-development
