_blackjack wrote:No a Service Oriented Architecture is what you are looking for. What technology to use to expose the webservices is entirely up to you; if you like JAX-WS webservices go right ahead, you could also look into JAX-RS. What I wouldn't do is go for remote EJBs as that requires you to bundle a whole mess of (server specific) libraries with your client application just to be able to make it work.
I'm thinking about to create a service layer with EJBs and expose some operations as webservices. Thus, I'll be able to request for those objects in DB and receive them as xml. So, mapping the response to Value Objects (VOs) would be enough in web front application. In the case of request to services, i'd invoke the webservices and pass the VOs as input parameters. I won't have the same annotated POJOs at web client, however, i don't see this as a big issue. Am I right?
Is there another way to achieve the same result in an easier of more appropriate approach?