Malformed XML

I've just started playing with WLP7SP2, and noticed that the EBCC
seems to produce invalid web.xml deployment descriptors, but what
bothers me is that WLS accepts them as valid. It's mixing the order
of the <servlet> and <servlet-mapping> elements. According to the
DTD, all of the servlet elements should precede the servlet-mapping
elements, while the xml produced by the EBCC seems to output one
servlet followed by its servlet-mapping, then another, and so on.
However, if you validate and persist the web deployment descriptors in
the console, they are rewritten correctly, so at least someone
understands how to handle XML.
The question is, why does WLS accept invalid web.xml deployment
descriptors, and are there any plans to fix this?

ParvezHakim wrote:
Can some body help me.Not really. Your project description is clear enough, but do you have a problem? You haven't said what it is, so how could we help you? And if the problem is "I don't have a clue how to get started" then how can we help you? Your first step should be to learn about XML and Java programming until you do have a clue. You should also come up with a design, as repairing malformed XML is not a trivial exercise.
my email is [email protected]
And don't ask for people to e-mail you clues. That's like cross-posting, only worse because we can't even know what other advice was offered.

Similar Messages

How to get the HTTP response body if the body is a malformed XML document

Hi,
I am using HTTP service with resultFormat = "e4x" set. What i
get in response is a malformed XML document in
some cases. Usually HTTPService throws a FaultEvent with the
fault detail set to faultCode:Client.CouldNotDecode
faultString:'Error #1091' or some other Error #1085 and so.
My client tries to log these errors on the server by using
another HTTP service again. But i would like to know
in the client code during run time what exact XML response
came in the first HTTP response.
How do i retrieve this information?
thanks,
Sunil

service capture or charles debug proxy can do the job.
flex builder 4 is rumored to include a traffic sniffer as
well, but that's next year.

Validating XML stored in CLOB without exceptions for malformed XML

Hello,
I have a CLOB column that should contain an XML which conforms to a registered XSD schema. However, there might also be cases, in which the CLOB content violates the XSD or is not even wellformed XML at all. Now I am trying to find a way to either
identify all records, for which the CLOB contains well-formed XML that validates against my schema (find all "good" records) , or
find all the other records (those with either no XML at all, malformed XML, or XML that does not validate against the XSD) (find all "exceptions")
The problem is that all XML-validation methods I know of (e.g. isXmlValid or XmlType.isSchemaValid) require an XmlType instance, and that records, for which no proper XmlType can be constructed from the CLOB, because the CLOB does not contain well-formed XML, will cause an exception, rather than just returning false or NULL or something else I could filter out.
Is there a way to do something like
SELECT * FROM MYTABLE where <MY_XML_COL is wellformed XML> and <MY_XML_COL validates against 'blabla.xsd'>
without getting an ORA-31011 or whatever other kind of exception as soon as there is a row that does not contain proper XML?
Thank you...

