On Wed, Jun 3, 2009 at 10:32 AM, Christopher L Merrill <[email protected]> wrote: > It's a question we've wrestled with as well. It seemed remarkably > inefficient to do XML encoding/decoding to move data from one part of > the appserver to another. It seemed to make more sense to let the > web UI skip past that and go straight to the business logic. >
Yes, the web UI should skip it definitely and just talk directly to the service objects. But, I'm talking about the client application. Is there any particular reason that you want to use XML-based communication if you have an all-Java architecture going on? Wouldn't it be easy to XMLize the services you're exposing remotely later if a different type of client would want to connect to it? I'd say just use Spring remoting (if you're using Spring). --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
