Author |
Message
|
schroederms |
Posted: Tue Sep 08, 2009 10:37 am Post subject: Message with Encoding after top level tag |
|
|
 Disciple
Joined: 21 Jul 2003 Posts: 169 Location: IA
|
We are in the process of recovering messages stored as clobs from our database. We are able to do it, however not without putting a parent tag around everyting, in this case <RECOVERED>
Now we are trying to strip that tag off and get the to the <REQUEST> tag, but no matter what we try we get a parser error.
Any ideas on what the coding would look like to do that? Here is the message. All I want is the message, that actaull starts with <REQUEST>
Thanks in advance.
<RECOVERED>
<?xml version="1.0"?>
<REQUEST>
<CONTROL>
<ORIGINATOR>EAI_NFIS_PUB_SUB_NAME_ADDRESS Flow</ORIGINATOR>
<ORIGIN_DATETIME>2009-09-05 08:49:13.901052</ORIGIN_DATETIME>
<SERVICE>NFIS</SERVICE>
<FUNCTION>PUBLICATION</FUNCTION>
<DESTINATION>
<INSTANCE>PR</INSTANCE>
<CLIENT>999</CLIENT>
</DESTINATION>
<VERSION>1.0</VERSION>
<PERSISTENCE>Y</PERSISTENCE>
<REALTIME>Y</REALTIME>
<AUDIT_LOG>Y</AUDIT_LOG>
<MY_LOOP_COUNT>104</MY_LOOP_COUNT>
<NFIS>
<RELATIONSHIP_FLAG>N</RELATIONSHIP_FLAG>
</NFIS>
<ROUTER_MSGTIMES>
<GMTMSGSTART>2009-09-05 13:49:16.850970</GMTMSGSTART>
<GMTMSGCOMPLETION>2009-09-05 13:49:16.851118</GMTMSGCOMPLETION>
</ROUTER_MSGTIMES>
</CONTROL>
<APP>
<PUBSUB>
<TOPICNAME>NFIS/PARTNER/NA/ROLE_ID/5</TOPICNAME>
</PUBSUB>
<USER>
<FIS_ID>17020118</FIS_ID>
<ROLE_ID>5</ROLE_ID>
<ROLE_DESCRIPTION>Business Partner</ROLE_DESCRIPTION>
<ROLE_TYPE_ID/>
<ROLE_TYPE_NAME/>
<PARTNER_ROLE_TYPE_ID/>
<FIRST_NAME>Sam</FIRST_NAME>
<LAST_NAME>Witte</LAST_NAME>
<MIDDLE_NAME/>
<PREFERRED_NAME/>
<BUSINESS_NAME/>
<PREFIX/>
<SUFFIX/>
<WEBSITE_ADDRESS/>
<LANGUAGE_ID>1</LANGUAGE_ID>
<LANGUAGE>English</LANGUAGE>
<PARTNER_TYPE_ID>1</PARTNER_TYPE_ID>
<PARTNER_TYPE_NAME>Individual</PARTNER_TYPE_NAME>
<BEGIN_DATE>19991219 </BEGIN_DATE>
<END_DATE/>
<INACTIVATION_REASON_ID/>
<INACTIVATION_REASON_NAME/>
<ADDRESS>
<ADDRESS_TYPE>Mailing</ADDRESS_TYPE>
<IS_PRIMARY>TRUE</IS_PRIMARY>
<STREET1>51 Nw 80 Ave</STREET1>
<STREET2/>
<CITY>Great Bend</CITY>
<REGION_ABBR>KS</REGION_ABBR>
<REGION_NAME>Kansas</REGION_NAME>
<POSTALCODE>67530</POSTALCODE>
<COUNTY_NAME>Barton</COUNTY_NAME>
<FIPS_CODE>20009</FIPS_CODE>
<COUNTRY_CODE>US</COUNTRY_CODE>
<COUNTRY_NAME>United States</COUNTRY_NAME>
</ADDRESS>
<ADDRESS>
<ADDRESS_TYPE>Shipping</ADDRESS_TYPE>
<IS_PRIMARY>TRUE</IS_PRIMARY>
<STREET1>51 Nw 80 Ave</STREET1>
<STREET2/>
<CITY>Great Bend</CITY>
<REGION_ABBR>KS</REGION_ABBR>
<REGION_NAME>Kansas</REGION_NAME>
<POSTALCODE>67530</POSTALCODE>
<COUNTY_NAME>Barton</COUNTY_NAME>
<FIPS_CODE>20009</FIPS_CODE>
<COUNTRY_CODE>US</COUNTRY_CODE>
<COUNTRY_NAME>United States</COUNTRY_NAME>
</ADDRESS>
<PHONE>
<PHONE_TYPE>Work</PHONE_TYPE>
<NUMBER>(620) 792-3476</NUMBER>
<EXTENSION/>
<PHONE_NUMBER_TYPEID>2</PHONE_NUMBER_TYPEID>
</PHONE>
<PHONE>
<PHONE_TYPE>Alternate</PHONE_TYPE>
<NUMBER>(620) 792-3476</NUMBER>
<EXTENSION/>
<PHONE_NUMBER_TYPEID>5</PHONE_NUMBER_TYPEID>
</PHONE>
<RETURN_CODE>0</RETURN_CODE>
<DESCRIPTION>Complete</DESCRIPTION>
<OPERATION_CD>I</OPERATION_CD>
</USER>
</APP>
<STATUS>
<CODE>0</CODE>
<DESCRIPTION>SUCCESSFUL</DESCRIPTION>
</STATUS>
</REQUEST>
</RECOVERED> |
|
Back to top |
|
 |
