Hi Jacob,

Those replies are  indeed very helpful.

Regarding schema design pattern I don't have much idea about various schema
design patterns and their advantages.
The java application which we are working on communicates with web service
which is exposing a wsdl. We plan to use xmlbeans to generate the java
artifacts
representing the wsdl.

The reason I posted that question on inheritance hierarchy was we wanted to
figure
out how can we get a ready made domain model to work with
from the underlying wsdl itself rather than investing time in creating
another domain model at our application layer.

By transfer objects what i meant to ask was can we get a
readymade domain model with the business logic in the form of generated
classes
or they would be dumb objects (just getter/setter) as it is currently in our
case
Will study at the links you posted on extension mechanism.


Directly accessing the generated classes inside the application code can
cause problems when there are changes to the underlying WSDL

So one option was too create a set of classes (one per generated xml class).
These custom
classes will extend the generated xml classes.
So we can have business logic in these custom classes and the app code
communicates with these
custom classes and will not be interacting directly with the xml generated
classes.
This way the application code will also be shielded from any changes to
underlying WSDL.

Another option would be too create these set of custom classes and have a
mapping with xml generated
classes. This involves creating a mapper utility to transfer data from the
xml generated classes to
their custom counterparts. Sounds a bit more overhead here.

Do let me know your viewpoints


-- 
View this message in context: 
http://www.nabble.com/evaluating-xmlbeans-and-best-practices-tf4440007.html#a12687455
Sent from the Xml Beans - User mailing list archive at Nabble.com.


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to