Robert, My application has an existing domain/service layer that does not map 1:1 with the entities that will be used on the wire. My process thus far has been to create a schema for the web service input/output and generate the java objects that map to them. What I am left with is still two different object models. Just like we use Hibernate/Ibatis to map between objects and tables, I would like to map between these two layers of objects. This way, the web service layer can change independently from my existing domain/service layer. What are you using for your mapping layer?
Joshua On 15 Mar 2007 17:48:58 -0000, Robert Monical <[EMAIL PROTECTED]> wrote:
I use a mapping layer to go from WSDL generated to Domain Objects. Since this is a legacy system and the domain objects are reversed out of a database with Hibernate we have information in the domain objects that is not relevent to the Web service interface. If you have the ability/desire to tightly couple the Web service to your domain, then maybe you don't need to do a mapping. I'ld be nervous. >-----Original Message----- >From: [email protected] >Sent: 03/15/07 - 12:18 >To: [email protected] >Subject: RE: Better way to map from axis generated objects to domain? > >Hello, > >Starting from a wsdl/schema, Axis will generate some plumbing >code/objects >to marshal/unmarshal xml. Is there an easier way to map to/from these >generated object to my corresponding domain objects? Is anyone using >any >mapping layer to do this? What are the best practices for insulating >your >existing java code from changes to the code generated by Axis? > >Thanks, > >Joshua --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
