Skip to Main Content

DevOps, CI/CD and Automation

Announcement

For appeals, questions and feedback about Oracle Forums, please email oracle-forums-moderators_us@oracle.com. Technical questions should be asked in the appropriate category. Thank you!

Interested in getting your voice heard by members of the Developer Marketing team at Oracle? Check out this post for AppDev or this post for AI focus group information.

XMLUpdate changes prolog!

435575Oct 2 2011 — edited Oct 3 2011
I have a database with an XMLType column that has the value:

<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/" xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/" xmlns:p2="urn:gfebs.army.mil:Common_Utils" xmlns:p1="urn:gfebs.army.mil:SC-INT-4504_ObligationsCommitments" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<SOAP-ENV:Body>
<mns1:ObligationsCommitments xmlns:mns1="urn:gfebs.army.mil:SC-INT-4504_ObligationsCommitments">
<Item/>
</mns1:ObligationsCommitments>
</SOAP-ENV:Body>
</SOAP-ENV:Envelope>

when I perform an XMLUpdate statement to actually add the meat to the SOAP package by replacing the Item Tag, the resulting XML
looks like this-

<?xml version="1.0" encoding="WINDOWS-1252" standalone="no"?>
<SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/" xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/" xmlns:p2="urn:gfebs.army.mil:Common_Utils" xmlns:p1="urn:gfebs.army.mil:SC-INT-2029_ObligationsCommitments" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<SOAP-ENV:Body>
<mns1:ObligationsCommitments xmlns:mns1="urn:gfebs.army.mil:SC-INT-2029_ObligationsCommitments">
<Item>
<CyCseLn>EGOAA001</CyCseLn>
<Req>BG53751173D035</Req>
<Item/>
</mns1:ObligationsCommitments>
</SOAP-ENV:Body>
</SOAP-ENV:Envelope>

How can I stop the encoding in the prolog from being changed to encoding="WINDOWS-1252"? I want to stay with UTF-8.

Edited by: ga**** on Oct 2, 2011 2:30 PM

Comments

Locked Post
New comments cannot be posted to this locked post.

Post Details

Locked on Oct 31 2011
Added on Oct 2 2011
1 comment
269 views