As I was getting geared up to implement this I realized that there is yet another issue with doing it this way. The problem is that the marshaller is the closest thing to the wire. Therefore, if someone implements a custom UnMarshaller (since it is just an interface), there is no way to ensure that they unmarshall the request for a marshaller correctly.
The only way this would work would be to force people to extend a base unmarshaller that I supply, which would intercept the 'I need XXX marshaller/unmarshaller' requests. Although this is not terrible, I wonder if this is partical? Guess AOP can come to the rescue here? Is it acceptable to use AOP for remoting (since AOP depends on remoting)? View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3864494#3864494 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3864494 ------------------------------------------------------- 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
