In the case of the UnifiedInvoker, this is a layer on top of remoting that wants to introduce a serialization configuration. This has to come in pairs. Introduction of an extension of the remoting framework on the server side needs to have a component on the client side which propgates this configuration information. If the service locator maps to a proxy bound into jndi then the marshaller info should be bound to the proxy. If the service locator maps to some registry, then the registry should hold the marshaller information. As John mentions, one type of base marshaller directly supported by the remoting framework could be one with an embedded registry that include a header packet which the client uses on the initial connection to obtain the application specific marshaller.
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3864127#3864127 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3864127 ------------------------------------------------------- This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting Tool for open source databases. Create drag-&-drop reports. Save time by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc. Download a FREE copy at http://www.intelliview.com/go/osdn_nl _______________________________________________ JBoss-Development mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/jboss-development
