Remove ?xml version = '1.0'?
I have a requirement In which i have to wite XML o/p into file.
I have used the XMLelement function to create xml and then used Utl_file.put_raw to raw the data into file.
But the requirement was to write the output for more than 1,00,000 transactions. So i have to break the query and run a loop and to write each 10,000 records in one loop as i was running out of memory. The code is working fine but the tag <?xml version = '1.0'?> is comming after each 10,000 iteration i.e after next loop starts to process anothe bunch of 10,000 records <?xml version = '1.0'?> header again comes at the top so for 100,000 records the <?xml version = '1.0'?> is comming 10 times. As i am appending o/p of next iteration to the previous one.
it is like <?xml version = '1.0'?>
trans 1
trans 10,000
<?xml version = '1.0'?>
trans 1
. trans 10,000
<?xml version = '1.0'?>
My question is how can i remove <?xml version = '1.0'?> from my xml. i tried to convert my xmltype into clob and then apply the substr but it is giving me error XML parsing failed.
my oracle version is 10g.
It would be great if you could suggest any possible way to remove <?xml version = '1.0'?> from header.
Source code is
Edited by: 965358 on Dec 17, 2012 7:32 AM
Please see the below code. I am not using XMLROOT
create or replace procedure test1(p_entity_ref in varchar2,
p_filepath IN VARCHAR2,
p_filename IN VARCHAR2) is
-- Data Variables
v_xml XMLTYPE;
v_blob BLOB;
v_data_length NUMBER;
-- Loop Control Variables
v_offset NUMBER DEFAULT 1;
v_chunk CONSTANT NUMBER DEFAULT 4000;
-- UTL_FILE variables
fh UTL_FILE.file_type;
l_count number;
MIN_AC_Entry number;
Max_ac_entry number;
max_limit number;
l_loop NUMBER ;
MyList INT_LIST := INT_LIST();
cursor Cur_AC_entry is
Select AC_ENTRY_SR_NO
from trans
where entity_ref = p_entity_ref
order by AC_ENTRY_SR_NO;
BEGIN
open Cur_AC_entry;
loop
fetch Cur_AC_entry bulk collect into MyList LIMIT 4000;
EXIT WHEN MyList.count = 0;
v_xml := null;
select XMLAGG(xmlelement("transaction",
xmlelement("transactionnumber",
trans.Trn_Ref_No),
xmlelement("transaction_description",
trans.trn_desc),
xmlelement("date_transaction",
to_char(trans.trn_dt,
'YYYY-MM-DD') || 'T' ||
to_char(trans.trn_dt,
'HH24:MI:SS')),
xmlelement("teller",
trans.Maker_ID),
xmlelement("authorized",
trans.checker_id),
xmlelement("value_date",
to_char(trans.value_dt,
'YYYY-MM-DD') || 'T' ||
to_char(trans.value_dt,
'HH24:MI:SS')),
xmlelement("transmode_code",
trans.transaction_mode),
xmlelement("amount_local",
trans.lcy_amount),
CASE
WHEN source.source_party <>
'acc_with_bntb' THEN
xmlelement("t_from_my_client", xmlelement("from_funds_code", source.from_FUNDS_TYPE), xmlelement("from_foreign_currency", xmlelement("foreign_currency_code", source.FCY), xmlelement("foreign_amount", source.FCY_AMOUNT), xmlelement("foreign_exchange_rate", source.EXCH_RATE)), CASE
WHEN trans.transaction_mode <>
'Cash_Transaction' Then
xmlelement("from_account",
xmlelement("institution_name",
source.INSTITUTION_NAME),
xmlelement("institution_code",
source.INSTITUTION_ID),
xmlelement("branch",
source.AC_BRANCH),
xmlelement("account",
source.AC_NO),
xmlelement("currency_code",
source.LCY),
xmlelement("account_name",
source.ACCOUNT_NAME),
xmlelement("client_number",
source.CUST_No),
xmlelement("personal_account_type",
source.ACCOUNT_TYPE),
xmlelement("signatory",
xmlelement("is_primary",
source.is_primary),
xmlelement("t_person",
xmlelement("gender",
source.GENDER),
xmlelement("title",
source.TITLE),
xmlelement("first_name",
source.FIRST_NAME),
xmlelement("middle_name",
source.MIDDLE_NAME),
xmlelement("last_name",
source.LAST_NAME),
xmlelement("birthdate",
to_char(source.DATE_OF_BIRTH,
'YYYY-MM-DD') || 'T' ||
to_char(source.DATE_OF_BIRTH,
'HH24:MI:SS')),
xmlelement("nationality1",
source.NATIONALITY),
xmlelement("phones",
xmlelement("tph_contact_type",
source.CONTACT_TYPE),
xmlelement("tph_communication_type",
source.COMMUNICATION_TYPE),
xmlelement("tph_country_prefix",
source.COUNTRY_CODE),
xmlelement("tph_number",
source.PHONE_NUMBER)),
xmlelement("addresses",
xmlelement("address_type",
source.ADDRESS_TYPE),
xmlelement("address",
source.ADDRESS),
xmlelement("city",
source.CITY)),
xmlelement("occupation",
source.OCCUPATION),
xmlelement("t_person_identification",
xmlelement("type",
source.ID_TYPE),
xmlelement("number",
source.ID_NUMBER),
xmlelement("issue_country",
source.ISSUED_IN)))),
xmlelement("opened",
to_char(source.AC_OPEN_DATE,
'YYYY-MM-DD') || 'T' ||
to_char(source.AC_OPEN_DATE,
'HH24:MI:SS')),
xmlelement("balance",
source.ACY_BALANCE),
xmlelement("status_code",
source.ACCOUNT_STATUS),
xmlelement("beneficiary",
source.BENEF_DETAILS)
ELSE
xmlelement("from_person",
xmlelement("gender",
source.GENDER),
xmlelement("title",
source.TITLE),
xmlelement("first_name",
source.FIRST_NAME),
xmlelement("middle_name",
source.MIDDLE_NAME),
xmlelement("last_name",
source.LAST_NAME),
xmlelement("birthdate",
to_char(source.DATE_OF_BIRTH,
'YYYY-MM-DD') || 'T' ||
to_char(source.DATE_OF_BIRTH,
'HH24:MI:SS')),
xmlelement("nationality1",
source.NATIONALITY),
xmlelement("phones",
xmlelement("tph_contact_type",
source.CONTACT_TYPE),
xmlelement("tph_communication_type",
source.COMMUNICATION_TYPE),
xmlelement("tph_country_prefix",
source.COUNTRY_CODE),
xmlelement("tph_number",
source.PHONE_NUMBER)),
xmlelement("addresses",
xmlelement("address_type",
source.ADDRESS_TYPE),
xmlelement("address",
source.ADDRESS),
xmlelement("city",
source.CITY)),
xmlelement("occupation",
source.OCCUPATION),
xmlelement("t_person_identification",
xmlelement("type",
source.ID_TYPE),
xmlelement("number",
source.ID_NUMBER),
xmlelement("issue_country",
source.ISSUED_IN)))
END,
xmlelement("from_country",
source.country_code))
Else
xmlelement("t_from",
xmlelement("from_funds_code",
source.from_FUNDS_TYPE),
xmlelement("from_foreign_currency",
xmlelement("foreign_currency_code",
source.FCY),
xmlelement("foreign_amount",
source.FCY_AMOUNT),
xmlelement("foreign_exchange_rate",
source.EXCH_RATE)),
CASE
WHEN trans.transaction_mode <>
'Cash_Transaction' Then
xmlelement("from_account",
xmlelement("institution_name",
source.INSTITUTION_NAME),
xmlelement("institution_code",
source.INSTITUTION_ID),
xmlelement("account",
source.AC_NO))
ELSE
xmlelement("from_person",
xmlelement("first_name",
source.FIRST_NAME),
xmlelement("last_name",
source.LAST_NAME))
end,
xmlelement("from_country",
source.country_code))
END,
CASE
WHEN dest.dest_party <>
'acc_with_bntb' THEN
xmlelement("t_to_my_client1", xmlelement("to_funds_code", dest.To_FUNDS_TYPE), xmlelement("to_foreign_currency", xmlelement("to_foreign_currency", dest.FCY), xmlelement("foreign_amount", dest.FCY_AMOUNT), xmlelement("foreign_exchange_rate", dest.EXCH_RATE)), CASE
WHEN trans.transaction_mode <>
'Cash_Transaction' Then
xmlelement("t_to_account",
xmlelement("institution_name",
dest.INSTITUTION_NAME),
xmlelement("institution_code",
dest.INSTITUTION_ID),
xmlelement("branch",
dest.AC_BRANCH),
xmlelement("account",
dest.AC_NO),
xmlelement("currency_code",
dest.LCY),
xmlelement("account_name",
dest.ACCOUNT_NAME),
xmlelement("client_number",
dest.CUST_No),
xmlelement("personal_account_type",
dest.ACCOUNT_TYPE),
xmlelement("signatory",
xmlelement("is_primary",
dest.is_primary),
xmlelement("t_person",
xmlelement("gender",
dest.GENDER),
xmlelement("title",
dest.TITLE),
xmlelement("first_name",
dest.FIRST_NAME),
xmlelement("middle_name",
dest.MIDDLE_NAME),
xmlelement("last_name",
dest.LAST_NAME),
xmlelement("birthdate",
to_char(dest.DATE_OF_BIRTH,
'YYYY-MM-DD') || 'T' ||
to_char(dest.DATE_OF_BIRTH,
'HH24:MI:SS')),
xmlelement("nationality1",
dest.NATIONALITY),
xmlelement("phones",
xmlelement("tph_contact_type",
dest.CONTACT_TYPE),
xmlelement("tph_communication_type",
dest.COMMUNICATION_TYPE),
xmlelement("tph_country_prefix",
dest.COUNTRY_CODE),
xmlelement("tph_number",
dest.PHONE_NUMBER)),
xmlelement("addresses",
xmlelement("address_type",
dest.ADDRESS_TYPE),
xmlelement("address",
dest.ADDRESS),
xmlelement("city",
dest.CITY)),
xmlelement("occupation",
dest.OCCUPATION),
xmlelement("t_person_identification",
xmlelement("type",
dest.ID_TYPE),
xmlelement("number",
dest.ID_NUMBER),
xmlelement("issue_country",
dest.ISSUED_IN)))),
xmlelement("opened",
to_char(dest.AC_OPEN_DATE,
'YYYY-MM-DD') || 'T' ||
to_char(dest.AC_OPEN_DATE,
'HH24:MI:SS')),
xmlelement("balance",
dest.ACY_BALANCE),
xmlelement("status_code",
dest.ACCOUNT_STATUS),
xmlelement("beneficiary",
dest.BENEF_DETAILS)
ELSE
xmlelement("to_person",
xmlelement("gender",
dest.GENDER),
xmlelement("title",
dest.TITLE),
xmlelement("first_name",
dest.FIRST_NAME),
xmlelement("middle_name",
dest.MIDDLE_NAME),
xmlelement("last_name",
dest.LAST_NAME),
xmlelement("birthdate",
to_char(dest.DATE_OF_BIRTH,
'YYYY-MM-DD') || 'T' ||
to_char(dest.DATE_OF_BIRTH,
'HH24:MI:SS')),
xmlelement("nationality1",
dest.NATIONALITY),
xmlelement("phones",
xmlelement("tph_contact_type",
dest.CONTACT_TYPE),
xmlelement("tph_communication_type",
dest.COMMUNICATION_TYPE),
xmlelement("tph_country_prefix",
dest.COUNTRY_CODE),
xmlelement("tph_number",
dest.PHONE_NUMBER)),
xmlelement("addresses",
xmlelement("address_type",
dest.ADDRESS_TYPE),
xmlelement("address",
dest.ADDRESS),
xmlelement("city",
dest.CITY)),
xmlelement("occupation",
dest.OCCUPATION),
xmlelement("t_person_identification",
xmlelement("type",
dest.ID_TYPE),
xmlelement("number",
dest.ID_NUMBER),
xmlelement("issue_country",
dest.ISSUED_IN)))
END,
xmlelement("to_country",
dest.country_code))
Else
xmlelement("t_to", xmlelement("to_funds_code", dest.To_FUNDS_TYPE), xmlelement("to_foreign_currency", xmlelement("foreign_currency_code", dest.FCY), xmlelement("foreign_amount", dest.FCY_AMOUNT), xmlelement("foreign_exchange_rate", dest.EXCH_RATE)),
CASE
WHEN trans.transaction_mode <>
'Cash_Transaction' Then
xmlelement("to_account",
xmlelement("institution_name",
dest.INSTITUTION_NAME),
xmlelement("institution_code",
dest.INSTITUTION_ID),
xmlelement("account",
dest.AC_NO))
ELSE
xmlelement("to_person",
xmlelement("first_name",
dest.FIRST_NAME),
xmlelement("last_name",
dest.LAST_NAME))
end,
xmlelement("to_country", dest.country_code))
END))
INTO V_XML
from trans trans,
dest dest,
source source
where source.AC_ENTRY_SR_NO = dest.AC_ENTRY_SR_NO
AND trans.AC_ENTRY_SR_NO = source.AC_ENTRY_SR_NO
AND trans.ENTITY_REF = dest.ENTITY_REF
AND trans.ENTITY_REF = source.ENTITY_REF
AND trans.entity_ref = p_entity_ref
AND source.AC_ENTRY_SR_NO in (select * from table(MyList));
Edited by: 965358 on Dec 18, 2012 1:35 AM
Edited by: 965358 on Dec 18, 2012 1:38 AM
Similar Messages
-
How to remove ?xml version="1.0" encoding="UTF-8"? .
HI Experts,
i am doing one scenario file to file . in soruce payload i have <?xml version="1.0" encoding="UTF-8"?> . i want to remove <?xml version="1.0" encoding="UTF-8"?> at target side. is it possible .
regards,
alekhya.Hello,
i want to remove <?xml version="1.0" encoding="UTF-8"?> at target side. is it possible .
You can use XSLT and add
<xsl:output method="text" version="1.0" encoding="UTF-8" omit-xml-declaration="yes"/>
in your output declaration
Hope this helps,
Mark -
Remove ?xml version="1.0" encoding="UTF-8"? from XML doc
I have generated an XML file using javax XML transformer. In the XML file thats generated I have the version and the encoding line
<?xml version="1.0" encoding="UTF-8"?>
which is automatically generated in my XML file. Is there any way that I can avoid that from the XML file thats generated.
Here is the transformer that I have used.
public static void printToXML(String fileName){
try{
File file = new File(fileName);
Transformer tr = TransformerFactory.newInstance().newTransformer();
tr.setOutputProperty(OutputKeys.INDENT, "yes");
tr.setOutputProperty(OutputKeys.METHOD,"xml");
tr.setOutputProperty("{http://xml.apache.org/xslt}indent-amount", "3");
tr.transform( new DOMSource(dom),new StreamResult(new FileWriter(file)));
}catch(TransformerConfigurationException tcex){
logger.info("TransformerConfigurationException at printToXML method in CSVtoXML.java");
logger.error("TransformerConfigurationException", tcex);
}catch(TransformerException tex){
logger.info("TransformerException at printToXML method in CSVtoXML.java");
logger.error("TransformerException", tex);
}catch(IOException ioex){
logger.info("IOException at printToXML method in CSVtoXML.java");
logger.error("IOException", ioex);
}Well, it is a pretty important line. Why do you need it removed? Anything that really processes XML knows how to read it and determine what encoding was used. That is vital, if you look at the number of questions posted here about foreign language text in XML. If you really have a text processsor that knows how to open a file called something.xml, and knows how to process or ignore most of the pointy bracket things, but not this one, it is time to fix it.
Dave Patterson -
hi experts,
how to remove <?xml version="1.0" encoding="UTF-8"?> from receiver payload.
my source srtucture is ,
<?xml version="1.0" encoding="UTF-8"?>
<ns0:entity-data xmlns:ns0="http://www.xxx.com">
<Customer>
<CustNo>xxx</CustNo>
</Customer>
</ns0:entity-data>
in receiver payload i dont wont " <?xml version="1.0" encoding="UTF-8"?> "
i want receiver payload
<ns0:entity-data xmlns:ns0="http://www.xxx.com">
<Customer>
<CustNo>xxx</CustNo>
</Customer>
</ns0:entity-data>
can any one provide me the solution for this.
regards,
ganeshhi vijayakumar,
thanx for ur response.... -
On outgoing messages, when I look in MONI, I see properly formatted XML message.
The first line of all my outgoing files has this line:
<?xml version="1.0" encoding="UTF-8" ?>
Is there a way to suppress this?
If so, is there a way to suppress for only certain partners within one interface?
Thanks,
JeffHi Jeff,
As others pointed without this line the document will not be a valid document. Can you tell your complete requirment. One of these kind of requirement is discussed in this thread, you can see whether its the same in your case or not. If not then tell your complete req. so that somebody can help you out here.
Remove first line in the XML Document
Regards,
---Satish -
Hi
i have a doubt if any one knows please let me know.
in atg rest service(POST Request) i am sending request as xml and also i am expecting response as xml
i have configured to get response as xml,but i want to delete xml prolog<?xml version="1.0" encoding="UTF-8"?>) from my response can we have property to remove xml prolog by using atg server.
thanks in advance
balaHello Soumya,
Good to know it worked, I have got some doubts of using XPATH have U ever worked on that, let me know.
Bye,
Sam Mathew -
How to remove ?xml version=
Dear All,
The moment I can see <?xml version="1.0"?> sentence in JSC produced pages going in the first line.
Does anybody know the easiest way to remove/disable this 'feature' from the generated pages.
The problem is comming using IE6.0 as a browser. I use CSS styles with fixed-size centered colums. IE6.0 goes nuts while anything else coming before DOCTYPE definition and swithes to quirk mode.
Quirk mode makes my CSS looks agly and doesn't support centered layout.
I have to say it is very annoying :)
AlexSorry, but I want remove this first line with <?xml version...
To check what gives a bug I did the following:
1.Run my page in design mode and it looks fine
2. Clear and build my project, run it under Sun App Serv 8.2
3. Can see centered CSS doesn't work
4. Save source HTML by using 'View Source' context menu and remove annoying <?xml version...
5. I got it - IT WORKS FINE.
6. Please look at http://www.adobe.com/devnet/dreamweaver/articles/css_concepts_03.html (paragraph just before picture of Quirk and Standard mode)
7. What is the reason of putting <xml into to the first line. XHTML is NOT xml anyway.
King regards,
Alex -
Removing ?xml version="1.0"? from the result
Hi Friends
How do we remove <?xml version="1.0"?> from the result if we have ran two query in one resultset
e.g
qryCtx := DBMS_XMLGEN.newContext('select ename, job from emp where empno > 7900');
DBMS_XMLGEN.setRowSetTag(qryCtx,'employeedata');
DBMS_XMLGEN.setRowTag(qryCtx,'emp');
result := DBMS_XMLGEN.getXML(qryCtx);
insert into temp_clob_tab values(result);
DBMS_XMLGEN.closeContext(qryCtx);
qryCtx := DBMS_XMLGEN.newContext('select * from dept');
DBMS_XMLGEN.setRowSetTag(qryCtx,'departments');
DBMS_XMLGEN.setRowTag(qryCtx,'dept');
result := DBMS_XMLGEN.getXML(qryCtx);
insert into temp_clob_tab values(result);
DBMS_XMLGEN.closeContext(qryCtx);
RESULT
<?xml version="1.0"?>
<employeedata>
<emp>
<ENAME>FORD</ENAME>
<JOB>ANALYST</JOB>
</emp>
<emp>
<ENAME>MILLER</ENAME>
<JOB>CLERK</JOB>
</emp>
</employeedata>
<?xml version="1.0"?>
<departments>
<dept>
<DEPTNO>10</DEPTNO>
<DNAME>ACCOUNTING</DNAME>
<LOC>NEW YORK</LOC>
</dept>
<dept>
<DEPTNO>20</DEPTNO>
<DNAME>RESEARCH</DNAME>
<LOC>DALLAS</L[i]Long postings are being truncated to ~1 kB at this time.Why do you want to get rid of the XML header ? If you want to concatenate the two values to produce a single XML document, I would recommend using XMLConcat or XMLAgg SQL functions.
- Ravi -
Remove ?xml version="1.0" encoding="UTF-8"? from xml file
I have generated an XML file using sax paraser. In the XML file thats generated I have the version and the encoding line
<?xml version="1.0" encoding="UTF-8"?>which is automatically generated in my XML file. Is there any way that I can avoid that from the XML file thats generated.try
FileWriter fr = new FileWriter(new File(path, fileName));
Document docNode = docNodeMap.get(name);
XMLOutputter outputter = new XMLOutputter();
outputter.output(docNode, fr);
fr.close();
catch (IOException e)
e.printStackTrace();
}this the code generating xml file. -
Is it possible to remove xml declaration from a target HTTP msg in PI 7.1?
Hello,
I am working on a SOAP to HTTP scenario in PI 7.1.
I am using a java mapping to create a target string. This target string does not contain XML declaration(<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>) in it.
To elaborate the issue, while testing the message mapping, this XML declaration is not being prefixed to the message content. But, in integration engine, the http target message is being prefixed by this XML declaration by default.
Output when tested in Operation Mapping(Desired result):
abc=123:def=456
Output been sent to receiver:
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?> abc=123:def=456
Is there any possibility to send a HTTP message to the receiver without this XML declartion. In other words, I need only the message content to be sent to the receiver.
Kindly suggest.
Regards,
SwethaHi,
You can use JAVA/or XSLT mapping
See this for Code
Remove Encoding UTF from xml declaration in PI -
XML - including: " ?xml version="1.0" encoding="UTF-8"? "
When I parse an XML document and output:
#xmlCode.XMLRoot.property.autoID#
I get this line before every field: <?xml version="1.0"
encoding="UTF-8"?>
eg.
<?xml version="1.0" encoding="UTF-8"?>
<autoID>19</autoID>
<?xml version="1.0" encoding="UTF-8"?>
<autoID>53</autoID>
<?xml version="1.0" encoding="UTF-8"?>
<autoID>59</autoID>
How do I stop this? I just want the number from the field.
I also don't understand why it is UTF-8 when I specify
iso-8859-1.If you use the CFXML tag, you dont need to do the <?xml
version='1.0' encoding='iso-8859-1'?> line in your code. It will
do it for you automatically.
Remove it and it should be fine.
EX:
<cfxml variable="rsPropDataXML" casesensitive="no">
<allData>
<cfoutput query="rsPropData" maxrows="20">
<property>
<autoID>#rsPropData.autoID#</autoID>
<Tour>#rsPropData.Tour#</Tour>
</property>
</cfoutput>
</allData>
</cfxml> -
Problem with PI ?xml version="1.0"? in parseEscapedXML
Hi,
Our process reciveing the xml contend as string which contains the
PI <?xml version="1.0" encoding="utf-8"?> i need to convert this string as xml
when i use the function ora:parseEscapedXML(strvar) am getting the exception PI instruction is not allowed in this. can you please tell me is there any way other than string trim operation or other function provieds the conversion with PI.
Thanks
BogiBogi
Had exactly the same issue with an external supplier who would not change the interface to remove this line. We created a java proxy which was called instead of the BPEL, then stripped out the invalid line and then called the BPEL. Not pretty, but worked.
Pete -
Do not include ?xml version="1.0" encoding="UTF8" when transform?
I try to Output correctly XML(sox) from DOM with transformer. The first two lines of output should like this
<?soxtype PurchaseOrder urn:x-commerceone:document:com:commerceone:CBL:CBL.sox$1.0?>
<?import PurchaseOrder urn:x-commerceone:document:com:commerceone:CBL:CBL.sox$1.0?> .
But what I get always inclue <?xml version="1.0" encoding="UTF-8" ?> ,how can I remove this line when transform?
Thanks in advance.well, you get a legal regular XML prolog in your XML file.
without it, your file can't really be called an XML file...
if you don't want it, you can try changing the output type to "text", so you will get an XML looking text file, with no problem.
but of course this is not really serious. -
Hi,
When I am Using append mode in file adapter,for each file that i send a seperate <?xml version="1.0" encoding="UTF-8"?> tag is getting generated in the target.
eg:
File 1
<?xml version="1.0" encoding="UTF-8"?>
<DEPT>
<name>e1</name>
</DEPT>
File 2
<?xml version="1.0" encoding="UTF-8"?>
<DEPT>
<name>e2</name>
</DEPT>
Result
<?xml version="1.0" encoding="UTF-8"?>
<DEPT>
<name>e1</name>
</DEPT>
<?xml version="1.0" encoding="UTF-8"?>
<DEPT>
<name>e2</name>
</DEPT>
Here <?xml version="1.0" encoding="UTF-8"?> tag is repeated.
How to remove the same from 2nd time.so that my output file is displayed as follows
<?xml version="1.0" encoding="UTF-8"?>
<DEPT>
<name>e1</name>
</DEPT>
<DEPT>
<name>e2</name>
</DEPT>
Thanks in advance
sreeHi
Did you check the occurence of DEPT Node as 0..unbounded???
Did You check the output from Test tab of Message Mapping???
Did You use the Node function in mapping???
if not
You better use either Java mapping
with regards
Gabriel -
How to remove xmls from output?
Hello All,
I have created a BPEL process that takes a flat file and converts to an XML file. I get an output of the following (see below). Is there a way that I can remove xmlns="" from the output?
Incorrect Output
<?xml version="1.0" encoding="UTF-8" ?>
<WhseShipNotice xmlns="">
Correct Output
<?xml version="1.0" encoding="UTF-8" ?>
<WhseShipNotice>
Any suggestions?
Regards,
KathyI can remember if this xsd removes namespaces correctly, I think it may still have the initial xmlns at the top but give it a try. Typically what needs to be done is some embedded java to do this.
<schema targetNamespace="http://www.oracle.com/Gateway"
xmlns="http://www.w3.org/2001/XMLSchema">
<element name="Message">
<complexType>
<sequence>
<element name="Header">
<complexType>
<sequence>
<element name="UniqueID" type="string"/>
<element name="RoutingRule" type="string"/>
<element name="FileName" type="string"/>
<element name="Destination" type="string"/>
<element name="TransportType" type="string"/>
<element name="Attachment" type="string"/>
<element name="MQMessageID" type="string"/>
<element name="MQCorrelationID" type="string"/>
</sequence>
</complexType>
</element>
<element name="Payload" type="base64Binary"/>
</sequence>
</complexType>
</element>
</schema>cheers
James
Maybe you are looking for
-
KEEPING APERTURE 2 and 3 side-by-side
Hi everyone... ...I was one of those whose Macbook Pros seized up for days when trying to upgrade to 3 from 2. In the end I reverted to 2 and restored from my backed up AP2 Library. All fine. QUESTION: Is a viable answer to buy AP3 complete, and run
-
Get child nodes and only child nodes from a tree?
Hi all, Relatively simple table create table replaced_parts old_part_number varchar(7), replaced_part_number varchar(7), updated_date date insert into Replaced_parts values('AAAAA/1', 'BBBBB/1', '2012-Feb-16'); insert into Replaced_parts values('BBBB
-
CR XI R2 Cannot find Nth root - "Numeric Overflow" Error
In Crystal Reports Xi Release 2, when i try to perform a calculation within a formula X ^ Y where Y = 1/years and Y < 1, I receive a "Numeric Overflow" error when running the report. Is there anything that can be done to work around or fix this?
-
Hi, I am implementing Quality Module. I have copied the collection plans Defined parent-child relationship Updated menu entry to point to the correct plan (Mandatory). Made changes to Form Functions window I am in Receiving Transactions and I enter t
-
Been testing with my new Vista 64 install here's what I found
Some one correct if I'm wrong but I've been doign alot of testing since adding Vista 64 to my computer. There's been alot of speculation about Vista 64 and possible benefits to premiere. From what I can tell there are none. Besides Photoshop being 64