Users of the Xerces-J Java XML parser can meet and discuss questions, raise issues, etc.

Benjamin Keil | 1 May 2006 03:54

Validating a document against a schema that contains inline SVGs

Hello all,

  I'm trying to put together a schema that would allow inline SVG
elements, but I'm having a lot of trouble making this work.

The main problem seems to be coming from the SVG schema
(from http://www.w3.org/TR/2002/WD-SVG11-20020108/SVG.xsd )

I am loading documents like this:

DocumentBuilderFactory factory = new
org.apache.xerces.jaxp.DocumentBuilderFactoryImpl();
factory.setFeature("http://apache.org/xml/features/validation/schema",
true);
factory.setFeature("http://xml.org/sax/features/validation", true);	
factory.setFeature("http://xml.org/sax/features/namespaces", true);
factory.setNamespaceAware(true);

DocumentBuilder builder = factory.newDocumentBuilder();
Document doc = builder.parse(source);

Even trying to validate a little document like this:

<?xml version="1.0" encoding="UTF-8"?>
<svg:svg height="10cm" width="11cm" viewBox="0 0 1100 1000"
xmlns:svg="http://www.w3.org/2000/svg"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
	xsi:schemaLocation="http://www.w3.org/2000/svg svg.xsd ">

	<svg:rect x="1" y="1" width="1098" height="998" fill="none"

(Continue reading)

headers

Michael Glavassevich | 1 May 2006 04:44

Re: Validating a document against a schema that contains inline SVGs

Benjamin Keil <bkeil <at> humnet.ucla.edu> wrote on 04/30/2006 09:54:01 PM:

> Hello all,
> 
>   I'm trying to put together a schema that would allow inline SVG
> elements, but I'm having a lot of trouble making this work.
> 
> The main problem seems to be coming from the SVG schema
> (from http://www.w3.org/TR/2002/WD-SVG11-20020108/SVG.xsd )

This schema document has a DTD (XMLSchema.dtd) which references another 
document (datatypes.dtd) that doesn't exist at the specified location. The 
working draft of SVG [1] you're using says: "this schema is still in 
development and is being tested" so it's possible there were other 
problems with this version.

error: Parse error occurred - 
http://www.w3.org/TR/2002/WD-SVG11-20020108/datatypes.dtd
java.io.FileNotFoundException: 
http://www.w3.org/TR/2002/WD-SVG11-20020108/datatypes.dtd
        at 
sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:682)
        at 
org.apache.xerces.impl.XMLEntityManager.setupCurrentEntity(XMLEntityManager.java:959)
        at 
org.apache.xerces.impl.XMLEntityManager.startEntity(XMLEntityManager.java:871)
        at 
org.apache.xerces.impl.XMLEntityManager.startEntity(XMLEntityManager.java:809)
        at 
org.apache.xerces.impl.XMLDTDScannerImpl.startPE(XMLDTDScannerImpl.java:640)

(Continue reading)

headers

Prashant | 1 May 2006 06:13

Re: Validating a document against a schema that contains inline SVGs


>Hello all,
>
><snip>
>
>I am loading documents like this:
>
>DocumentBuilderFactory factory = new
>org.apache.xerces.jaxp.DocumentBuilderFactoryImpl();
>factory.setFeature("http://apache.org/xml/features/validation/schema",
>true);
>factory.setFeature("http://xml.org/sax/features/validation", true);	
>factory.setFeature("http://xml.org/sax/features/namespaces", true);
>factory.setNamespaceAware(true);
>
>DocumentBuilder builder = factory.newDocumentBuilder();
>Document doc = builder.parse(source);
>
>Even trying to validate a little document like this:
>
><?xml version="1.0" encoding="UTF-8"?>
><svg:svg height="10cm" width="11cm" viewBox="0 0 1100 1000"
>xmlns:svg="http://www.w3.org/2000/svg"
>xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
>	xsi:schemaLocation="http://www.w3.org/2000/svg svg.xsd ">
>
>	<svg:rect x="1" y="1" width="1098" height="998" fill="none"
>stroke="blue" stroke-width="2" />
>
></svg:svg>

(Continue reading)

headers

Prashant | 1 May 2006 06:17

Re: Validating a document against a schema that contains inline SVGs

Oops!

    xsi:schemaLocation="http://www.w3.org/2000/svg svg.xsd

does contain the schema location hint and target namespace. I should 
have been paying more attention. :)