So here is my example - this will be quiet a long post now...
First, I create the table with the CLOBs
CREATE TABLE ZZZ_MINITEST_CLOB (
ID NUMBER(10,0) NOT NULL ENABLE,
XML_DOC CLOB,
REMARKS VARCHAR2(1000),
CONSTRAINT PK_ZZZ_MINITEST_CLOB PRIMARY KEY (ID)
) NOLOGGING;
Then I insert some examples
INSERT INTO ZZZ_MINITEST_CLOB VALUES (
10,
'<minitest_root>
<l2Node>
<l2Num>1</l2Num>
<l2Name>one.one</l2Name>
</l2Node>
<minitestId>1</minitestId>
<minitestName>One</minitestName>
</minitest_root>',
'Basic valid example');
INSERT INTO ZZZ_MINITEST_CLOB VALUES (
20,
'<minitest_root>
<l2Node>
<l2Num>1</l2Num>
<l2Name>two.one</l2Name>
</l2Node>
<minitestId>2</minitestId>

</minitest_root>',
'Invalid - minitestName element is missing');
INSERT INTO ZZZ_MINITEST_CLOB VALUES (
30,
'<minitest_root>
<l2Node>
<l2Num>1</l2Num>
<l2Name>three.one</l2Name>
</l2Node>

<minitestName>Three</minitestName>
<minitestId>3</minitestId>
</minitest_root>',
'Invalid - minitestName and minitestId are switched');
INSERT INTO ZZZ_MINITEST_CLOB VALUES (
40,
'<minitest_root>
<l2Node>
<l2Num>1</l2Num>
<l2Name>four.one</l2Name>
</l2Node>
<l2Node>
<l2Num>2</l2Num>
<l2Name>four.two</l2Name>
</l2Node>
<l2Node>
<l2Num>3</l2Num>
<l2Name>four.three</l2Name>
</l2Node>
<minitestId>4</minitestId>
<minitestName>Four</minitestName>
</minitest_root>',
'Valid - multiple l2Node elements');
INSERT INTO ZZZ_MINITEST_CLOB VALUES (
50,
'<minitest_root>
<l2Node>
<l2Num>1</l2Num>
<l2Name>five.one</l2Name>
</l2Node>
<l2Node>
<l2Num>2</l2Num>
<l2Name>five.two</l2Name>
</l2Node>
<minitestId>4</minitestId>
<minitestName>Five</minitestName>

<l2Node>
<l2Num>3</l2Num>
<l2Name>five.three</l2Name>
</l2Node>
</minitest_root>',
'Invalid - another l2Node node, but too far down');
INSERT INTO ZZZ_MINITEST_CLOB VALUES (
60,
'something that is not even xml',
'Invalid - something that is not even xml');
INSERT INTO ZZZ_MINITEST_CLOB VALUES (
70,
NULL,
'Invalid - good old NULL');
INSERT INTO ZZZ_MINITEST_CLOB VALUES (
80,
'<minitest_root>
<l2Node>
<l2Num>1</l2Num>
<l2Name>
<unexpected_node>
this one should not be here!
</unexpected_node>
</l2Name>
</l2Node>
<minitestId>8</minitestId>
<minitestName>Eight</minitestName>
</minitest_root>',
'Invalid - unexpected addl node');
INSERT INTO ZZZ_MINITEST_CLOB VALUES (
90,
'<something> that has tags but is no xml </either>',
'Invalid - something that has tags but is no xml either');
COMMIT;
Next I register the XSD...
BEGIN
DBMS_XMLSCHEMA.REGISTERSCHEMA(
'http://localhost/minitest.xsd',
'<?xml version="1.0" encoding="UTF-8"?>
<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema" elementFormDefault="qualified" xmlns:oraxdb="http://xmlns.oracle.com/xdb" oraxdb:storeVarrayAsTable="true" oraxdb:schemaURL="http://localhost/minitest.xsd">
<xs:element name="minitest_root" oraxdb:SQLName="MINITEST_ROOT" oraxdb:SQLType="MINITEST_TYPE" oraxdb:defaultTable="" oraxdb:tableProps="NOLOGGING" oraxdb:maintainDOM="false">
 <xs:complexType oraxdb:SQLType="MINITEST_TYPE" oraxdb:maintainDOM="false">
 <xs:sequence>
 <xs:element maxOccurs="unbounded" ref="l2Node" oraxdb:SQLName="L2_NODE" oraxdb:SQLType="L2_NODE_TYPE" oraxdb:SQLCollType="L2_NODE_COLL" oraxdb:maintainDOM="false"/>
 <xs:element ref="minitestId" oraxdb:SQLName="MINITEST_ID" oraxdb:SQLType="NUMBER" oraxdb:maintainDOM="false"/>
 <xs:element ref="minitestName" oraxdb:SQLName="MINITEST_NAME" oraxdb:SQLType="VARCHAR2" oraxdb:maintainDOM="false"/>
 </xs:sequence>
 </xs:complexType>
</xs:element>
<xs:element name="l2Node" oraxdb:SQLName="L2_NODE" oraxdb:SQLType="L2_NODE_TYPE" oraxdb:defaultTable="" oraxdb:tableProps="TABLESPACE CATALOG NOLOGGING" oraxdb:maintainDOM="false">
 <xs:complexType oraxdb:SQLType="L2_NODE_TYPE" oraxdb:maintainDOM="false">
 <xs:sequence>
 <xs:element ref="l2Num" oraxdb:SQLName="L2_NUM" oraxdb:SQLType="NUMBER" oraxdb:maintainDOM="false"/>
 <xs:element ref="l2Name" oraxdb:SQLName="L2_NAME" oraxdb:SQLType="VARCHAR2" oraxdb:maintainDOM="false"/>
 </xs:sequence>
 </xs:complexType>
</xs:element>
<xs:element name="l2Num" type="number10_0Type" oraxdb:SQLName="L2_NUM" oraxdb:SQLType="NUMBER" oraxdb:maintainDOM="false" />
<xs:element name="l2Name" type="varchar100Type" oraxdb:SQLName="L2_NAME" oraxdb:SQLType="VARCHAR2" oraxdb:maintainDOM="false" />
<xs:element name="minitestId" type="number10_0Type" oraxdb:SQLName="MINITEST_ID" oraxdb:SQLType="NUMBER" oraxdb:maintainDOM="false" />
<xs:element name="minitestName" type="varchar100Type" oraxdb:SQLName="MINITEST_NAME" oraxdb:SQLType="VARCHAR2" oraxdb:maintainDOM="false" />
<xs:simpleType name="varchar100Type">
 <xs:restriction base="xs:string">
 <xs:maxLength value="100"/>
 </xs:restriction>
</xs:simpleType>
<xs:simpleType name="number10_0Type">
 <xs:restriction base="xs:integer">
 <xs:totalDigits value="10"/>
 </xs:restriction>
</xs:simpleType>
</xs:schema>',
GENTABLES=>FALSE
END;
And then I create my XML tables - four different ones for four different test cases. I am trying unstructured binary XML and strucured OR-based XML, each with and without a trigger.
One with structured OR storage and no trigger
CREATE TABLE ZZZ_MINITEST_ORXML (
ID NUMBER(10,0) NOT NULL ENABLE,
XML_CONTENT XMLTYPE,
CONSTRAINT PK_ZZZ_MINITEST_ORXML PRIMARY KEY (ID)
) NOLOGGING
VARRAY "XML_CONTENT"."XMLDATA"."L2_NODE" STORE AS TABLE "ZZZ_OR_L2_NODE" (NOLOGGING) RETURN AS LOCATOR
XMLTYPE XML_CONTENT STORE AS OBJECT RELATIONAL XMLSCHEMA "http://localhost/minitest.xsd" ELEMENT "minitest_root";
One with structured OR storage which will also have a trigger added further down
CREATE TABLE ZZZ_MINITEST_ORXML_TRGR (
ID NUMBER(10,0) NOT NULL ENABLE,
XML_CONTENT XMLTYPE,
CONSTRAINT PK_ZZZ_MINITEST_ORXML_TRGR PRIMARY KEY (ID)
) NOLOGGING
VARRAY "XML_CONTENT"."XMLDATA"."L2_NODE" STORE AS TABLE "ZZZ_OR_L2_NODE_TRGR" (NOLOGGING) RETURN AS LOCATOR
XMLTYPE XML_CONTENT STORE AS OBJECT RELATIONAL XMLSCHEMA "http://localhost/minitest.xsd" ELEMENT "minitest_root";
One with unstructured binary XML in a SECUREFILE, no trigger
CREATE TABLE ZZZ_MINITEST_BINXML_TRGR (
ID NUMBER(10,0) NOT NULL ENABLE,
XML_CONTENT XMLTYPE,
CONSTRAINT PK_ZZZ_MINITEST_BINXML_TRGR PRIMARY KEY (ID)
) NOLOGGING
XMLTYPE COLUMN XML_CONTENT STORE AS SECUREFILE BINARY XML
(NOCOMPRESS NOCACHE NOLOGGING KEEP_DUPLICATES);
One with unstructured binary XML in a SECUREFILE, which will also have a trigger
CREATE TABLE ZZZ_MINITEST_BINXML (
ID NUMBER(10,0) NOT NULL ENABLE,
XML_CONTENT XMLTYPE,
CONSTRAINT PK_ZZZ_MINITEST_BINXML PRIMARY KEY (ID)
) NOLOGGING
XMLTYPE COLUMN XML_CONTENT STORE AS SECUREFILE BINARY XML
(NOCOMPRESS NOCACHE NOLOGGING KEEP_DUPLICATES);
Then I create the error logging tables
begin
DBMS_ERRLOG.CREATE_ERROR_LOG ('ZZZ_MINITEST_BINXML', 'ZZZ_MINITEST_BINXML_E', NULL, NULL, TRUE);
DBMS_ERRLOG.CREATE_ERROR_LOG ('ZZZ_MINITEST_BINXML_TRGR', 'ZZZ_MINITEST_BINXML_TRGR_E', NULL, NULL, TRUE);
DBMS_ERRLOG.CREATE_ERROR_LOG ('ZZZ_MINITEST_ORXML', 'ZZZ_MINITEST_ORXML_E', NULL, NULL, TRUE);
DBMS_ERRLOG.CREATE_ERROR_LOG ('ZZZ_MINITEST_ORXML_TRGR', 'ZZZ_MINITEST_ORXML_TRGR_E', NULL, NULL, TRUE);
END;
Now the two triggers
create or replace trigger TRG_ZZZ_MINITEST_BINXML
BEFORE UPDATE OR INSERT ON ZZZ_MINITEST_BINXML_TRGR
REFERENCING NEW AS NEW
for each row
BEGIN
:NEW.XML_CONTENT := :NEW.XML_CONTENT.createSchemaBasedXML('http://localhost/minitest.xsd');
:NEW.XML_CONTENT.SCHEMAVALIDATE();
END TRG_ZZZ_MINITEST_BINXML;
CREATE OR REPLACE TRIGGER TRG_ZZZ_MINITEST_ORXML
BEFORE UPDATE OR INSERT ON ZZZ_MINITEST_ORXML_TRGR
REFERENCING NEW AS NEW
for each row
BEGIN
:NEW.XML_CONTENT := :NEW.XML_CONTENT.createSchemaBasedXML('http://localhost/minitest.xsd');
:NEW.XML_CONTENT.SCHEMAVALIDATE();
END TRG_ZZZ_MINITEST_ORXML;
I also tried to just validate the XML using queries such as the below, since validating all without the WHERE also caused exception and abortion:
SELECT ID, DECODE(XMLISVALID(XMLTYPE(XML_DOC), 'http://localhost/minitest.xsd'), 1, 'Y', 0, 'N', '?') VALID
FROM ZZZ_MINITEST_CLOB WHERE ID=90;
The results are in column "VALID" in the below tables
I tried inserting all records from ZZZ_MINITEST_CLOB into the four test tables at once using a query such as
INSERT INTO ZZZ_MINITEST_ORXML_TRGR
SELECT ID, XMLPARSE(DOCUMENT XML_DOC WELLFORMED) FROM ZZZ_MINITEST_CLOB
LOG ERRORS INTO ZZZ_MINITEST_ORXML_TRGR_E REJECT LIMIT UNLIMITED;
I also tried different versions of creating the XML in the SELECT portion:
XMLPARSE(DOCUMENT XML_DOC WELLFORMED)
XMLPARSE(DOCUMENT XML_DOC WELLFORMED)
XMLTYPE(XML_DOC)
XMLTYPE(XMLDOC, 'http://localhost/minitest.xsd', 0, 1)
Almost all combinations of the four test tables with the four ways to instantiate the XML caused exceptions and query abortion despite the LOG ERRORS INTO clause.
In order to find the exact problems, I started inserting records one by one using queries like
INSERT INTO ZZZ_MINITEST_ORXML
SELECT ID, XMLPARSE(DOCUMENT XML_DOC) FROM ZZZ_MINITEST_CLOB WHERE ID=10
LOG ERRORS INTO ZZZ_MINITEST_ORXML_E REJECT LIMIT UNLIMITED;
or
INSERT INTO ZZZ_MINITEST_BINXML_TRGR
SELECT ID, XMLTYPE(XMLDOC, 'http://localhost/minitest.xsd', 0, 1) FROM ZZZ_MINITEST_CLOB WHERE ID=20
LOG ERRORS INTO ZZZ_MINITEST_BINXML_TRGR_E REJECT LIMIT UNLIMITED;
I captured the results of each in the below four tables. "1" and "0" are number of rows inserted. 0 means there was no record inserted and instead, there was an error logged in the ERROR LOGGING table.
The ORA-????? exception numbers mean that this error actually caused the INSERT to fail and abort rather than just being logged in the LOGGING TABLE.These are the most critical cases for me. Why do these exceptions "bubble up" forcing the query to be aborted rather than being logged in the error log as well???
This table is for INSERT of XMLs using XMLTYPE(XML_DOC)
Test case
VALID
Binary XML,
no trigger
Binary XML,
trigger
OR XML,
no trigger
OR XML,
trigger
10
Good
Y
1
1
1
1
20
no name
N
1
0
1
0
30
switched tags
N
1
1
1
1
40
Good
Y
1
1
1
1
50
L2 down
N
1
1
1
1
60
no xml
EX
ORA-31011
ORA-31011
ORA-31011
ORA-31011
70
NULL
EX
ORA-06502
ORA-06502
ORA-06502
ORA-06502
80
addl. Node
N
1
0
ORA-31187
ORA-31187
90
crappy xml
EX
ORA-31011
ORA-31011
ORA-31011
ORA-31011
This table is for INSERT of XMLs using XMLTYPE(XML_DOC, 'http://localhost/minitest.xsd', 0, 1)
Test case
VALID
Binary XML,
no trigger
Binary XML,
trigger
OR XML,
no trigger
OR XML,
trigger
10
Good
Y
1
1
1
1
20
no name
N
1
0
1
0
30
switched tags
N
1
1
1
1
40
Good
Y
1
1
1
1
50
L2 down
N
1
1
1
1
60
no xml
EX
ORA-31043
ORA-31043
ORA-31043
ORA-31043
70
NULL
EX
ORA-06502
ORA-06502
ORA-06502
ORA-06502
80
addl. Node
N
1
0
ORA-31187
ORA-31187
90
crappy xml
EX
ORA-31043
ORA-31043
ORA-31043
ORA-31043
This table is for INSERT of XMLs using XMLPARSE(DOCUMENT XML_DOC WELLFORMED)
Test case
VALID
Binary XML,
no trigger
Binary XML,
trigger
OR XML,
no trigger
OR XML,
trigger
10
Good
Y
1
1
1
1
20
no name
N
1
0
1
0
30
switched tags
N
1
1
1
1
40
Good
Y
1
1
1
1
50
L2 down
N
1
1
1
1
60
no xml
ORA-31061
0
ORA-31011
ORA-31011
70
NULL
1
0
1
0
80
addl. Node
N
0
0
ORA-31187
ORA-31187
90
crappy xml
ORA-31061
0
ORA-30937
ORA-30937
This table is for INSERT of XMLs using XMLPARSE(DOCUMENT XML_DOC) (same as above, but without "WELLFORMED")
Test case
VALID
Binary XML,
no trigger
Binary XML,
trigger
OR XML,
no trigger
OR XML,
trigger
10
Good
Y
1
1
1
1
20
no name
N
1
0
1
0
30
switched tags
N
1
1
1
1
40
Good
Y
1
1
1
1
50
L2 down
N
1
1
1
1
60
no xml
ORA-31011
ORA-31011
ORA-31011
ORA-31011
70
NULL
1
0
1
0
80
addl. Node
N
1
0
ORA-31187
ORA-31187
90
crappy xml
ORA-31011
ORA-31011
ORA-31011
ORA-31011
As you can see, different ways to instantiate the XML which is being inserted will cause different results for the most critical cases (60, 80 and 90). One will go through with an error logged in the logging table and no record inserted, others cause exceptions. Also, using XMLPARSE with or without WELLFORMED causes different ORA numbers for record 90...
It seems like the only way to not get any exceptions for my test records is inserting XMLs that were created using XMLPARSE (DOCUMENT ... WELLFORMED) into the trigger-protected binary XML table. However, that causes me to miss record number 80, which is one that I really need, because it is well formed and I could use XSLTs to fix the XML by removing the extra tags, as long as I know which ones those are.

Access denied - LOADXML Malformed XML Error

Hi everyone,
I am trying to navigate through some webDynpro ABAP component Methods each time I click on a method, a system message appears and it reads:
Access denied
And having the title LOADXML Malformed XML Error
This doesnu2019t happen on different machine neither my college PC.
Could somebody help?
Thanks,

I have found this threed usfule:
[Re: SAP GUI XML related error message and crash.;
and my problem is resolved now

Why Getting Malformed XML from DDX DocumentText

Hello,
I wanted to get DocumentText information on assembled PDF documents. Works fine ( load output DocumentText document in XML Editor without XML malformed error) when the source PDF documents does not contain reserved xml entities (for example & ). However, when the source PDF document contained xml reserved characters (for example the &), I could not successfully load the DocumentText XML document into the XML editor (the XML editor informs that the & character is not escaped. Thank you for any insight.
Regards, Jesse

and what JDK? Java didn't support SOCKS 5 until a certain point, sorry can't remember offhand. Check your release notes.

Malformed XML payload on RFC sender scenario

Hi all,
I'm trying to send data from RFC to XI but I got follow error in SXMB_MONI:
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>

<SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30"
xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="">
<SAP:Category>Application</SAP:Category>
<SAP:Code area="MAPPING">EXCEPTION_DURING_EXECUTE</SAP:Code>
<SAP:P1>com/sap/xi/tf/_mm_ZFI_RFC_CADASTRO_FORNECEDOR_To_~</SAP:P1>
<SAP:P2>com.sap.aii.utilxi.misc.api.BaseRuntimeException</SAP:P2>
<SAP:P3>Fatal Error: com.sap.engine.lib.xml.parser.Parser~</SAP:P3>
<SAP:P4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>com.sap.aii.utilxi.misc.api.BaseRuntimeException thrown during application mapping
com/sap/xi/tf/_mm_ZFI_RFC_CADASTRO_FORNECEDOR_To_~: Fatal Error: com.sap.engine.lib.xml.parser.Parser~</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
When open XML payload the structure and fields are ok but data on these fields is not, some data from one field is concatenate on another field and other case data is in different field. For example on field KUNNR, data sent by RFC on R/3 is '1000000386' But on PI the XML looks like that:
<?xml version="1.0" encoding="UTF-8" ?>
<rfc:ZFI_RFC_CADASTRO_FORNECEDOR xmlns:rfc="urn:sap-com:document:sap:rfc:functions">
<T_LFA1>
<item>
<LIFNR>0000386</LIFNR>
And in some fields that expect telephone number, on XML is like that:
<TELFX> & #00;& #00;& #00;& #00;& #00;& #00;& #00;& #12;</TELFX>
(I HAVE TO INSERT SPACE BETWEEN & and #00; )
These codes generate the error com.sap.engine.lib.xml.parser.Parser~ on mapping program.
I've tried to re-import RFC and full cache refresh but I think that error is on JCO on java stack when converting RFC call to XML. I've looked for some RFC Adapter and JCO configuration on Visual Administrator but everything looks ok.
My system is:
SAP PI 7.0 SP13
SAP ECC 6.0
Any idea how to solve this issue?
Thanks!
Edited by: Daniel Torres on Nov 5, 2008 2:12 PM

Hi,
As you can see mapping is because of Mapping , Exception During Execute come because of mapping error. So if you doing some graphical mapping there as you said you are concatenating some values passed from SAP R/3 in mapping , check it. Rather you can also check your mapping is right ot wrong using Test tab in mapping editor. also you can use Interface mapping for testing your whole scenario, i will prefer Interface Mapping thing to test my scenario as it will tell you if your requeswt mapping is correct or response message is correct.
Lets check there and you will see exact problem of mapping.
Regards
Aashish Sinha

Org.xml.sax.SAXParseException

Hi All,
I am trying to parse an xml file whcih contains some special characters like "&" using DOM parser.
So, i am gtting the saxparse exception "The reference to entity "T" must end with the ';' delimiter"
Is there any way to overcome this exception, since i could not modify the xml file to remove the special characters, since it is coming from different application.
Pls suggest a way to parse this xml file to get the root element?
My XML contains:
Net: J^l 
Total: JL'J 
*<Figure ActualText="&T ">*
<ImageData src="images/17PT 07009K_img_1.jpg"/>
&T </Figure>
Checked by 
Thanks in advance...

It appears that this "other application" is generating malformed XML. Apparently its author did not code it to escape ampersands in text elements correctly.
There is no way for you to parse that. You will have to get the other application fixed.

XML SAX parser that support LexicalHandler

Hello,
I'm looking for an XML SAX parser that support a LexicalHandler.
I have xml files that are not well formed, ie: (&, <, >, etc...) characters within tags and I need to ignore them.
Anyone have a link to some opensource library ??
Thanks,
Samir

Don't waste your time. Using a LexicalHandler isn't going to help with parsing malformed XML. You should get the person who produced those files to replace them with correct XML.
PC²

Generate XML - Special Character in data causing error

Hello,
I have a procedure written using DBMS_XMLGEN to create xml output. A problem that I am running into is some of my data has an eacute in it. How can I code the XML to account for this and any other weird characters that may exist?
(ie - i need to be able to specify the encoding part of ?xml version=1.0 encoding=ISO-8859-1?)
Here is an excerpt of what i have so far...the results are fine until I run to include the data with the eacute. Then nothing is generated at all. I tried .convert, but I don't know if that's what I need, or if I am calling it correctly.
Thanks!
Janel
ctx := dbms_xmlgen.newContext(rc_data);
-- set name of root element --
dbms_xmlgen.setRowsetTag(ctx, 'XXFA10022');
-- set name of element separating all rows --
-- default is ROW --
dbms_xmlgen.setRowTag(ctx, 'G_DATA');
-- generate XML document --
xml := dbms_xmlgen.getXml(Ctx);
xml := dbms_xmlgen.convert(xml, dbms_xmlgen.ENTITY_ENCODE);
i := dbms_xmlgen.getNumRowsProcessed(ctx);
dbms_xmlgen.closeContext(Ctx);
apps.fnd_file.put_line(apps.fnd_file.log, 'rows processed -' || i);
apps.fnd_file.put_line(apps.fnd_file.log, 'close');
apps.fnd_file.put_line(apps.fnd_file.log, xml);
apps.fnd_file.put_line(apps.fnd_file.output, xml);
-- free clob content --
dbms_lob.freetemporary(xml);

No. There are no XML components that will clean up malformed XML. Your options are to go to whoever sent you that document and tell them that their XML is malformed and that in future they should not do that, or to write your own component to clean up the malformed XML. Since that would involve more work than writing a full XML parser, I don't recommend the second option.

Writing a large xml string to a file

Hi,
I get a large xml file, into a String (It might be around 8 MB also). After this, I need to write this to a file. Which java method I can use for the same.
I am getting confused by the various classes for writing a file.
I want to use the best, efficient way of doing this. Can any one please help?
public static void writeStringToFile( String fileName, String content,
          boolean append )
          throws FileNotFoundException, IOException
          FileOutputStream fos = null;
          File file = new File (fileName);
          try {
//++ fos = new FileOutputStream( file);
      fos = new FileOutputStream( file, append );                 //++
               fos.write(getBytes(content));
          } catch (FileNotFoundException fne) {
               throw fne;
          } catch (IOException ioe) {
               throw ioe;
          } finally {
               try {
               if(fos != null)
                    fos.close();
               } catch (Exception _ex) {
     }

hi_all wrote:
But is there any any particular reason for using the encoding specific to xml?Yes, because that's what the XML specification says you're supposed to do. If you don't do that then you may produce malformed XML.
Will there be any perf degrade or truncation of the large string, while writing to the file, if we use,
out.write(sigUpdateString);Compared to what? You're just writing the data out to a file, the quickest way to do that is to just write the data out. The two things you should do are: (1) use a BufferedWriter (2) stop obsessing about performance.

Using XML as plain text in TextFilter

I have an application with an XML tag:
<mx:XML id="textXML1">
<root><c1>goodbye</c1></root>
</mx:XML>
I then have a string variable which I set equal to that XML:
var t:String = textXML1;
I then set up a TextFlow by the following line of code:
textFlow = TextFilter.importToFlow(t,
TextFilter.PLAIN_TEXT_FORMAT);
However, I then do a trace of the text value in the TextFlow:
trace("textFlow's text: " + TextUtil.extractText(textFlow));
The resultant dump is:
textFlow's text: <root>
<c1>goodby
<c1>goodbye
Any ideas?

Yes, the XML.toString() method is called. This means that t
is the result of textXML1.toString(), which, on complex XML,
produces a string of the entire XML object, tags and all. If I do a
trace on t, the output is:
<root>
<c1>goodbye</c1>
</root>
That is expected. That also means that the value of "t" is no
longer XML, just a string that looks like XML.
What is unexpected is the malformed "xml" string produced
when it's been handled by the TLF. If you note from my first post,
the result of
TextUtil.extractText(textFlow) is not the entire "xml"
string, but rather a malformed version of it. I'm assuming this is
a bug in either
TextFilter.importToFlow() or
TextUtil.extractText(), but, since there are no exposed
variables/properties on the TextFlow's text (if it has such a
variable at all), I have no way of knowing where this is breaking
down.

Large XML Document Error

We are using Oracle's XSQL servlet engine 9.0.2.0.0A to query an Oracle Database using xsql:include-owa. This xsql document uses a custom serializer to write the resulting XML to a file on the webserver. We have run into a problem with writing XML documents larger than approximatly 7MB. The file is written but just contains a Malformed XML Document error. We have tried tracking down the problem and it seems to be occuring before the custom serializer is given control of the document. Attached below is the xsql document and the Java source of our serializer if it would be of any help.
-Eric Dalquist
<?xml version="1.0"?>
<?xml-stylesheet type="text/xsl" href="simple_transform_xml.xsl" serializer="XMLWriter"?>
<BASE_TAG connection="XXXXXXXX" xmlns:xsql="urn:oracle-xsql">
 <xsql:set-page-param name="save-file" value="XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX/applInfo.xml"/>
 <xsql:include-owa >
 STUDEV.STUADMSDSET.P_GET_RECRUIT_INFO('A','C');
 </xsql:include-owa>
</BASE_TAG>-----------------------------------------
* Author: Eric Dalquist
* E-Mail: [email protected]
* Date Created: 10-03-2001
* Last Modified: 10-03-2001
* Modified By: Eric Dalquist
* Description: This class writes out the contents of the final document produced by the xsql servlet.
package com.mtu.XSQLSerializers;
import java.io.FileOutputStream;
import oracle.xml.xsql.*;
import oracle.xml.parser.v2.XMLDocument;
import org.w3c.dom.Document;
* 
* XMLWriter is an implementation of the abstract XSQLDocumentSerializer class. It is passed a refrence to a DOM Document
* and the servlet environment. The XMLWriter takes the document and writes it out to the servlet's output stream. There
* is also the option that the saveFile xsql page parameter can be set to a fully qualified path and file name to write the
* document to.
* 
* 
* Here is an example of setting the saveFile page paramter. This line would be the first tag inside the root xsql servlet tag.
* 
* <PRE>
* <xsql:set-page-param name="save-file" value="/u01/oracle/ias10210/xdk/java/xsql/Repository/Course_List/XMLDocument.xml"/>
* </PRE>
* @author Eric B. Dalquist
* @version 1.0 10/03/2001
public class XMLWriter implements XSQLDocumentSerializer
 /** the header we send if we are returning XML */
 private static final String MIME_XML = "text/xml";
 /** the name of the page parameter we look for to get the path and name to save the XML document to */
 private static final String ATTR_FILE = "save-file";
 * The serialize is called by the servlet engine and is passed the DOM Docuement result
 * from the XSLT transformation if there was one and a refrence to the XSQL servlet environment
 * @param doc The document representation of the XML output of the xsql servlet.
 * @param env A refrence to the servlet's environment.
 * @throws Throwable Any unhandled error is handled by the servlet by default.
 public void serialize(Document doc, XSQLPageRequest env) throws Throwable
 System.out.print("start ... ");
 FileOutputStream fos = null;
 String reqType = env.getRequestType();
 String saveFile = env.getParameter(ATTR_FILE);
 if (!reqType.equals("Command Line"))
 env.setContentType(MIME_XML);
 ((XMLDocument)doc).print(env.getOutputStream());
 env.getOutputStream().close();
 if (saveFile != null && !saveFile.equals("") && saveFile.indexOf("..") == -1 && saveFile.indexOf("~") == -1)
 fos = new FileOutputStream(saveFile);
 ((XMLDocument)doc).print(fos);
 fos.close();
 System.gc();
 System.out.println("end");
}

Technically DBMS_XMLSAVE and it's alter ego DBMS_XMLQUERY are not considered part of XML DB. DBMS_XMLSAVE and DBMS_XMLQUERY are legacy Java implementations.
In 9.2.x these routines were replaced by DBMS_XMLSTORE and DBMS_XMLGEN which are written in 'C' and should be much faster in most cases and address a number of limitations inherant in the older implementations. DBMS_XMLSTORE and DBMS_XMLGEN are part of XML DB and the minimum supported release for XML DB is 9.2.0.3.0.
DBMS_XMLSAVE issues are addressed in the TECH/XML forum
http://forums.oracle.com/forums/category.jspa?categoryID=51

Invalid XML character in web service answer of MS Exchange

Hello Forum!
We have to look up contacts in the global address list of a Microsoft Exchange server.
The current solution uses the web services that have been introduced in version 2007 of MS Exchange.
Unfortunately some records returned by the MS Server cause a javax.xml.stream.XMLStreamException. The Exception
tells us that a parser error occurred. The Exception says:
Message: Character reference "&#x7" is an invalid XML character.
The Java classes used for accessing the Exchange web services are generated using the jaxws plugin and the application
is running on the Glassfish application server v2 ur1.
The only solution we can think of right now is to access the XML stream returned by the Exchange server before it is handed over
to the parser in order to replace the invalid characters.
Can anyone point me to some documentation or give me an example of how to intercept the XML parsing process used by the jaxws
component?
Any other ideas for a solution are of course also appreciated.
Thanks for your help in advance,
Henning Malzahn

hm@collogia wrote:
In addition to that MS is not very responsive when it comes to Java questions.Yes, but "Your software is producing malformed XML" is not a Java question.
I can imagine that filtering the stream isn't very easy - are you able to provide some links to additional
information that can help us getting started in that direction?A subclass of FilterInputStream whose read() method calls the superclass's read() method a second time when the input is between 0 and 19, or whatever are the invalid XML characters?

Detection of encoding of XML file with the StAX parser

Hello!
I am using the StAX parser to read an XML file which can have different encodings.
I don't know how to detect the encoding before reading the file.
This is the way I instantiate the reader now:
XMLStreamReader xmlr = xmlif.createXMLStreamReader(new InputStreamReader (new FileInputStream(inputfile), "utf-8"));
Is there any way to make the reader detect the encoding with StAX? Is it possible detect the encoding with SAX or DOM?
Just paste some piece of code and you will help me a lot!
Thanks,
Lara

XML parsers are supposed to auto-detect the encoding of their inputs. The SAX and DOM parsers built into Java, as well as others like Xerces, do that. I don't know whether your StAX parser does, but it should. There is a standard procedure for determining the encoding that is described in the XML spec.
However if you have malformed XML that fails to declare its encoding properly, then none of those parsers will be able to fix that problem for you.
Here's the simplified rule as it applies to most files: if the XML file doesn't have a prolog, or if it's prolog doesn't specify an encoding, the parser will assume the file's encoding is UTF-8. If the XML file does have a prolog that specifies an encoding, the parser will assume that encoding.
Unfortunately it is common for people to write XML files that don't declare an encoding, but to forget to encode the file in UTF-8. Then you have a file that is actually encoded in (e.g.) Windows-1252, but the parser believes it is UTF-8, and this fails when there are non-ASCII characters in the document.

Osb: Proxy Messaging Service retrieve only xml message that have the proper

Hi All.
I have a Proxy Service with Messaging Service type which read xml messages from a queue.
The Request Message Type in the proxy is xml and I have provided the type information by declaring (in the element and type field) the XML schema type of the XML document exchanged.
I need the proxy service to retrieve from the queue only the xml messages that have the proper schema.
But when the proxy retrieves any xml msg in the queue regardless of their schema definition .
Appreciate your input.
Thx,
Ross
Edited by: user6677631 on Feb 25, 2013 9:52 AM
Edited by: user6677631 on Feb 25, 2013 10:02 AM

Selecting the XML schema for request type in a messaging proxy does not ensure the validation of incoming XML message against schema. Similarly if you create a WSDL based proxy the validation against WSDL definition will not happen automatically. Choosing XML as the type of message will only ensure that any malformed XMLs will be rejected before entering the message flow. For validating against schema you will need to explicitly add a validate action within the proxy message flow, if validation fails raise an error and roll back the message to the Queue or log the errored message and commit the message/publish to an error queue.

Malformed XML

Similar Messages

Maybe you are looking for