Hi Swami,

We're using ESQL.  What makes you think you need to map elements individually?  I can't believe that you would need to map every element within every XML tag that needed to be copied over from input to output, these messages could be up to 100Mb in size.  This must be a bug within MQSI.  

Regards,

Kulbir.


"SwamiRaj Govindan" <[EMAIL PROTECTED]>

Sent by: "MQSeries List" <[EMAIL PROTECTED]>

11-Jun-2002 14:05
Please respond to "MQSeries List" <[EMAIL PROTECTED]>

       
                       

        To:        MQSERIES

        cc:        
        Subject:        Re: XML attributes being lost/converted to tags



Hi kulbir..
Have u created a message set for the transformation?
or r u using ESQL for the transformation?

if u r using the Messsage Set what domain r u using???(I think it will be
XML)
if u r ESQL you have to map the element within the ESQL Code.

get back on the queries to clear u r problems.


cheers,
swami.



                    "Kulbir S.
                   Thind"                To:     [EMAIL PROTECTED]
                   <Kulbir.S.Thind       cc:
                   @GSK.COM>             Subject:     XML attributes being lost/converted to tags
                   Sent by:
                   MQSeries List
                   <MQSERIES@AKH-W
                   ien.AC.AT>


                    06/11/02 16:41
                   Please respond
                   to MQSeries
                   List







Hi there,

I was wandering if someone could help.  We're using the following
configuration:

MQSI 2.0.2
CSD 3
Windows NT 4 SP 6a
MQSeries 5.2 CSD 1

We're sending XML messages through a flow and having problems with the XML
format.  When we send a message through a flow that will:
    Move a portion of the the XML message to the destination list
    Create a new XML message
    Restore the XML portion from the destination list to the outbound
    message

     We end up with a problem with the XML produced.  For example if we
    send the following XML tags in the input XML message:

     <GSK.ChartOfAccounts elementName="GSK.ChartOfAccounts" language
    ="English" action="load"><UniqueName class
    ="java.lang.String">A00PC63020.1225.10</UniqueName></GSK.ChartOfAccounts>


     The output message produced contains the above tags in the following
    format:

     <GSK.ChartOfAccounts><elementName>GSK.ChartOfAccounts></elementName><language>English</language><action>load</action><UniqueName>A00PC63020.1225.10</UniqueName></GSK.ChartOfAccounts>


     The following problems exist:

     attributes are sometimes converted to tags (i.e. elementName,
    language, action>
    attributes are lost (i.e. class attribute for the UniqueName tag)

     Has anyone seen this before?  Any suggestions?

     Regards,

     Kulbir.




*****************************  DISCLAIMER  ***************************

This message is confidential to the company, and is intended only
for the named recipient. It may also be privileged or otherwise
protected by work product immunity or other legal rules. If you are
not the intended recipient, you are requested to delete this mail and
also be notified that disclosing, copying, distributing or taking any
action in reliance on the contents of this mail is strictly prohibited.
The company accepts no liability for any damage caused by any virus
transmitted by this email.

**********************************************************************

Instructions for managing your mailing list subscription are provided in
the Listserv General Users Guide available at http://www.lsoft.com
Archive: http://vm.akh-wien.ac.at/MQSeries.archive



Reply via email to