-Prashant

Prashant wrote:

>
>> Hello all,
>>
>> <snip>
>>
>> I am loading documents like this:
>>
>> DocumentBuilderFactory factory = new
>> org.apache.xerces.jaxp.DocumentBuilderFactoryImpl();
>> factory.setFeature("http://apache.org/xml/features/validation/schema",
>> true);
>> factory.setFeature("http://xml.org/sax/features/validation", true);   
>> factory.setFeature("http://xml.org/sax/features/namespaces", true);
>> factory.setNamespaceAware(true);
>>
>> DocumentBuilder builder = factory.newDocumentBuilder();
>> Document doc = builder.parse(source);
>>
>> Even trying to validate a little document like this:

(Continue reading)

headers

Jeff.Barton | 2 May 2006 18:58

NullPointerException when calling Document.importNode(Node importedNode,boolean deep)

I’m hoping someone can give me some insight to an issue that is currently stalling a development project. In summary, I need to insert a pre-existing XML document fragment in to another XML document. I have tried to do this insertion by first using the importNode() operation on the org.w3c.dom.Document interface followed by an appendChild() operation from the org.w3c.dom.Node interface on the new owner document. When I attempt these operations I receive a NullPointException that is being generated by an underlying Xerces implementation. The code below generates the Exception:

public void insertNode(SOAPMessage message, Context context)

