What information do you really need from the xml-document?! Is there a
header-part, that you can use to control the flow of your xml?! Most of
the time, you do not need the stuff inside the xml, it just flows
through your app without the need to be touched by your program: There
is mostly no business-logic attached to it apart from CRUD, and as long
as you do not need explicit elements from inside the documents, this can
be handled generically by a combination of xslt and xupdate. Have a look
at cocoon, it has lots of patterns to deal with xml without ever
mapping xml into objects.

Bayarsaikhan VOLODYA (YAZ-ArGe) wrote:

>i think, it is not for me.
>my problem is how to seperate these XML documents. should i create objects for each XML document and apply mapping between them? or is there any way to create dynamic objects using XML?
>thanks,
>
>-----Original Message-----
>From: Chanian, Raj [mailto:Raj.Chanian@(protected)]
>Sent: Tuesday, September 14, 2004 6:15 PM
>To: J2EEPATTERNS-INTEREST@(protected)
>Subject: Re: XML messaging
>
>
>Use CorrelationIdentifier messaging pattern
>
>Regards,
>
>Raj Chanian
>LogicaCMG
>
>-----Original Message-----
>From: Bayarsaikhan VOLODYA (YAZ-ArGe) [mailto:bayar@(protected)]
>Sent: 14 September 2004 15:54
>To: J2EEPATTERNS-INTEREST@(protected)
>Subject: XML messaging
>
>
>Hi all, i hope you all are doing well.
>
>There is an challenging project.
>Maybe some of you know about FlexCube. I have to talk to FlexCube using XML
>messaging.
>There are so many XML documents i send to FlexCube to make some kind of
>transaction or blah blah, and result is also in XML format.
>How do i seperate incoming XML? How do i know which kind of transaction is
>that XML.
>How do i manage so many XML documents? Should i convert all of them into
>Java Objects (will be static)? Is there any way to process all these XML in
>similar manner? In future, when there maybe new kind of transaction, i dont
>want to play with my code again. So is there any dynamic way to handle all
>that XML messages? sorry, i know there is so many questions. but i will
>appreciate any feedback, advice from you.
>
>Bayarsaikhan VOLODYA
>
>====================================================================
>Companion Site: http://www.corej2eepatterns.com
>J2EE BluePrints: http://java.sun.com/blueprints/corej2eepatterns
>List Archive:
>http://archives.java.sun.com/archives/j2eepatterns-interest.html
>Unsubscribing: email "signoff J2EEPATTERNS-INTEREST" to
>listserv@(protected)
>
>This e-mail and any attachment is for authorised use by the intended recipient(s) only. It may contain proprietary material, confidential information and/or be subject to legal privilege. It should not be copied, disclosed to, retained or used by, any other party. If you are not an intended recipient then please promptly delete this e-mail and any attachment and all copies and inform the sender. Thank you.
>
>====================================================================
>Companion Site: http://www.corej2eepatterns.com
>J2EE BluePrints: http://java.sun.com/blueprints/corej2eepatterns
>List Archive: http://archives.java.sun.com/archives/j2eepatterns-interest.html
>Unsubscribing: email "signoff J2EEPATTERNS-INTEREST" to listserv@(protected)
>
>====================================================================
>Companion Site: http://www.corej2eepatterns.com
>J2EE BluePrints: http://java.sun.com/blueprints/corej2eepatterns
>List Archive: http://archives.java.sun.com/archives/j2eepatterns-interest.html
>Unsubscribing: email "signoff J2EEPATTERNS-INTEREST" to listserv@(protected)
>
>
>

====================================================================
Companion Site: http://www.corej2eepatterns.com
J2EE BluePrints: http://java.sun.com/blueprints/corej2eepatterns
List Archive: http://archives.java.sun.com/archives/j2eepatterns-interest.html
Unsubscribing: email "signoff J2EEPATTERNS-INTEREST" to listserv@(protected)