Vitor |
Posted: Tue Sep 08, 2009 10:40 am Post subject: Re: Message with Encoding after top level tag |
|
|
 Grand High Poobah
Joined: 11 Nov 2005 Posts: 26093 Location: Texas, USA
|
schroederms wrote: |
We are able to do it, however not without putting a parent tag around everyting, in this case <RECOVERED>
|
What forces the insertion of this tag?
schroederms wrote: |
no matter what we try we get a parser error |
What error? At what point in the processing? Using what level of WMB?
What have you already tried? There's no point us suggesting things which have already failed. _________________ Honesty is the best policy.
Insanity is the best defence. |
|
Back to top |
|
 |
schroederms |
Posted: Tue Sep 08, 2009 10:42 am Post subject: |
|
|
 Disciple
Joined: 21 Jul 2003 Posts: 169 Location: IA
|
The tag is from the message that is hardened to our database to track all messages through our services. This is the encoding from the original message. |
|
Back to top |
|
 |
mqjeff |
Posted: Tue Sep 08, 2009 10:46 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008 Posts: 17447
|
It's not valid XML to have the <?xml declaration anywhere but at the start of the document. |
|
Back to top |
|
 |
Vitor |
Posted: Tue Sep 08, 2009 10:47 am Post subject: |
|
|
 Grand High Poobah
Joined: 11 Nov 2005 Posts: 26093 Location: Texas, USA
|
schroederms wrote: |
The tag is from the message that is hardened to our database to track all messages through our services. This is the encoding from the original message. |
Why put the tag there?
What about the answers to my other questions? _________________ Honesty is the best policy.
Insanity is the best defence. |
|
Back to top |
|
 |
jbanoop |
Posted: Tue Sep 08, 2009 10:49 am Post subject: |
|
|
Chevalier
Joined: 17 Sep 2005 Posts: 401 Location: SC
|
have you tried storing the retrieved message to the environment tree, moving to the <REQUEST> tag (using the MOVE statement) and then attaching this as the last child of the outgoing message ?
Can you show us the code(s) that you have already tried ? |
|
Back to top |
|
 |
kimbert |
Posted: Tue Sep 08, 2009 10:53 am Post subject: |
|
|
 Jedi Council
Joined: 29 Jul 2003 Posts: 5542 Location: Southampton
|
Quote: |
no matter what we try we get a parser error |
Tut. No help from me until you paste the full text of that error message. Take a user trace if necessary. |
|
Back to top |
|
 |
|