I have come up with two solutions for this. This first one is to provide datatype, marshaller, and unmarshaller as parameters to the locator url. The datatype is whatever name want to associate the custom marshaller/unmarshaller under. The values for marshaller/unmarshaller parameters is the fully qualified class name for the custom classes. They will then be dynamically loaded if exist on the classpath (of course requires that they do exist on both the client and the server). This has already been implemented and checked into CVS HEAD for jboss-head.
The second is to provide a port via the locator url which will signify the port on which the marshalling service will reside. This will be using the plain, default marshaller to load custom marshallers. This has not been implemented yet (but about to start on it). View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3865719#3865719 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3865719 ------------------------------------------------------- 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