{

// This is the Node that needs to be inserted in the new “Owner” document. The content of the node can be seen below

Node wsseNode = (Node)sessionContext.getSessionAttribute(ISessionContext.WSSE_NODE_KEY);

// This Node is present and this print statement never executes

if (wsseNode == null)

System.out.println(ErrorFormatter.formatLogMessage(this.getClass(),"wsse:Security Node IS NULL",ErrorFormatter.ERROR));

else

{

Node importedNode = null;

// soapMessage is not null and the following code block always executes

if (message != null)

{

Element header = message.getHeader();

if (header == null)

header = message.addHeader();

Document doc = message.getDocument();

try

{

// this call generates the NullPointException. The wsseNode is not null and its presence has been verified by multiple means

// the method never proceeds beyond this point.

ImportedNode = doc.importNode(wsseNode,true);

}

catch (DOMException de)

{System.out.println(ErrorFormatter.formatErrorMessage(this.getClass(),de));}

header.appendChild(importedNode);

}

else

System.out.println(ErrorFormatter.formatLogMessage(this.getClass(),"SOAPMessage IS NULL",ErrorFormatter.ERROR));

}

This is the resulting stack trace:

Exception in thread "main" java.lang.NullPointerException

at org.apache.xerces.dom.CoreDocumentImpl.importNode(Unknown Source)

at com.gxs.common.webservice.security.SAMLSerializationInterceptor.intercept(SAMLSerializationInterceptor.java:61)

at electric.soap.util.SOAPInterceptors.callInterceptors(Unknown Source)

at electric.soap.references.interceptor.InterceptorSOAPReference.handle(Unknown Source)

at electric.soap.java.reference.JavaToSOAP.handle(Unknown Source)

at electric.soap.java.reference.JavaToSOAP.invoke(Unknown Source)

at electric.proxy.handler.Proxy.invoke(Unknown Source)

at $Proxy0.testProcess(Unknown Source)

at com.gxs.saml.test.SAMLTestClient.<init>(SAMLTestClient.java:54)

at com.gxs.saml.test.SAMLTestClient.main(SAMLTestClient.java:66)

The XML Node that I’m trying to insert is:

<wsse:Security xmlns:wsse='http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd'>

<saml:Assertion AssertionID='id-5a344e56a77d5f8b88fba7adf1a5e9578edf3cec' IssueInstant='2006-04-05T19:40:00.869Z' Issuer='http://www.forumsys.com/sentry' MajorVersion='1' MinorVersion='1' xmlns:saml='urn:oasis:names:tc:SAML:1.0:assertion'>

<saml:Conditions NotBefore='2006-04-05T19:40:00.869Z' NotOnOrAfter='2006-04-05T19:41:00.869Z'></saml:Conditions>

<saml:AuthenticationStatement AuthenticationInstant='2006-04-05T19:40:00.869Z' AuthenticationMethod='urn:oasis:names:tc:SAML:1.0:am:password'>

<saml:Subject>

<saml:NameIdentifier Format='urn:oasis:names:tc:SAML:1.1:nameid-format:X509SubjectName'> 1.2.840.113549.1.9.1=#16167062656e656e736f6e40666f72756d7379732e636f6d,CN=Pasha Benenson,C=US</saml:NameIdentifier>

<saml:SubjectConfirmation>

<saml:ConfirmationMethod>urn:oasis:names:tc:SAML:1.0:cm:sender-vouches</saml:ConfirmationMethod>

</saml:SubjectConfirmation>

</saml:Subject>

<saml:SubjectLocality IPAddress='10.160.37.108'></saml:SubjectLocality>

</saml:AuthenticationStatement>

<saml:AttributeStatement>

<saml:Subject>

<saml:NameIdentifier Format='urn:oasis:names:tc:SAML:1.1:nameid-format:X509SubjectName'>1.2.840.113549.1.9.1=#16167062656e656e736f6e40666f72756d7379732e636f6d,CN=Pasha Benenson,C=US</saml:NameIdentifier>

<saml:SubjectConfirmation>

<saml:ConfirmationMethod>urn:oasis:names:tc:SAML:1.0:cm:sender-vouches</saml:ConfirmationMethod>

</saml:SubjectConfirmation>

</saml:Subject>

<saml:Attribute AttributeName='IM_UserID' AttributeNamespace='http://www.forumsys.com/sentry'>

<saml:AttributeValue>GCP4444449999</saml:AttributeValue>

</saml:Attribute>

<saml:Attribute AttributeName='IM_FirstName' AttributeNamespace='http://www.forumsys.com/sentry'>

<saml:AttributeValue>Donald</saml:AttributeValue>

</saml:Attribute>

<saml:Attribute AttributeName='IM_MiddleInitials' AttributeNamespace='http://www.forumsys.com/sentry'>

<saml:AttributeValue>M</saml:AttributeValue>

</saml:Attribute>

<saml:Attribute AttributeName='IM_LastName' AttributeNamespace='http://www.forumsys.com/sentry'>

<saml:AttributeValue>Duck</saml:AttributeValue>

</saml:Attribute>

<saml:Attribute AttributeName='IM_BUID' AttributeNamespace='http://www.forumsys.com/sentry'>

<saml:AttributeValue>GC7777888888</saml:AttributeValue></saml:Attribute>

<saml:Attribute AttributeName='IM_PreferredLanguage' AttributeNamespace='http://www.forumsys.com/sentry'>

<saml:AttributeValue>en</saml:AttributeValue>

</saml:Attribute>

<saml:Attribute AttributeName='IM_TimeZone' AttributeNamespace='http://www.forumsys.com/sentry'>

<saml:AttributeValue>America/Los Angelos</saml:AttributeValue>

</saml:Attribute>

<saml:Attribute AttributeName='IM_UserEmail' AttributeNamespace='http://www.forumsys.com/sentry'>

<saml:AttributeValue>donald.duck <at> disney.com</saml:AttributeValue>

</saml:Attribute>

<saml:Attribute AttributeName='IM_Country' AttributeNamespace='http://www.forumsys.com/sentry'>

<saml:AttributeValue>US</saml:AttributeValue>

</saml:Attribute>

<saml:Attribute AttributeName='IM_CommunityID' AttributeNamespace='http://www.forumsys.com/sentry'>

<saml:AttributeValue>GCM65405</saml:AttributeValue>

</saml:Attribute>

</saml:AttributeStatement>

<saml:AuthorizationDecisionStatement Decision='Permit' Resource='WebService_Authorization'>

<saml:Subject>

<saml:NameIdentifier Format='urn:oasis:names:tc:SAML:1.1:nameid-format:X509SubjectName'>1.2.840.113549.1.9.1=#16167062656e656e736f6e40666f72756d7379732e636f6d,CN=Pasha Benenson,C=US</saml:NameIdentifier>

<saml:SubjectConfirmation>

<saml:ConfirmationMethod>urn:oasis:names:tc:SAML:1.0:cm:sender-vouches</saml:ConfirmationMethod>

</saml:SubjectConfirmation>

</saml:Subject>

<saml:Action Namespace='urn:oasis:names:tc:SAML:1.0:action:rwedc-negation'>Execute</saml:Action>

</saml:AuthorizationDecisionStatement>

</saml:Assertion>

</wsse:Security>

Are there limitations to the complexity of the Node that you can import? I tried the import operation with a simple parent/single child xml document and the import() operation worked successfully.

Am I using the importNode() operation in an inappropriate way?

If so, what are my alternatives for inserting an xml fragment from one document to another?

If not, what changes do I need to make to accomplish this activity?

I am using the xml-apis.jar and xercesImpl.jar files from the 2.7 release of Xalan.

Thanks in advance for any help!

Jeff

headers

Joseph Kesselman | 2 May 2006 20:30

Re: NullPointerException when calling Document.importNode(Node importedNode,boolean deep)

You might want to try running this under a debugger to see what field is
actually coming up as null. I'd be inclined to suspect that the node you're
importing from is damaged and/or otherwise isn't properly implementing the
DOM APIs, hence is returning null at a time when null isn't expected.

If not, then we may have a bug in the importNode implementation. But
determining exactly what's failing is the first step in determining whether
the problem is in the source DOM or sink DOM.

______________________________________
"... Three things are most perilous: Connectors that corrode,
  Unproven algorithms, and self-modifying code! ..."
  -- "Threes" Rev 1.1 - Duane Elms / Leslie Fish
(http://www.ovff.org/pegasus/songs/threes-rev-11.html)

headers

Crain, David B. (LNG-DAY | 5 May 2006 21:54

I am currently having a problem with entities in a DOM Parser

Code:

domParser.setFeature(“http://apache.org/xml/features/validation/schema”, false);

domParser.setFeature(“http://apache.org/xml/features/dom/create-entity-ref-nodes”, false);

With this configuration, and using Xerces 2.2.1, anytime the parser encounters an entity that is not defined in the DTD, we get the following results:

Input: properly elected to do so, can amend its &bogus; Federal income tax returns filed

Output: Federal income tax returns filed

Ran a test with a newer version of Xerces (2.6.0) and got a slightly different result:

Input: properly elected to do so, can amend its &bogus; Federal income tax returns filed

Output: properly elected to do so, can amend its Federal income tax returns filed

In either case, this is not a good thing.

I am looking for method that would allow me to keep the above features set the way they are, but code a method that would allow me identify an undefined entity in the data.

I am also curious why the Xerces code would not throw an exception when the above data is encountered. I am will to go to 2.8.0 Xerces if this problem was addressed.

Let me re-state, I want the code to throw an exception!!!!

Please let me know if there are any questions.

Dave

David B. Crain
Consultant Software Engineer
Editorial & Conversion Systems
Lexis-Nexis
Phone: 937-865-6800 ext. 56303

headers

Michael Glavassevich | 6 May 2006 20:04

Re: I am currently having a problem with entities in a DOM Parser

Dave,

A reference to an undeclared entity isn't always a well-formedness error 
[1]. I suspect your document has an external DTD, in which case you need 
to enable DTD validation and register an error handler to be notified that 
your document references an undeclared entity [2]. You can throw an 
exception from your error handler if you want the parser to stop.

Thanks.

[1] http://www.w3.org/TR/2004/REC-xml-20040204/#wf-entdeclared
[2] http://www.w3.org/TR/2004/REC-xml-20040204/#vc-entdeclared

Michael Glavassevich
XML Parser Development
IBM Toronto Lab
E-mail: mrglavas <at> ca.ibm.com
E-mail: mrglavas <at> apache.org

"Crain, David B. \(LNG-DAY\)" <David.Crain <at> lexisnexis.com> wrote on 
05/05/2006 03:54:16 PM:

> Code:
>                         domParser.setFeature(?http://apache.
> org/xml/features/validation/schema?, false);
>                         domParser.setFeature(?http://apache.
> org/xml/features/dom/create-entity-ref-nodes?, false);
> 
> With this configuration, and using Xerces 2.2.1, anytime the parser 
> encounters an entity that is not defined in the DTD, we get the 
> following results:
> Input:                properly elected to do so, can amend its &bogus;
> Federal income tax returns filed
> Output:             Federal income tax returns filed
> 
> Ran a test with a newer version of Xerces (2.6.0) and got a slightly
> different result:
> Input:                properly elected to do so, can amend its &bogus
> ; Federal income tax returns filed
> Output:             properly elected to do so, can amend its 
> Federal income tax returns filed
> 
> In either case, this is not a good thing. 
> 
> I am looking for method that would allow me to keep the above 
> features set the way they are, but code a method that would allow me
> identify an undefined entity in the data. 
> 
> I am also curious why the Xerces code would not throw an exception 
> when the above data is encountered. I am will to go to 2.8.0 Xerces 
> if this problem was addressed. 
> 
> Let me re-state, I want the code to throw an exception!!!!
> 
> Please let me know if there are any questions. 
> 
> Dave 
> 
> David B. Crain 
> Consultant Software Engineer 
> Editorial & Conversion Systems 
> Lexis-Nexis 
> Phone: 937-865-6800 ext. 56303

headers

Kopic Benjamin | 8 May 2006 15:35

Offline validation works on MS Windows but fails under Linux

Hi

We use Xerces J 2.7.1 to process XML files that validate against XML Schemata. However, the offline validation fails when run on Linux, although it works fine under MS Windows 2000. The API we use is dom4j (http://www.dom4j.org/) and JAXP, but I doubt that the problem is in those APIs.

This is the code snippet that does the validation:

reader.setXMLReaderClassName("org.apache.xerces.parsers.SAXParser");
reader.setFeature("http://apache.org/xml/features/validation/schema", true);

String mpdSchemaSource = System.getProperty("mpd-eph");
String messageheaderSchemaSource = System.getProperty("messageheader-eph");

String JAXP_SCHEMA_SOURCE = "http://java.sun.com/xml/jaxp/properties/schemaSource";
String JAXP_SCHEMA_LANGUAGE = "http://java.sun.com/xml/jaxp/properties/schemaLanguage";
String W3C_XML_SCHEMA = "http://www.w3.org/2001/XMLSchema";

try {
// retrieve schemata as InputStream from CLASSPATH
java.io.InputStream _mpd = getClass().getClassLoader().getResourceAsStream(mpdSchemaSource);
java.io.InputStream _mh = getClass().getClassLoader().getResourceAsStream(messageheaderSchemaSource);
java.io.InputStream[] _schemas = { _mpd, _mh };

reader.setProperty(JAXP_SCHEMA_SOURCE, _schemas);
reader.setProperty(JAXP_SCHEMA_LANGUAGE, W3C_XML_SCHEMA);
}
catch (Exception ex) {
// log the error
}

reader.read(fileObj);

if (errorHandler.hasErrors()) {
// not OK
// always under Linux
}
else {
// OK
// always under MS Windows
}

The schemata are loaded correctly (I have verified that by outputing the InputStream objects to a file). One of the things we do, however, is using <xsd:import> to import "message-header" schema into "mpd" schema:

<?xml version="1.0" encoding="UTF-8"?>
<xsd:schema
xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns:mh="http://www.emea.eu.int/EuroPharm/1.0/message-header"
xmlns:mpd="http://www.emea.eu.int/EuroPharm/1.0/mpd"
targetNamespace="http://www.emea.eu.int/EuroPharm/1.0/mpd"
elementFormDefault="qualified"
attributeFormDefault="unqualified">

<xsd:import schemaLocation="messageheader-eph-1.0.xsd" namespace="http://www.emea.eu.int/EuroPharm/1.0/message-header"/>

<xsd:element name="mpd">
  <xsd:annotation>
   <xsd:documentation>This is a Dictionary feed file format....</xsd:documentation>
  </xsd:annotation>
  <xsd:complexType>
   <xsd:sequence>
    <xsd:element name="messageheader" type="mh:MessageHeader"/>
    <xsd:group ref="mpd:DictionaryEntriesGroup"/>
   </xsd:sequence>
  </xsd:complexType>
</xsd:element>

The error I get is the following:

src-resolve: Cannot resolve the name 'mh:MessageHeader' to a(n) 'type definition' component.
schema_reference.4: Failed to read schema document 'file:///home/oracle/europharm/feed_ben/inbox/messageheader-eph-1.0.xsd', because 1) could not find the document; 2) the document could not be read; 3) the root element of the document is not <xsd:schema>.

I suspect the problem is with this import directive in the schema definition, and the error message certainly points to it. The directory, /home/oracle/europharm/feed_ben/inbox/, is the location of XML files, while schemata are located in the CLASSPATH (in a JAR file).

Does anyone know how could I resolve this?

Best regards,

--
Benjamin Kopić
European Medicines Agency (EMEA)
IT Development - Communications & Networking
7 Westferry Circus
Canary Wharf
London
E14 4HB
Tel. +44(0)20 7523 7417
Fax. +44(0)20 7418 8669
benjamin.kopic <at> emea.eu.int

________________________________________________________________________
This e-mail has been scanned for all known viruses by EMEA.
________________________________________________________________________

headers

Robert.A.Boesl | 8 May 2006 16:39

Robert A Boesl/MMBI/HSBCAMERICAS is out of the office.


I will be out of the office starting  05/08/2006 and will not return until
05/09/2006.

B2G concerns please contact Becky Archambault at ext. 2002. All other
assistance contact Terry O'Shei at ext. 1165

-----------------------------------------
*******************************************************************
****
 This E-mail is confidential. It may also be legally privileged. If
you
 are not the addressee you may not copy, forward, disclose or use
any
 part of it. If you have received this message in error, please
delete
 it and all copies from your system and notify the sender
immediately
 by return E-mail.

 Internet communications cannot be guaranteed to be timely, secure,
 error or virus-free. The sender does not accept liability for any
 errors or omissions.
*******************************************************************
****

4	May 2013
25	April 2013
5	March 2013
6	February 2013
11	January 2013
14	December 2012
11	November 2012
24	October 2012
10	September 2012
10	August 2012
3	July 2012
13	June 2012
32	May 2012
18	April 2012
52	March 2012
12	February 2012
11	January 2012
6	December 2011
2	November 2011
17	October 2011
2	September 2011
14	August 2011
33	July 2011
39	June 2011
11	May 2011
10	April 2011
20	March 2011
4	February 2011
19	January 2011
9	December 2010
18	November 2010
27	October 2010
16	September 2010
54	August 2010
21	July 2010
32	June 2010
23	May 2010
20	April 2010
11	March 2010
55	February 2010
40	January 2010
36	December 2009
69	November 2009
72	October 2009
45	September 2009
48	August 2009
33	July 2009
58	June 2009
16	May 2009
56	April 2009
21	March 2009
41	February 2009
32	January 2009
67	December 2008
88	November 2008
21	October 2008
30	September 2008
24	August 2008
31	July 2008
27	June 2008
53	May 2008
45	April 2008
70	March 2008
36	February 2008
65	January 2008
34	December 2007
66	November 2007
59	October 2007
15	September 2007
60	August 2007
50	July 2007
33	June 2007
53	May 2007
45	April 2007
43	March 2007
72	February 2007
119	January 2007
94	December 2006
68	November 2006
96	October 2006
166	September 2006
72	August 2006
43	July 2006
79	June 2006
47	May 2006
53	April 2006
75	March 2006
24	February 2006
26	January 2006
22	December 2005
61	November 2005
65	October 2005
34	September 2005
78	August 2005
68	July 2005
72	June 2005
26	May 2005
28	April 2005
112	March 2005
78	February 2005
103	January 2005
104	December 2004
97	November 2004
80	October 2004
94	September 2004
103	August 2004
91	July 2004
121	June 2004
80	May 2004
123	April 2004
126	March 2004
96	February 2004
158	January 2004
106	December 2003
132	November 2003
113	October 2003
146	September 2003
12	August 2003

Mon	Tue	Wed	Thu	Fri	Sat	Sun

1	2	3	4	5	6	7
8	9	10	11	12	13	14
15	16	17	18	19	20	21
22	23	24	25	26	27	28
29	30	31