Thanks A Lot For The Answer I think this would be a good option so that I could hide implementation details in the future
http://camel.apache.org/hiding-middleware.html >>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? Actually the reason why i went with remoting rather than going with jaxws is all my beans will actually be remotely called. it is somehow more transparent on the developer's part that he is actually calling a bean outside, if i go the jaxws way, i would have to generate different artifacts and stuff it would take mostly spring configuration to actually change the behavior of the beans. i'm using wicket as a front end and the beans are mapped automatically through annotations. However if I use the jms version, then i would be able to get the benefits of having brokers as well. i'm looking at other advantages. I think camel would provide me a lot that's why i'm considering it more having used it a lot before
