Hi Carlo, I think the main question for you is: Do you want just remoting inside one application (client and server are inside the same release unit), or do you want to offer services to another application?
If you want simple remoting then you can directly expose your business objects. In this case you can use any of the named technologies. Often you will use code first here as it is less work to do. Many people use service facades even in this case as not all of your object graphs can be easily transported through all transports. If you want to offer services then you should go contract first and use a service facade. In this case you define a stable representation of some of the business objects for the service. These will often be pure data transfer objects as these can be easily transported. You will also want to avoid complex object graphs and instead rather use trees. For this case the typical technology would be JAX-WS/JAXB with code generation from a wsdl which will be your service contract. Greetings Christian Christian Schneider Team Handel und Risikomanagement Informationsverarbeitung Business Solutions Trading EnBW Systeme Infrastruktur Support GmbH Informationsverarbeitung Business Solutions Handel und Dispatching Durlacher Allee 93 76131 Karlsruhe Tel : +49-(0)721-63-15482 Mail: christian.schnei...@enbw.com Sitz der Gesellschaft: Karlsruhe Handelsregister: Amtsgericht Mannheim HRB 108550 Vorsitzender des Aufsichtsrats: Dr. Bernhard Beck Geschäftsführer: Jochen Adenau, Dr. Peter Krampf -----Ursprüngliche Nachricht----- Von: James Strachan [mailto:james.strac...@gmail.com] Gesendet: Dienstag, 10. November 2009 15:19 An: users@camel.apache.org Betreff: Re: Question On Using Spring Remoting Against Camel Remoting Its either Spring remoting - or go JAXWS or REST I'd say. They've all got strengths and weaknesses. If you want WSDLs / XSDS and stuff, then maybe JAXWS is a simpler approach? -- James ------- http://macstrac.blogspot.com/ Open Source Integration http://fusesource.com/
