activemq-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Eugeny N Dzhurinsky <>
Subject Re: distributing legacy code using JMS
Date Thu, 28 Aug 2008 11:53:01 GMT
On Thu, Aug 28, 2008 at 11:29:02AM +0100, James Strachan wrote:
> 2008/8/28 Eugeny N Dzhurinsky <>:
> The tricky bit is ensuring that the on-the-wire message formats
> correctly match up to the legacy application. There's a number of
> solutions out there in general for doing this kind of thing - such as
> JAX-WS via say CXF using Web Services with SOAP/XML encoding.
> For more custom coding of messages to Java objects you might wanna
> experiment with the Spring Remoting support with Camel
> If you control both ends of the wire, Camel supports trivial remoting
> of any Java interface/class; however if the back end is some legacy
> system you might want to plugin your own Message Translator so perform
> whatever custom encodings your legacy application expects - as there
> are many different ways to encode method invocations into
> messages/destinations/headers and payloads.

Actually I am controlling the both ends of the system, so looks like it is
worth to try out Camel - it probably can save me a lot of time.

Thank you!

Eugene N Dzhurinsky

View raw message