j-users@xerces.apache.org Archives http://mail-archives.apache.org/mod_mbox/xerces-j-users/ 2009-12-07T14:31:48Z Re: Special characters problem while writing XML files using JAXP DOM Parser Benson Margulies <bimargulies@gmail.com> urn:uuid:%3c61b5d9410912040753m5f2431bbwad2d41ec32812183@mail-gmail-com%3e 2009-12-04T15:53:29Z 
I (mis?)understood the original poster to have a strong opinion on the
lexical surface form of the XML.

On Fri, Dec 4, 2009 at 8:23 AM, Michael Glavassevich
<mrglavas@ca.ibm.com> wrote:
> Sure, lexically but CDATA is just syntactic sugar. An entity reference
> (&lt;) or character reference (&#60; or &#x3C;) would also work fine.
>
> Michael Glavassevich
> XML Parser Development
> IBM Toronto Lab
> E-mail: mrglavas@ca.ibm.com
> E-mail: mrglavas@apache.org
>
> Benson Margulies <bimargulies@gmail.com> wrote on 12/04/2009 07:13:06 AM:
>
>> If you need a less than, you need to put it all in a CDATA.
>>
>>
>> On Fri, Dec 4, 2009 at 12:25 AM, nagineni <naganirangen_r@yahoo.com>
>> wrote:
>> >
>> > Hi,
>> >
>> > I'm creating xml file using JAXP DOM parser.While writing text data to a
>> > node parser is writing special characters.Below is the example.
>> >
>> > <?xml version="1.0" encoding="UTF-8" standalone="no"?>
>> > <template>
>> >          <name>naga</name>
>> >          <expr>for(int i=0;i&lt20;i++)</expr>
>> > </template>
>> >
>> > I want to my XML file output for(int i=0;i<20;i++) inside <expr>
>> > element.Is
>> > there any solution around it ?
>> > Can any one suggest me the solution for this problem ?Thanks in advance.
>> >
>> > Regards,
>> > Naga.
>> >
>> >
>> > -----
>> > Regards,
>> > Naga.
>> > --
>> > View this message in context: http://old.nabble.com/Special-
>> characters-problem-while-writing-XML-files-using-JAXP-DOM-Parser-
>> tp26635769p26635769.html
>> > Sent from the Xerces - J - Users mailing list archive at Nabble.com.
>> >
>> >
>> > ---------------------------------------------------------------------
>> > To unsubscribe, e-mail: j-users-unsubscribe@xerces.apache.org
>> > For additional commands, e-mail: j-users-help@xerces.apache.org
>> >
>> >
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: j-users-unsubscribe@xerces.apache.org
>> For additional commands, e-mail: j-users-help@xerces.apache.org
>

---------------------------------------------------------------------
To unsubscribe, e-mail: j-users-unsubscribe@xerces.apache.org
For additional commands, e-mail: j-users-help@xerces.apache.org
Re: Special characters problem while writing XML files using JAXP DOM Parser keshlam@us.ibm.com urn:uuid:%3cOFFA6B663F-0E36EDFC-ON85257682-004999CE-85257682-0049E5AE@lotus-com%3e 2009-12-04T13:29:53Z 
Or, better, escape the individual troublesome character by expressing it 
as  &lt;

XML also considers > and & to be reserved characters; they should be 
expressed as &gt; and &amp;.

<[[CDATA[]]> sections, which provide a block-escaping mechanism, are 
sometimes useful for hand-generated XML; less so for machine-generated. I 
generally discourage their use.

______________________________________
"... Three things see no end: A loop with exit code done wrong,
A semaphore untested, And the change that comes along. ..."
  -- "Threes" Rev 1.1 - Duane Elms / Leslie Fish (
http://www.ovff.org/pegasus/songs/threes-rev-11.html)



Benson Margulies <bimargulies@gmail.com> 
12/04/2009 07:13 AM
Please respond to
j-users@xerces.apache.org


To
j-users@xerces.apache.org
cc

Subject
Re: Special characters problem while writing XML files using JAXP DOM 
Parser






If you need a less than, you need to put it all in a CDATA.


On Fri, Dec 4, 2009 at 12:25 AM, nagineni <naganirangen_r@yahoo.com> 
wrote:
>
> Hi,
>
> I'm creating xml file using JAXP DOM parser.While writing text data to a
> node parser is writing special characters.Below is the example.
>
> <?xml version="1.0" encoding="UTF-8" standalone="no"?>
> <template>
>          <name>naga</name>
>          <expr>for(int i=0;i&lt20;i++)</expr>
> </template>
>
> I want to my XML file output for(int i=0;i<20;i++) inside <expr> 
element.Is
> there any solution around it ?
> Can any one suggest me the solution for this problem ?Thanks in advance.
>
> Regards,
> Naga.
>
>
> -----
> Regards,
> Naga.
> --
> View this message in context: 
http://old.nabble.com/Special-characters-problem-while-writing-XML-files-using-JAXP-DOM-Parser-tp26635769p26635769.html

> Sent from the Xerces - J - Users mailing list archive at Nabble.com.
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: j-users-unsubscribe@xerces.apache.org
> For additional commands, e-mail: j-users-help@xerces.apache.org
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: j-users-unsubscribe@xerces.apache.org
For additional commands, e-mail: j-users-help@xerces.apache.org
Re: Special characters problem while writing XML files using JAXP DOM Parser Michael Glavassevich <mrglavas@ca.ibm.com> urn:uuid:%3cOF39801EAC-5A39A289-ON85257682-0048F42A-85257682-00499B3C@ca-ibm-com%3e 2009-12-04T13:23:58Z 
Content-type: text/plain; charset=ISO-8859-1
Content-transfer-encoding: quoted-printable


Sure, lexically but CDATA is just syntactic sugar. An entity reference
(&lt;) or character reference (&#60; or &#x3C;) would also work fine.

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

Benson Margulies <bimargulies@gmail.com> wrote on 12/04/2009 07:13:06 A=
M:

> If you need a less than, you need to put it all in a CDATA.
>
>
> On Fri, Dec 4, 2009 at 12:25 AM, nagineni <naganirangen_r@yahoo.com>
wrote:
> >
> > Hi,
> >
> > I'm creating xml file using JAXP DOM parser.While writing text data=
 to
a
> > node parser is writing special characters.Below is the example.
> >
> > <?xml version=3D"1.0" encoding=3D"UTF-8" standalone=3D"no"?>
> > <template>
> > =A0 =A0 =A0 =A0 =A0<name>naga</name>
> > =A0 =A0 =A0 =A0 =A0<expr>for(int i=3D0;i&lt20;i++)</expr>
> > </template>
> >
> > I want to my XML file output for(int i=3D0;i<20;i++) inside <expr>
element.Is
> > there any solution around it ?
> > Can any one suggest me the solution for this problem ?Thanks in
advance.
> >
> > Regards,
> > Naga.
> >
> >
> > -----
> > Regards,
> > Naga.
> > --
> > View this message in context: http://old.nabble.com/Special-
> characters-problem-while-writing-XML-files-using-JAXP-DOM-Parser-
> tp26635769p26635769.html
> > Sent from the Xerces - J - Users mailing list archive at Nabble.com=
.
> >
> >
> > -------------------------------------------------------------------=
--
> > To unsubscribe, e-mail: j-users-unsubscribe@xerces.apache.org
> > For additional commands, e-mail: j-users-help@xerces.apache.org
> >
> >
>
> ---------------------------------------------------------------------=

> To unsubscribe, e-mail: j-users-unsubscribe@xerces.apache.org
> For additional commands, e-mail: j-users-help@xerces.apache.org=
Re: External entity in XML causing null pointer exception during DocumentBuilder.parse Michael Glavassevich <mrglavas@ca.ibm.com> urn:uuid:%3cOF83CEDAE7-10142D34-ON85257682-0045E4D3-85257682-004631B3@ca-ibm-com%3e 2009-12-04T12:46:41Z 
Content-type: text/plain; charset=US-ASCII

I already responded to you. See [1].

[1] http://markmail.org/message/2qzf4yeeg5iy5o7e.

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

sri kumar <sri_kumar_4u@yahoo.co.in> wrote on 12/04/2009 07:18:28 AM:

> I was trying to parse a XML Document using DOM Parser.
>
> I got null pointer exception while executing doc = builder.parse
> (xmlDataFile);
>
> There were few entities in the XML data file. On removing a
> particular entity, i was able to parse the file successfully
>
> The entity was some thing like this
>
> <!ENTITY SAMPLE.TIF SYSTEM "SAMPLE.TIF" NDATA TIF>
>
> What could be the reason?
>
> EDIT:
>
> Here is the code:
>
>         DocumentBuilderFactory aFactory =
> DocumentBuilderFactory.newInstance();
>         aFactory.setValidating(false);
>         aFactory.setFeature("http://xml.org/sax/features/namespaces",
false);
>         aFactory.setFeature
("http://apache.org/xml/features/validation/schema
> ", false);
>         aFactory.setIgnoringComments(true);
>         builder = aFactory.newDocumentBuilder();
>         doc = builder.parse(xmlDataFile);
> This is the trace:
>
>  at
> com.sun.org.apache.xerces.internal.dom.DeferredDocumentImpl.setChunkIndex
> (DeferredDocumentImpl.java:1944)
>     at
> com.sun.org.apache.xerces.internal.dom.DeferredDocumentImpl.appendChild
> (DeferredDocumentImpl.java:644)
>     at
> com.sun.org.apache.xerces.internal.parsers.AbstractDOMParser.characters
> (AbstractDOMParser.java:1191)
>     at
> com.sun.org.apache.xerces.internal.impl.dtd.XMLDTDValidator.characters
> (XMLDTDValidator.java:862)
>     at
>
com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl.scanDocument

> (XMLDocumentFragmentScannerImpl.java:463)
>     at
> com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse
> (XML11Configuration.java:807)
>     at
> com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse
> (XML11Configuration.java:737)
>     at com.sun.org.apache.xerces.internal.parsers.XMLParser.parse
> (XMLParser.java:107)
>     at com.sun.org.apache.xerces.internal.parsers.DOMParser.parse
> (DOMParser.java:225)
>     at
> com.sun.org.apache.xerces.internal.jaxp.DocumentBuilderImpl.parse
> (DocumentBuilderImpl.java:283)
>     at javax.xml.parsers.DocumentBuilder.parse(DocumentBuilder.java:180)
>     at XMLParser.Parse(XMLParser.java:89)
>     at Main.main(Main.java:116)
>
>
> 89 line number points to -> doc = builder.parse(xmlDataFile);
>
> i was able to find the workaround  if i add this code
>
>  aFactory.setFeature
("http://apache.org/xml/features/dom/defer-node-expansion
> ", false);
>
> the issue is resolved. But i need to know the cause of this problem.
> Was the entity the cause?
>
> Thanks
> Sri kumar
External entity in XML causing null pointer exception during DocumentBuilder.parse sri kumar <sri_kumar_4u@yahoo.co.in> urn:uuid:%3c622593-64873-qm@web8702-mail-in-yahoo-com%3e 2009-12-04T12:18:28Z 
I was trying to parse a XML Document using DOM Parser. 

I got null pointer exception while executing doc = builder.parse(xmlDataFile); 

There were few entities in the XML data file. On removing a particular entity, i was able
to parse the file successfully 

The entity was some thing like this 

<!ENTITY SAMPLE.TIF SYSTEM "SAMPLE.TIF" NDATA TIF> 

What could be the reason? 

EDIT: 

Here is the code: 

        DocumentBuilderFactory aFactory = DocumentBuilderFactory.newInstance(); 
        aFactory.setValidating(false); 
        aFactory.setFeature("http://xml.org/sax/features/namespaces", false); 
        aFactory.setFeature("http://apache.org/xml/features/validation/schema", false); 
        aFactory.setIgnoringComments(true); 
        builder = aFactory.newDocumentBuilder(); 
        doc = builder.parse(xmlDataFile); 
This is the trace: 

 at com.sun.org.apache.xerces.internal.dom.DeferredDocumentImpl.setChunkIndex(DeferredDocumentImpl.java:1944)

    at com.sun.org.apache.xerces.internal.dom.DeferredDocumentImpl.appendChild(DeferredDocumentImpl.java:644)

    at com.sun.org.apache.xerces.internal.parsers.AbstractDOMParser.characters(AbstractDOMParser.java:1191)

    at com.sun.org.apache.xerces.internal.impl.dtd.XMLDTDValidator.characters(XMLDTDValidator.java:862)

    at com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl.scanDocument(XMLDocumentFragmentScannerImpl.java:463)
    at com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Configuration.java:807)

    at com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Configuration.java:737)

    at com.sun.org.apache.xerces.internal.parsers.XMLParser.parse(XMLParser.java:107) 
    at com.sun.org.apache.xerces.internal.parsers.DOMParser.parse(DOMParser.java:225) 
    at com.sun.org.apache.xerces.internal.jaxp.DocumentBuilderImpl.parse(DocumentBuilderImpl.java:283)

    at javax.xml.parsers.DocumentBuilder.parse(DocumentBuilder.java:180) 
    at XMLParser.Parse(XMLParser.java:89) 
    at Main.main(Main.java:116) 


89 line number points to -> doc = builder.parse(xmlDataFile);


i was able to find the workaround  if i add this code

 aFactory.setFeature("http://apache.org/xml/features/dom/defer-node-expansion", false);

the issue is resolved. But i need to know the cause of this problem. Was the entity the cause?

Thanks
Sri kumar


      The INTERNET now has a personality. YOURS! See your Yahoo! Homepage. http://in.yahoo.com/
Re: Special characters problem while writing XML files using JAXP DOM Parser Benson Margulies <bimargulies@gmail.com> urn:uuid:%3c61b5d9410912040413l4216f97em59e69610cc1fed4d@mail-gmail-com%3e 2009-12-04T12:13:06Z 
If you need a less than, you need to put it all in a CDATA.


On Fri, Dec 4, 2009 at 12:25 AM, nagineni <naganirangen_r@yahoo.com> wrote:
>
> Hi,
>
> I'm creating xml file using JAXP DOM parser.While writing text data to a
> node parser is writing special characters.Below is the example.
>
> <?xml version="1.0" encoding="UTF-8" standalone="no"?>
> <template>
>          <name>naga</name>
>          <expr>for(int i=0;i&lt20;i++)</expr>
> </template>
>
> I want to my XML file output for(int i=0;i<20;i++) inside <expr> element.Is
> there any solution around it ?
> Can any one suggest me the solution for this problem ?Thanks in advance.
>
> Regards,
> Naga.
>
>
> -----
> Regards,
> Naga.
> --
> View this message in context: http://old.nabble.com/Special-characters-problem-while-writing-XML-files-using-JAXP-DOM-Parser-tp26635769p26635769.html
> Sent from the Xerces - J - Users mailing list archive at Nabble.com.
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: j-users-unsubscribe@xerces.apache.org
> For additional commands, e-mail: j-users-help@xerces.apache.org
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: j-users-unsubscribe@xerces.apache.org
For additional commands, e-mail: j-users-help@xerces.apache.org
Re: Special characters problem while writing XML files using JAXP DOM Parser Mukul Gandhi <mukulg@apache.org> urn:uuid:%3c7870f82e0912032140q570e1480sbb826a8010c94364@mail-gmail-com%3e 2009-12-04T05:40:21Z 
it seems, you are not writing the built in entity reference for
character, "<" appropriately.
you are not writing a semicolon, after &lt.

The parsing of the document you have posted, would likely fail with
this particular error.

The Xerces-J sax.Counter sample gives following error, while parsing
the XML document you have posted:

[Fatal Error] test.xml:4:35: The entity "lt20" was referenced, but not declared.

On Fri, Dec 4, 2009 at 10:55 AM, nagineni <naganirangen_r@yahoo.com> wrote:
>
> Hi,
>
> I'm creating xml file using JAXP DOM parser.While writing text data to a
> node parser is writing special characters.Below is the example.
>
> <?xml version="1.0" encoding="UTF-8" standalone="no"?>
> <template>
>          <name>naga</name>
>          <expr>for(int i=0;i&lt20;i++)</expr>
> </template>
>
> I want to my XML file output for(int i=0;i<20;i++) inside <expr> element.Is
> there any solution around it ?
> Can any one suggest me the solution for this problem ?Thanks in advance.
>
> Regards,
> Naga.


-- 
Regards,
Mukul Gandhi

---------------------------------------------------------------------
To unsubscribe, e-mail: j-users-unsubscribe@xerces.apache.org
For additional commands, e-mail: j-users-help@xerces.apache.org
Special characters problem while writing XML files using JAXP DOM Parser nagineni <naganirangen_r@yahoo.com> urn:uuid:%3c26635769-post@talk-nabble-com%3e 2009-12-04T05:25:08Z 

Hi,

I'm creating xml file using JAXP DOM parser.While writing text data to a
node parser is writing special characters.Below is the example.

<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<template>
          <name>naga</name>
          <expr>for(int i=0;i&lt20;i++)</expr>
</template>

I want to my XML file output for(int i=0;i<20;i++) inside <expr> element.Is
there any solution around it ?
Can any one suggest me the solution for this problem ?Thanks in advance.

Regards,
Naga.


-----
Regards,
Naga.
-- 
View this message in context: http://old.nabble.com/Special-characters-problem-while-writing-XML-files-using-JAXP-DOM-Parser-tp26635769p26635769.html
Sent from the Xerces - J - Users mailing list archive at Nabble.com.


---------------------------------------------------------------------
To unsubscribe, e-mail: j-users-unsubscribe@xerces.apache.org
For additional commands, e-mail: j-users-help@xerces.apache.org
=?UTF-8?B?UmU6IE51bGwgcG9pbnRlciBleGNlcHRpb24gZHVyaW5n?= =?UTF-8?B?IERvY3VtZW50QnVpbGRlci5wYXJzZSg=?= =?ISO-8859-1?Q?=3F?= =?UTF-8?B?ZmlsZQ==?= =?ISO-8859-1?Q?=3F?= =?UTF-8?B?KTs=?= Michael Glavassevich <mrglavas@ca.ibm.com> urn:uuid:%3cOFE14853F9-A9D91059-ON85257681-003B1EA4-85257681-003BB6F1@ca-ibm-com%3e 2009-12-03T10:52:14Z 
Content-type: text/plain; charset=US-ASCII
Content-transfer-encoding: quoted-printable


This is a bug [1] that was fixed in Xerces-J back in 2007.

However, you are using Sun's implementation, not Apache Xerces-J. We ca=
nnot
do anything about the problem you're having with this implementation as=
 we
have no influence over its codebase. You need to pursue this with the J=
DK
vendor if you want a fix there.

Thanks.,

[1] https://issues.apache.org/jira/browse/XERCESJ-977

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

sri kumar <sri_kumar_4u@yahoo.co.in> wrote on 12/03/2009 04:50:50 AM:

> Hello All,
>
> I got null pointer exception while executing doc =3D builder.parse
(xmlDataFile);
>
> There were few entities in the XML data file. On removing a
> particular entity, i was able to parse the file successfully
>
> The entity was some thing like this
>
> <!ENTITY SAMPLE.TIF SYSTEM "SAMPLE.TIF" NDATA TIF>
>
> What could be the reason?
>
> Here is the code:
>
> DocumentBuilderFactory aFactory =3D DocumentBuilderFactory.newInstanc=
e();
> aFactory.setValidating(false);
> aFactory.setFeature("http://xml.org/sax/features/namespaces", false);=

> aFactory.setFeature("http://apache.org/xml/features/validation/schema=

> ", false);
> aFactory.setIgnoringComments(true);
> builder =3D aFactory.newDocumentBuilder();
> doc =3D builder.parse(xmlDataFile);
>
>
>
> This is the trace:
>
> at
> com.sun.org.apache.xerces.internal.dom.DeferredDocumentImpl.setChunkI=
ndex
> (DeferredDocumentImpl.java:1944)
> at
> com.sun.org.apache.xerces.internal.dom.DeferredDocumentImpl.appendChi=
ld
> (DeferredDocumentImpl.java:644)
> at
> com.sun.org.apache.xerces.internal.parsers.AbstractDOMParser.characte=
rs
> (AbstractDOMParser.java:1191)
> at
> com.sun.org.apache.xerces.internal.impl.dtd.XMLDTDValidator.character=
s
> (XMLDTDValidator.java:862)
> at
>
com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl.=
scanDocument

> (XMLDocumentFragmentScannerImpl.java:463)
> at
> com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse
> (XML11Configuration.java:807)
> at
> com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse
> (XML11Configuration.java:737)
> at com.sun.org.apache.xerces.internal.parsers.XMLParser.parse
> (XMLParser.java:107)
> at com.sun.org.apache.xerces.internal.parsers.DOMParser.parse
> (DOMParser.java:225)
> at com.sun.org.apache.xerces.internal.jaxp.DocumentBuilderImpl.parse
> (DocumentBuilderImpl.java:283)
> at javax.xml.parsers.DocumentBuilder.parse(DocumentBuilder.java:180)
> at XMLParser.Parse(XMLParser.java:89)
> at Main.main(Main.java:116)
>
>
>
> 89 line number points to -> doc =3D builder.parse(xmlDataFile);=
Re: Loosing significant space in LSSerializer Chris Simmons <cps@corefiling.com> urn:uuid:%3c4B0E4FCC-3040702@corefiling-com%3e 2009-11-26T09:52:12Z 
Stanimir Stamenkov wrote:
> Mon, 23 Nov 2009 11:20:23 +0000, /Chris Simmons/:
>
>> I raised a bug (which included a patch) over two
>> years ago due to different behaviour between the Xerces/Xalan
>> LSSerializer but it has seemingly been ignored.
>>
>> https://issues.apache.org/jira/browse/XALANJ-2409
>>
>> I wonder if LSSerializer bugs are falling between the cracks?
>
> Have you tried whether registering an LSSerializerFilter and filtering 
> out xmlns:xml attributes works around the problem?
>
We just built a patched version of the serializer jar as it seemed the 
most robust fix.  I can't recall whether we tried a filter.  I suppose 
it should work as long as the filter is after the namespace fix-up in 
the serializer's pipeline.

Chris.

---------------------------------------------------------------------
To unsubscribe, e-mail: j-users-unsubscribe@xerces.apache.org
For additional commands, e-mail: j-users-help@xerces.apache.org
Re: Loosing significant space in LSSerializer Stanimir Stamenkov <s7an10@netscape.net> urn:uuid:%3c4B0DA1C6-9070608@netscape-net%3e 2009-11-25T21:29:42Z 
Mon, 23 Nov 2009 11:20:23 +0000, /Chris Simmons/:

> I raised a bug (which included a patch) over two
> years ago due to different behaviour between the Xerces/Xalan
> LSSerializer but it has seemingly been ignored.
>
> https://issues.apache.org/jira/browse/XALANJ-2409
>
> I wonder if LSSerializer bugs are falling between the cracks?

Have you tried whether registering an LSSerializerFilter and 
filtering out xmlns:xml attributes works around the problem?

-- 
Stanimir

---------------------------------------------------------------------
To unsubscribe, e-mail: j-users-unsubscribe@xerces.apache.org
For additional commands, e-mail: j-users-help@xerces.apache.org
Re: xs:any namespace resolution Michael Glavassevich <mrglavas@ca.ibm.com> urn:uuid:%3cOF456BA30A-405504DE-ON85257679-002132CE-85257679-00227B40@ca-ibm-com%3e 2009-11-25T06:16:37Z 
Content-type: text/plain; charset=US-ASCII
Content-transfer-encoding: quoted-printable


Hi Ajay,

The Validator knows what kind of Schema it was created with. It will on=
ly
call the LSResourceResolver if the Schema was created with
SchemaFactory.newSchema() (the one with no parameters). Whatever it loa=
ds
dynamically does get cached [1] (though might get flushed out at some p=
oint
in the future due to demand for memory).

Thanks.

[1]
http://svn.apache.org/viewvc/xerces/java/trunk/src/org/apache/xerces/ja=
xp/validation/SoftReferenceGrammarPool.java?revision=3D699892&view=3Dma=
rkup.

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

ajay bhadauria <abhadauria@yahoo.com> wrote on 11/24/2009 05:30:58 PM:

> Michael,
>
> Thanks a lot, it works. I have a question for you.
>
> Is Validator smart enough to figure out when LSResourceResolver is
> giving compiled schema or uncompiled schema just to avoid compiling
> of schema at runtime ?
>
> Thanks
> Ajay=
Re: xs:any namespace resolution ajay bhadauria <abhadauria@yahoo.com> urn:uuid:%3c871272-55674-qm@web111510-mail-gq1-yahoo-com%3e 2009-11-24T22:30:58Z 
Michael,

Thanks a lot, it works. I have a question for you.

Is Validator smart enough to figure out when LSResourceResolver is giving compiled schema
or uncompiled schema just to avoid compiling of schema at runtime ?

Thanks
Ajay   

--- On Fri, 11/20/09, Michael Glavassevich <mrglavas@ca.ibm.com> wrote:

> From: Michael Glavassevich <mrglavas@ca.ibm.com>
> Subject: Re: xs:any namespace resolution
> To: j-users@xerces.apache.org
> Date: Friday, November 20, 2009, 3:14 AM
> 
> Ajay,
> 
> 
> 
> If you want schemas to be dynamically loaded by the
> validator you need to use the SchemaFactory.newSchema()
> method [1] (the one with no parameters). JAXP doesn't
> let you mix that with pre-loading of schemas. See [2][3] in
> the mailing list archives for more details.
> 
> 
> 
> Thanks.
> 
> 
> 
> [1] http://xerces.apache.org/xerces2-j/javadocs/api/javax/xml/validation/SchemaFactory.html#newSchema()
> 
> [2] http://markmail.org/message/5xe4u5njgxkiosk7
> 
> [3] http://markmail.org/message/4nhwp7ggi6fytqfg
> 
> 
> 
> Michael Glavassevich
> 
> XML Parser Development
> 
> IBM Toronto Lab
> 
> E-mail: mrglavas@ca.ibm.com
> 
> E-mail: mrglavas@apache.org
> 
> 
> 
> ajay bhadauria <abhadauria@yahoo.com> wrote on
> 11/19/2009 12:25:17 PM:
> 
> 
> 
> > Michael,
> 
> > 
> 
> > Sorry. I was over excited. I was doing the same way as
> you suggested
> 
> > but my LSResourceResolver is not getting called which
> means that I 
> 
> > am missing something which I am not aware of it. 
> 
> > 
> 
> > The Test2.xml which I attached in the previous mail,
> the tag 
> 
> > "ns1:Document" contains namespace
> xmlns:ns1="urn:swift:xsd:$xtsn.
> 
> > 998.001.01" which is on the 2.xsd.
> 
> > 
> 
> > Please find the attached Code where I set
> LSresourceResolver to Validator.
> 
> > 
> 
> > Thanks
> 
> > Ajay 
> 
> > --- On Thu, 11/19/09, Michael Glavassevich
> <mrglavas@ca.ibm.com> wrote:
> 
> > 
> 
> > > From: Michael Glavassevich
> <mrglavas@ca.ibm.com>
> 
> > > Subject: Re: xs:any namespace resolution
> 
> > > To: j-users@xerces.apache.org
> 
> > > Date: Thursday, November 19, 2009, 8:32 PM
> 
> > > 
> 
> > > (Ajay, patience. In the future, please don't
> 
> > > post the same message over and over again to the
> list. We
> 
> > > heard you the first time.)
> 
> > > 
> 
> > > 
> 
> > > 
> 
> > > Try writing an LSResourceResolver (which you
> would
> 
> > > register with the validator) and have that return
> the 2nd
> 
> > > schema document on the request with its target
> 
> > > namespace.
> 
> > > 
> 
> > > 
> 
> > > 
> 
> > > Thanks.
> 
> > > 
> 
> > > 
> 
> > > 
> 
> > > Michael Glavassevich
> 
> > > 
> 
> > > XML Parser Development
> 
> > > 
> 
> > > IBM Toronto Lab
> 
> > > 
> 
> > > E-mail: mrglavas@ca.ibm.com
> 
> > > 
> 
> > > E-mail: mrglavas@apache.org
> 
> > > 
> 
> > > 
> 
> > > 
> 
> > > ajay bhadauria <abhadauria@yahoo.com> wrote
> on
> 
> > > 11/19/2009 09:15:03 AM:
> 
> > > 
> 
> > > 
> 
> > > 
> 
> > > > Hi,
> 
> > > 
> 
> > > > 
> 
> > > 
> 
> > > > I do knot know much about xs:any construct
> and I
> 
> > >  am new to this and
> 
> > > 
> 
> > > > I read it but I do not know how I can tell
> the
> 
> > > validator to use 
> 
> > > 
> 
> > > > namespace (only runtime) which is defined in
> the
> 
> > > different schema.
> 
> > > 
> 
> > > >  
> 
> > > 
> 
> > > > Using  
> 
> > > 
> 
> > > > <xs:any
> 
> > > 
> 
> > > > >  namespace="##any"
> 
> > > processContents="strict"/>
> construct, 
> 
> > > 
> 
> > > > 
> 
> > > 
> 
> > > > I am vlidating xml instance with Validator
> which has a
> 
> > > main schema 
> 
> > > 
> 
> > > > but validator does not know second schema.
>  
> 
> > > 
> 
> > > > 
> 
> > > 
> 
> > > > Now,  how I can tell the validator during
> 
> > > validation time about the 
> 
> > > 
> 
> > > > second schema to which some elements belong
> to the
> 
> > > namespace which 
> 
> > > 
> 
> > > > is defined in the second schema.   
> 
> > > 
> 
> > > > 
> 
> > > 
> 
> > > > Thanks
> 
> > > 
> 
> > > > ajay
> 
> > > 
> 
> > > > 
> 
> > > 
> 
> > > > --- On Thu, 11/19/09, ajay bhadauria
> 
> > > <abhadauria@yahoo.com> wrote:
> 
> > > 
> 
> > > > 
> 
> > > 
> 
> > > > > From: ajay bhadauria
> 
> > > <abhadauria@yahoo.com>
> 
> > > 
> 
> > > > > Subject: Re: xs:any namespace
> resolution
> 
> > > 
> 
> > > > > To: j-users@xerces.apache.org
> 
> > > 
> 
> > > > > Date: Thursday, November 19, 2009, 6:38
> AM
> 
> > > 
> 
> > > > > Hi,
> 
> > > 
> 
> > > > > 
> 
> > > 
> 
> > > > > I am using <xs:any
> 
> > > 
> 
> > > > > > namespace="##any"
> 
> > > processContents="strict"/> and I
> 
> > > 
> 
> > > > > am validating xml instance which is
> having
> 
> > > elements which
> 
> > > 
> 
> > > > > belong to the different namespace and
> 
> > > corresponding to this
> 
> > > 
> 
> > > > > namespace, schema is not pre-loaded. I
> mean yhat
> 
> > > external
> 
> > > 
> 
> > > > > schema is not pre-loaded.
> 
> > > 
> 
> > > > > 
> 
> > > 
> 
> > > > > How do I tell Java Validator about this
> external
> 
> > > schema so
> 
> > > 
> 
> > > > > that xml instance is validated
> successfully ?
> 
> > > 
> 
> > > > > 
> 
> > > 
> 
> > > > > 
> 
> > > 
> 
> > > > > Is there any way I can tell the
> validator at the
> 
> > > time of
> 
> > > 
> 
> > > > > validation only about external schema
> which is
> 
> > > not
> 
> > > 
> 
> > > > > pre-loaded with main schema?
> 
> > > 
> 
> > > > > 
> 
> > > 
> 
> > > > > Help me in understanding whether it can
> be done
> 
> > > ???
> 
> > > 
> 
> > > > > Thanks
> 
> > > 
> 
> > > > > Ajay 
> 
> > > 
> 
> > > > > 
> 
> > > 
> 
> > > > > --- On Thu, 11/19/09, ajay bhadauria
> 
> > > <abhadauria@yahoo.com>
> 
> > > 
> 
> > > > > wrote:
> 
> > > 
> 
> > > > > 
> 
> > > 
> 
> > > > > > From: ajay bhadauria
> 
> > > <abhadauria@yahoo.com>
> 
> > > 
> 
> > > > > > Subject: xs:any namespace
> resolution
> 
> > > 
> 
> > > > > > To: j-users@xerces.apache.org
> 
> > > 
> 
> > > > > > Date: Thursday, November 19, 2009,
> 12:48 AM
> 
> > > 
> 
> > > > > > Hi,
> 
> > > 
> 
> > > > > > 
> 
> > > 
> 
> > > > > > I have schema file 1.xsd which has
> xs:any
> 
> > > schema
> 
> > > 
> 
> > > > > construct
> 
> > > 
> 
> > > > > >  
> 
> > > 
> 
> > > > > > <xs:complexType
> 
> > > name="ExtensionEnvelope">
> 
> > > 
> 
> > > > > >     
> 
> > > 
> 
> > > > >    <xs:sequence>
> 
> > > 
> 
> > > > > >         
> 
> > > 
> 
> > > > >    <xs:any
> 
> > > 
> 
> > > > > > namespace="##any"
> 
> > > processContents="strict"/>
> 
> > > 
> 
> > > > > >     
> 
> > > 
> 
> > > > >    </xs:sequence>
> 
> > > 
> 
> > > > > >     </xs:complexType>
> 
> > > 
> 
> > > > > > 
> 
> > > 
> 
> > > > > > And I try to validate xml instance
> (
> 
> > > test2.xml )
> 
> > > 
> 
> > > > > against
> 
> > > 
> 
> > > > > > this schema, it gave the following
> error
> 
> > > 
> 
> > > > > >      cvc-complex-type.2.4.c:
> The
> 
> > > 
> 
> > > > > > matching wildcard is strict, but
> no
> 
> > > declaration can be
> 
> > > 
> 
> > > > > found
> 
> > > 
> 
> > > > > > for element
> 'ns1:Document'.
> 
> > > 
> 
> > > > > > 
> 
> > > 
> 
> > > > > > However, the namespace which the
> Validator
> 
> > > is looking
> 
> > > 
> 
> > > > > for
> 
> > > 
> 
> > > > > > is in other xsd file (2.xsd). 
> 
> > > 
> 
> > > > > > 
> 
> > > 
> 
> > > > > > How do I tell Validator the
> location of
> 
> > > 2.xsd file
> 
> > > 
> 
> > > > > during
> 
> > > 
> 
> > > > > > validation ? 
> 
> > > 
> 
> > > > > > 
> 
> > > 
> 
> > > > > > The test.xml has some elements
> which belong
> 
> > > to the
> 
> > > 
> 
> > > > > > namespace
> urn:swift:xsd:$xtsn.998.001.01
> 
> > > which is
> 
> > > 
> 
> > > > > defined in
> 
> > > 
> 
> > > > > > the 2.xsd file.
> 
> > > 
> 
> > > > > > 
> 
> > > 
> 
> > > > > > 
> 
> > > 
> 
> > > > > >       
> 
> > > 
> 
> > > > > >
> 
> > > 
> 
> > > > >
> 
> > >
> ---------------------------------------------------------------------
> 
> > > 
> 
> > > > > > To unsubscribe, e-mail:
> 
> > > j-users-unsubscribe@xerces.apache.org
> 
> > > 
> 
> > > > > > For additional commands, e-mail:
> 
> > > j-users-help@xerces.apache.org
> 
> > > 
> 
> > > > > 
> 
> > > 
> 
> > > > > 
> 
> > > 
> 
> > > > >       
> 
> > > 
> 
> > > > > 
> 
> > > 
> 
> > > > >
> 
> > >
> ---------------------------------------------------------------------
> 
> > > 
> 
> > > > > To unsubscribe, e-mail:
> 
> > > j-users-unsubscribe@xerces.apache.org
> 
> > > 
> 
> > > > > For additional commands, e-mail:
> 
> > > j-users-help@xerces.apache.org
> 
> > > 
> 
> > > >       
> 
> > > 
> 
> > > > 
> 
> > > 
> 
> > > >
> 
> > >
> ---------------------------------------------------------------------
> 
> > > 
> 
> > > > To unsubscribe, e-mail:
> 
> > > j-users-unsubscribe@xerces.apache.org
> 
> > > 
> 
> > > > For additional commands, e-mail:
> 
> > > j-users-help@xerces.apache.org
> 
> > > 
> 
> > >
> 
> > 
> 
> > 
> 
> >       [attachment
> "SchemaReader.java" deleted by Michael 
> 
> > Glavassevich/Toronto/IBM] 
> 
> >
> ---------------------------------------------------------------------
> 
> > To unsubscribe, e-mail:
> j-users-unsubscribe@xerces.apache.org
> 
> > For additional commands, e-mail:
> j-users-help@xerces.apache.org


      

---------------------------------------------------------------------
To unsubscribe, e-mail: j-users-unsubscribe@xerces.apache.org
For additional commands, e-mail: j-users-help@xerces.apache.org
Re: doctype? Michael Glavassevich <mrglavas@ca.ibm.com> urn:uuid:%3cOF6B846778-1BCFFD3E-ON85257678-00640090-85257678-0064AB53@ca-ibm-com%3e 2009-11-24T18:19:34Z 
Content-type: text/plain; charset=US-ASCII
Content-transfer-encoding: quoted-printable


Michael Ludwig <milu71@gmx.de> wrote on 11/24/2009 12:20:15 PM:

> Michael Glavassevich schrieb am 24.11.2009 um 12:02:29 (-0500):
> >
> > A DOCTYPE can be specified programmatically [1][2][3], so you don't=

> > need to write a stylesheet.
>
> True, thanks. But I assumed the OP had already written one, as he wro=
te:
>
> > > > > I use the usual TraX call. No doctype lands in the output. I'=
m
> > > > > very carefully using Xerces for the DOM and Xalan for TraX.
>
> I might be wrong, but the first of the three references you gave is
> probably not related to specifying the DOCTYPE.

Good catch. I meant to post a link to setOutputProperty():

http://xerces.apache.org/xerces2-j/javadocs/api/javax/xml/transform/Tra=
nsformer.html#setOutputProperty
(java.lang.String,%20java.lang.String)

> > [1] http://xerces.apache.org/xerces2-j/javadocs/api/javax/xml/
> transform/Transformer.html#setParameter
(java.lang.String,%20java.lang.Object)
>
> Best,
>
> --
> Michael Ludwig
>
> ---------------------------------------------------------------------=

> To unsubscribe, e-mail: j-users-unsubscribe@xerces.apache.org
> For additional commands, e-mail: j-users-help@xerces.apache.org

Michael Glavassevich
XML Parser Development
IBM Toronto Lab
E-mail: mrglavas@ca.ibm.com
E-mail: mrglavas@apache.org=
Re: doctype? Michael Ludwig <milu71@gmx.de> urn:uuid:%3c20091124172015-GB2912@wladimir%3e 2009-11-24T17:20:15Z 
Michael Glavassevich schrieb am 24.11.2009 um 12:02:29 (-0500):
> 
> A DOCTYPE can be specified programmatically [1][2][3], so you don't
> need to write a stylesheet.

True, thanks. But I assumed the OP had already written one, as he wrote:

> > > > I use the usual TraX call. No doctype lands in the output. I'm
> > > > very carefully using Xerces for the DOM and Xalan for TraX.

I might be wrong, but the first of the three references you gave is
probably not related to specifying the DOCTYPE.

> [1] http://xerces.apache.org/xerces2-j/javadocs/api/javax/xml/transform/Transformer.html#setParameter(java.lang.String,%20java.lang.Object)

Best,

-- 
Michael Ludwig

---------------------------------------------------------------------
To unsubscribe, e-mail: j-users-unsubscribe@xerces.apache.org
For additional commands, e-mail: j-users-help@xerces.apache.org
Re: doctype? Michael Glavassevich <mrglavas@ca.ibm.com> urn:uuid:%3cOF62A4CFFE-B96B95ED-ON85257678-005D1628-85257678-005D9CD0@ca-ibm-com%3e 2009-11-24T17:02:29Z 
Content-type: text/plain; charset=US-ASCII
Content-transfer-encoding: quoted-printable


A DOCTYPE can be specified programmatically [1][2][3], so you don't nee=
d to
write a stylesheet. Note that either approach only works if the
DocumentType node has no internal subset. If it has one it will still b=
e
lost if you do this.

Thanks.

[1]
http://xerces.apache.org/xerces2-j/javadocs/api/javax/xml/transform/Tra=
nsformer.html#setParameter
(java.lang.String,%20java.lang.Object)
[2]
http://xerces.apache.org/xerces2-j/javadocs/api/javax/xml/transform/Out=
putKeys.html#DOCTYPE_PUBLIC
[3]
http://xerces.apache.org/xerces2-j/javadocs/api/javax/xml/transform/Out=
putKeys.html#DOCTYPE_SYSTEM

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

Michael Ludwig <milu71@gmx.de> wrote on 11/24/2009 08:22:31 AM:

> Michael Glavassevich schrieb am 30.10.2009 um 12:45:44 (-0400):
>
> > Benson Margulies <bimargulies@gmail.com> wrote on 10/30/2009 10:59:=
27
> > AM:
> >
> > > I'm not sure if I should be consulting Xerces, Xalan, or a beer.
> > >
> > > I've got a DOM tree with a doctype on it.
> > >
> > > I want to serialize it.
> > >
> > > I use the usual TraX call. No doctype lands in the output. I'm ve=
ry
> > > carefully using Xerces for the DOM and Xalan for TraX.
>
> You can set a DOCTYPE from XSLT using xsl:output/@doctype-system and
> xsl:output/@doctype-public:
>
> <xsl:stylesheet version=3D"1.0"
>   xmlns:xsl=3D"http://www.w3.org/1999/XSL/Transform">
>
>   <xsl:output doctype-public=3D"eins zwei drei"
>     doctype-system=3D"http://eins.de/zwei/drei"/>
>
>   <xsl:template match=3D"@*|node()">
>     <xsl:copy>
>       <xsl:apply-templates select=3D"@*|node()"/>
>     </xsl:copy>
>   </xsl:template>
> </xsl:stylesheet>
>
> --
> Michael Ludwig
>
> ---------------------------------------------------------------------=

> To unsubscribe, e-mail: j-users-unsubscribe@xerces.apache.org
> For additional commands, e-mail: j-users-help@xerces.apache.org=
Re: doctype? Michael Ludwig <milu71@gmx.de> urn:uuid:%3c20091124132231-GA2912@wladimir%3e 2009-11-24T13:22:31Z 
Michael Glavassevich schrieb am 30.10.2009 um 12:45:44 (-0400):

> Benson Margulies <bimargulies@gmail.com> wrote on 10/30/2009 10:59:27
> AM:
> 
> > I'm not sure if I should be consulting Xerces, Xalan, or a beer.
> >
> > I've got a DOM tree with a doctype on it.
> >
> > I want to serialize it.
> >
> > I use the usual TraX call. No doctype lands in the output. I'm very
> > carefully using Xerces for the DOM and Xalan for TraX.

You can set a DOCTYPE from XSLT using xsl:output/@doctype-system and
xsl:output/@doctype-public:

<xsl:stylesheet version="1.0"
  xmlns:xsl="http://www.w3.org/1999/XSL/Transform">

  <xsl:output doctype-public="eins zwei drei"
    doctype-system="http://eins.de/zwei/drei"/>

  <xsl:template match="@*|node()">
    <xsl:copy>
      <xsl:apply-templates select="@*|node()"/>
    </xsl:copy>
  </xsl:template>
</xsl:stylesheet>

-- 
Michael Ludwig

---------------------------------------------------------------------
To unsubscribe, e-mail: j-users-unsubscribe@xerces.apache.org
For additional commands, e-mail: j-users-help@xerces.apache.org
Re: Loosing significant space in LSSerializer Michael Glavassevich <mrglavas@ca.ibm.com> urn:uuid:%3cOF4009AE26-AE5407F0-ON85257677-004F7E8A-85257677-0054676A@ca-ibm-com%3e 2009-11-23T15:21:54Z 
Content-type: text/plain; charset=US-ASCII
Content-transfer-encoding: quoted-printable


Chris Simmons <cps@corefiling.com> wrote on 11/23/2009 06:20:23 AM:

> > It is in Xalan. Their serializer started as a copy of the Xerces on=
e
> > (even has similar package names: org.apache.xml.serialize vs.
> > org.apache.xml.serializer). We didn't want to duplicate the effort
> > anymore and decided to combine forces and the Xalan one was chosen =
as
> > the common codebase because it was better maintained and was making=

> > significant improvements to performance. Its LSSerializer
> > implementation was written by a Xerces committer and I have made
> > improvements and fixes to it too where I've found issues, so it's
> > being jointly maintained, though in a different project. This is th=
e
> > alternative. It *is* an LSSerializer and there is no reason that it=

> > can't be updated / fixed to have similar behaviour, but that's only=

> > likely to happen if users report the problems they're having (patch=
es
> > are welcome), preferably in JIRA.
> >
> If only that were true.  I raised a bug (which included a patch) over=

> two years ago due to different behaviour between the Xerces/Xalan
> LSSerializer but it has seemingly been ignored.
>
> https://issues.apache.org/jira/browse/XALANJ-2409
>
> I wonder if LSSerializer bugs are falling between the cracks?

Xalan has been relatively dormant the last couple years (developers bus=
y at
their day jobs and elsewhere), so yes it's been awhile since things hav=
e
moved but there's recently been interest in revitalizing the project an=
d
potentially two new committers who seem eager to get things rolling aga=
in.
b
> Chris Simmons.
>
> ---------------------------------------------------------------------=

> To unsubscribe, e-mail: j-users-unsubscribe@xerces.apache.org
> For additional commands, e-mail: j-users-help@xerces.apache.org

Thanks.

Michael Glavassevich
XML Parser Development
IBM Toronto Lab
E-mail: mrglavas@ca.ibm.com
E-mail: mrglavas@apache.org=
Re: Loosing significant space in LSSerializer Chris Simmons <cps@corefiling.com> urn:uuid:%3c4B0A6FF7-2060202@corefiling-com%3e 2009-11-23T11:20:23Z 

> It is in Xalan. Their serializer started as a copy of the Xerces one 
> (even has similar package names: org.apache.xml.serialize vs. 
> org.apache.xml.serializer). We didn't want to duplicate the effort 
> anymore and decided to combine forces and the Xalan one was chosen as 
> the common codebase because it was better maintained and was making 
> significant improvements to performance. Its LSSerializer 
> implementation was written by a Xerces committer and I have made 
> improvements and fixes to it too where I've found issues, so it's 
> being jointly maintained, though in a different project. This is the 
> alternative. It *is* an LSSerializer and there is no reason that it 
> can't be updated / fixed to have similar behaviour, but that's only 
> likely to happen if users report the problems they're having (patches 
> are welcome), preferably in JIRA.
>
If only that were true.  I raised a bug (which included a patch) over 
two years ago due to different behaviour between the Xerces/Xalan 
LSSerializer but it has seemingly been ignored.

https://issues.apache.org/jira/browse/XALANJ-2409

I wonder if LSSerializer bugs are falling between the cracks?

Chris Simmons.

---------------------------------------------------------------------
To unsubscribe, e-mail: j-users-unsubscribe@xerces.apache.org
For additional commands, e-mail: j-users-help@xerces.apache.org
Re: Loosing significant space in LSSerializer Michael Glavassevich <mrglavas@ca.ibm.com> urn:uuid:%3cOFF462A0C4-0B9E2D72-ON85257676-007A4B44-85257676-007BD264@ca-ibm-com%3e 2009-11-22T22:32:27Z 
Content-type: text/plain; charset=US-ASCII

Right, that's exactly how it works:

    public LSSerializer createLSSerializer() {
        try {
            Class serializerClass = ObjectFactory.findProviderClass(
                "org.apache.xml.serializer.dom3.LSSerializerImpl",
                ObjectFactory.findClassLoader(), true);
            return (LSSerializer) serializerClass.newInstance();
        }
        catch (Exception e) {}
        // Fall back to Xerces' deprecated serializer if
        // the Xalan based serializer is unavailable.
        return new DOMSerializerImpl();
    }

Was hoping to put a warning in there if it takes the fallback path but
there's no DOMErrorHandler to report it to at this point.

FYI: If you don't have Xerces on the classpath but instead try to access
the JDK version [1] you may not get very far.

Thanks.

[1] http://markmail.org/message/e6rlhwymr43p4u4v

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

Dick Deneer <dick.deneer@donkeydevelopment.com> wrote on 11/22/2009
04:06:06 PM:

> Hi Benson,
>
> As Michael notes, Xerces is now shipped with the serializer.jar
> (which contains the xalan serializer). If you have this on your
> classpath it will be used.
> If you leave it out, then xerces will fall back to it's own (deprecated)
one.
>
> regards
> Dick Deneer
> Op 22-nov-2009, om 21:54 heeft Benson Margulies het volgende geschreven:
>
> Hi Michael,
>
> So, if I put Xerces and not Xalan into classpath, and ask a document
> for it's implementation, and ask that for the DOMImplementationLS,
> what do I get? Whatever Sun tossed into the pot? And if I then add
> Xalan, do I get the right one?
>
> --benson
>

> On Sat, Nov 21, 2009 at 10:24 PM, Michael Glavassevich
<mrglavas@ca.ibm.com
> > wrote:
> Hi Benson,
>
> We're talking about two different implementations of the DOM Level 3
> LSSerializer, the more recently developed one in Xalan
> (serializer.jar which Xerces now ships and shares with Xalan) and
> the much older deprecated one in Xerces. If you're curious about the
> history on that, there's an FAQ [1] on the website.
>
> Some users have decided to keep using Xerces' deprecated serializer
> due to some quirks and issues with the currently available one from
> Xalan. Folks really should be opening JIRA issues [2] against Xalan,
> so those problems get addressed there. There's no intention to do
> any further development or fixes to the one in Xerces.
>
> Thanks.
>
> [1] http://xerces.apache.org/xerces2-j/faq-general.html#faq-6
> [2] https://issues.apache.org/jira/browse/XALANJ
>
>
> Michael Glavassevich
> XML Parser Development
> IBM Toronto Lab
> E-mail: mrglavas@ca.ibm.com
> E-mail: mrglavas@apache.org

> Benson Margulies <bimargulies@gmail.com> wrote on 11/21/2009 02:17:49 PM:
>
>
> > Could I please ask for a bit of clarification? The only LSSerializer
> > I'm aware of is the DOM level 3 stuff, which, I thought, was the
> > opposite of obsolete. As someone pointed out here, unlike TraX, it
> > will serialize doctypes and do other handy things. In general, I'm
> > beginning to prefer the DOMImplementationLS to JAXP and TraX.
>
> > On Sat, Nov 21, 2009 at 2:07 PM, Michael Glavassevich
<mrglavas@ca.ibm.com
> > > wrote:
> > You should also be able to control whether spaces are preserved by
> > registering an LSSerializerFilter.
> >
> > When I added one to your test program:
> >
> >         if (useXerces)
> >         {
> >             domWriter = new DOMSerializerImpl();
> >             domWriter.setFilter(new LSSerializerFilter() {
> >                 public int getWhatToShow() {
> >                     return LSSerializerFilter.SHOW_ALL;
> >                 }
> >                 public short acceptNode(Node n) {
> >                     return LSSerializerFilter.FILTER_ACCEPT;
> >                 }});
> >         }
> >
> > the output I get is:
> >
> >
> > Program started
> > Xerces serializer will be used
> > <?xml version="1.0" encoding="UTF-16"?>
> > <root>
> > <child1>text</child1>
> > <child2> </child2>
> >
> > </root>
> >
> > Xalan serializer will be used
> > <?xml version="1.0" encoding="UTF-16"?><root>
> > <child1>text</child1>
> > <child2> </child2>
> > </root>
>
> > which I believe is what you were expecting.
> >
> > Thanks.
> >
> > Michael Glavassevich
> > XML Parser Development
> > IBM Toronto Lab
> > E-mail: mrglavas@ca.ibm.com
> > E-mail: mrglavas@apache.org
> >
> > Dick Deneer <dick.deneer@donkeydevelopment.com> wrote on 11/21/2009
> > 01:19:27 PM:
> >
> >
> > > Hi Jake,
> > >
> > >
> > > I just tried your suggestion and the spaces are indeed preserved.
> > > But still, I woud prefer another solution. I do not have any clue
> > > about the xml (I use xerces in a xml editor) and I do not want to
> > > change the xml.
> > > And also I would like to stay with the LSSerializer (it also
> > > serilalizes doctype nodes).
> > > If there is another way please let me know.
> > >
> > > Thanks
> > > Dick Deneer
> > >
> > >
> > >
> > > Op 21-nov-2009, om 19:03 heeft Jacob Kjome het volgende geschreven:
> > >
> > > > Have you tried xml:space="preserve"?
> > > >
> > > > Jake
> > > >
> > > > On 11/20/2009 4:36 PM, Dick Deneer wrote:
> > > >> I am still using the deprecated LSSerializer because the xalan
> > > >> serializer has issues with the pretty print.
> > > >> But when I have simple elements with only space, the serializer
> > > >> produces
> > > >> empty elements. Is there a tweak to keep the spaces in this
elements?
> > > >>
> > > >> Sample xml:
> > > >> <root><child1>text</child1><child2> </child2></root>
> > > >> I attached a simple test program, that you can just run to see the

> > > >> results:
> > > >>
> > > >> Program started
> > > >> Xerces serializer will be used
> > > >> <?xml version="1.0" encoding="UTF-16"?>
> > > >> <root>
> > > >> <child1>text</child1>
> > > >> <child2/>
> > > >> </root>
> > > >>
> > > >> Xalan serializer will be used
> > > >> <?xml version="1.0" encoding="UTF-16"?><root>
> > > >> <child1>text</child1>
> > > >> <child2> </child2>
> > > >> </root>
> > > >>
> > > >> Regards
> > > >> Dick Deneer
> > > >>
> > > >>
---------------------------------------------------------------------
> > > >> ---
> > > >>
> > > >
> > > >
---------------------------------------------------------------------
> > > > To unsubscribe, e-mail: j-users-unsubscribe@xerces.apache.org
> > > > For additional commands, e-mail: j-users-help@xerces.apache.org
> > > >
> > >
> > >
> > > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: j-users-unsubscribe@xerces.apache.org
> > > For additional commands, e-mail: j-users-help@xerces.apache.org
Re: Loosing significant space in LSSerializer Dick Deneer <dick.deneer@donkeydevelopment.com> urn:uuid:%3cA6DF95FC-9A44-43EA-B9AC-D2CCCBF2B6B2@donkeydevelopment-com%3e 2009-11-22T21:06:06Z 
Hi Benson,

As Michael notes, Xerces is now shipped with the serializer.jar  
(which contains the xalan serializer). If you have this on your  
classpath it will be used.
If you leave it out, then xerces will fall back to it's own  
(deprecated) one.

regards
Dick Deneer
Op 22-nov-2009, om 21:54 heeft Benson Margulies het volgende geschreven:

> Hi Michael,
>
> So, if I put Xerces and not Xalan into classpath, and ask a  
> document for it's implementation, and ask that for the  
> DOMImplementationLS, what do I get? Whatever Sun tossed into the  
> pot? And if I then add Xalan, do I get the right one?
>
> --benson
>
>
> On Sat, Nov 21, 2009 at 10:24 PM, Michael Glavassevich  
> <mrglavas@ca.ibm.com> wrote:
> Hi Benson,
>
> We're talking about two different implementations of the DOM Level  
> 3 LSSerializer, the more recently developed one in Xalan  
> (serializer.jar which Xerces now ships and shares with Xalan) and  
> the much older deprecated one in Xerces. If you're curious about  
> the history on that, there's an FAQ [1] on the website.
>
> Some users have decided to keep using Xerces' deprecated serializer  
> due to some quirks and issues with the currently available one from  
> Xalan. Folks really should be opening JIRA issues [2] against  
> Xalan, so those problems get addressed there. There's no intention  
> to do any further development or fixes to the one in Xerces.
>
> Thanks.
>
> [1] http://xerces.apache.org/xerces2-j/faq-general.html#faq-6
> [2] https://issues.apache.org/jira/browse/XALANJ
>
>
>
> Michael Glavassevich
> XML Parser Development
> IBM Toronto Lab
> E-mail: mrglavas@ca.ibm.com
> E-mail: mrglavas@apache.org
>
> Benson Margulies <bimargulies@gmail.com> wrote on 11/21/2009  
> 02:17:49 PM:
>
>
> > Could I please ask for a bit of clarification? The only LSSerializer
> > I'm aware of is the DOM level 3 stuff, which, I thought, was the
> > opposite of obsolete. As someone pointed out here, unlike TraX, it
> > will serialize doctypes and do other handy things. In general, I'm
> > beginning to prefer the DOMImplementationLS to JAXP and TraX.
>
> > On Sat, Nov 21, 2009 at 2:07 PM, Michael Glavassevich  
> <mrglavas@ca.ibm.com
> > > wrote:
> > You should also be able to control whether spaces are preserved by
> > registering an LSSerializerFilter.
> >
> > When I added one to your test program:
> >
> >         if (useXerces)
> >         {
> >             domWriter = new DOMSerializerImpl();
> >             domWriter.setFilter(new LSSerializerFilter() {
> >                 public int getWhatToShow() {
> >                     return LSSerializerFilter.SHOW_ALL;
> >                 }
> >                 public short acceptNode(Node n) {
> >                     return LSSerializerFilter.FILTER_ACCEPT;
> >                 }});
> >         }
> >
> > the output I get is:
> >
> >
> > Program started
> > Xerces serializer will be used
> > <?xml version="1.0" encoding="UTF-16"?>
> > <root>
> > <child1>text</child1>
> > <child2> </child2>
> >
> > </root>
> >
> > Xalan serializer will be used
> > <?xml version="1.0" encoding="UTF-16"?><root>
> > <child1>text</child1>
> > <child2> </child2>
> > </root>
>
> > which I believe is what you were expecting.
> >
> > Thanks.
> >
> > Michael Glavassevich
> > XML Parser Development
> > IBM Toronto Lab
> > E-mail: mrglavas@ca.ibm.com
> > E-mail: mrglavas@apache.org
> >
> > Dick Deneer <dick.deneer@donkeydevelopment.com> wrote on 11/21/2009
> > 01:19:27 PM:
> >
> >
> > > Hi Jake,
> > >
> > >
> > > I just tried your suggestion and the spaces are indeed preserved.
> > > But still, I woud prefer another solution. I do not have any clue
> > > about the xml (I use xerces in a xml editor) and I do not want to
> > > change the xml.
> > > And also I would like to stay with the LSSerializer (it also
> > > serilalizes doctype nodes).
> > > If there is another way please let me know.
> > >
> > > Thanks
> > > Dick Deneer
> > >
> > >
> > >
> > > Op 21-nov-2009, om 19:03 heeft Jacob Kjome het volgende  
> geschreven:
> > >
> > > > Have you tried xml:space="preserve"?
> > > >
> > > > Jake
> > > >
> > > > On 11/20/2009 4:36 PM, Dick Deneer wrote:
> > > >> I am still using the deprecated LSSerializer because the xalan
> > > >> serializer has issues with the pretty print.
> > > >> But when I have simple elements with only space, the serializer
> > > >> produces
> > > >> empty elements. Is there a tweak to keep the spaces in this  
> elements?
> > > >>
> > > >> Sample xml:
> > > >> <root><child1>text</child1><child2> </child2></root>
> > > >> I attached a simple test program, that you can just run to  
> see the
> > > >> results:
> > > >>
> > > >> Program started
> > > >> Xerces serializer will be used
> > > >> <?xml version="1.0" encoding="UTF-16"?>
> > > >> <root>
> > > >> <child1>text</child1>
> > > >> <child2/>
> > > >> </root>
> > > >>
> > > >> Xalan serializer will be used
> > > >> <?xml version="1.0" encoding="UTF-16"?><root>
> > > >> <child1>text</child1>
> > > >> <child2> </child2>
> > > >> </root>
> > > >>
> > > >> Regards
> > > >> Dick Deneer
> > > >>
> > > >>  
> ---------------------------------------------------------------------
> > > >> ---
> > > >>
> > > >
> > > >  
> ---------------------------------------------------------------------
> > > > To unsubscribe, e-mail: j-users-unsubscribe@xerces.apache.org
> > > > For additional commands, e-mail: j-users-help@xerces.apache.org
> > > >
> > >
> > >
> > >  
> ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: j-users-unsubscribe@xerces.apache.org
> > > For additional commands, e-mail: j-users-help@xerces.apache.org
>
Re: Loosing significant space in LSSerializer Benson Margulies <bimargulies@gmail.com> urn:uuid:%3c61b5d9410911221254u1c801f5fhbec2d335b8637f2e@mail-gmail-com%3e 2009-11-22T20:54:37Z 
Hi Michael,

So, if I put Xerces and not Xalan into classpath, and ask a document for
it's implementation, and ask that for the DOMImplementationLS, what do I
get? Whatever Sun tossed into the pot? And if I then add Xalan, do I get the
right one?

--benson


On Sat, Nov 21, 2009 at 10:24 PM, Michael Glavassevich
<mrglavas@ca.ibm.com>wrote:

> Hi Benson,
>
> We're talking about two different implementations of the DOM Level 3
> LSSerializer, the more recently developed one in Xalan (serializer.jar which
> Xerces now ships and shares with Xalan) and the much older deprecated one in
> Xerces. If you're curious about the history on that, there's an FAQ [1] on
> the website.
>
> Some users have decided to keep using Xerces' deprecated serializer due to
> some quirks and issues with the currently available one from Xalan. Folks
> really should be opening JIRA issues [2] against Xalan, so those problems
> get addressed there. There's no intention to do any further development or
> fixes to the one in Xerces.
>
> Thanks.
>
> [1] http://xerces.apache.org/xerces2-j/faq-general.html#faq-6
> [2] https://issues.apache.org/jira/browse/XALANJ
>
>
> Michael Glavassevich
> XML Parser Development
> IBM Toronto Lab
> E-mail: mrglavas@ca.ibm.com
> E-mail: mrglavas@apache.org
>
> Benson Margulies <bimargulies@gmail.com> wrote on 11/21/2009 02:17:49 PM:
>
>
> > Could I please ask for a bit of clarification? The only LSSerializer
> > I'm aware of is the DOM level 3 stuff, which, I thought, was the
> > opposite of obsolete. As someone pointed out here, unlike TraX, it
> > will serialize doctypes and do other handy things. In general, I'm
> > beginning to prefer the DOMImplementationLS to JAXP and TraX.
>
> > On Sat, Nov 21, 2009 at 2:07 PM, Michael Glavassevich <
> mrglavas@ca.ibm.com
> > > wrote:
> > You should also be able to control whether spaces are preserved by
> > registering an LSSerializerFilter.
> >
> > When I added one to your test program:
> >
> >         if (useXerces)
> >         {
> >             domWriter = new DOMSerializerImpl();
> >             domWriter.setFilter(new LSSerializerFilter() {
> >                 public int getWhatToShow() {
> >                     return LSSerializerFilter.SHOW_ALL;
> >                 }
> >                 public short acceptNode(Node n) {
> >                     return LSSerializerFilter.FILTER_ACCEPT;
> >                 }});
> >         }
> >
> > the output I get is:
> >
> >
> > Program started
> > Xerces serializer will be used
> > <?xml version="1.0" encoding="UTF-16"?>
> > <root>
> > <child1>text</child1>
> > <child2> </child2>
> >
> > </root>
> >
> > Xalan serializer will be used
> > <?xml version="1.0" encoding="UTF-16"?><root>
> > <child1>text</child1>
> > <child2> </child2>
> > </root>
>
> > which I believe is what you were expecting.
> >
> > Thanks.
> >
> > Michael Glavassevich
> > XML Parser Development
> > IBM Toronto Lab
> > E-mail: mrglavas@ca.ibm.com
> > E-mail: mrglavas@apache.org
> >
> > Dick Deneer <dick.deneer@donkeydevelopment.com> wrote on 11/21/2009
> > 01:19:27 PM:
> >
> >
> > > Hi Jake,
> > >
> > >
> > > I just tried your suggestion and the spaces are indeed preserved.
> > > But still, I woud prefer another solution. I do not have any clue
> > > about the xml (I use xerces in a xml editor) and I do not want to
> > > change the xml.
> > > And also I would like to stay with the LSSerializer (it also
> > > serilalizes doctype nodes).
> > > If there is another way please let me know.
> > >
> > > Thanks
> > > Dick Deneer
> > >
> > >
> > >
> > > Op 21-nov-2009, om 19:03 heeft Jacob Kjome het volgende geschreven:
> > >
> > > > Have you tried xml:space="preserve"?
> > > >
> > > > Jake
> > > >
> > > > On 11/20/2009 4:36 PM, Dick Deneer wrote:
> > > >> I am still using the deprecated LSSerializer because the xalan
> > > >> serializer has issues with the pretty print.
> > > >> But when I have simple elements with only space, the serializer
> > > >> produces
> > > >> empty elements. Is there a tweak to keep the spaces in this
> elements?
> > > >>
> > > >> Sample xml:
> > > >> <root><child1>text</child1><child2> </child2></root>
> > > >> I attached a simple test program, that you can just run to see the
> > > >> results:
> > > >>
> > > >> Program started
> > > >> Xerces serializer will be used
> > > >> <?xml version="1.0" encoding="UTF-16"?>
> > > >> <root>
> > > >> <child1>text</child1>
> > > >> <child2/>
> > > >> </root>
> > > >>
> > > >> Xalan serializer will be used
> > > >> <?xml version="1.0" encoding="UTF-16"?><root>
> > > >> <child1>text</child1>
> > > >> <child2> </child2>
> > > >> </root>
> > > >>
> > > >> Regards
> > > >> Dick Deneer
> > > >>
> > > >>
> ---------------------------------------------------------------------
> > > >> ---
> > > >>
> > > >
> > > > ---------------------------------------------------------------------
> > > > To unsubscribe, e-mail: j-users-unsubscribe@xerces.apache.org
> > > > For additional commands, e-mail: j-users-help@xerces.apache.org
> > > >
> > >
> > >
> > > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: j-users-unsubscribe@xerces.apache.org
> > > For additional commands, e-mail: j-users-help@xerces.apache.org
>
Re: Loosing significant space in LSSerializer Michael Glavassevich <mrglavas@ca.ibm.com> urn:uuid:%3cOF6D78CBA1-E93F2A55-ON85257676-005575B6-85257676-0055A442@ca-ibm-com%3e 2009-11-22T15:35:25Z 
Content-type: text/plain; charset=US-ASCII

(Copying xalan-j-users to this thread.)

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

Michael Glavassevich <mrglavas@ca.ibm.com> wrote on 11/22/2009 10:30:49 AM:

> Dick Deneer <dick.deneer@donkeydevelopment.com> wrote on 11/22/2009
> 06:33:28 AM:
>
> > Michael,
> >
> > Thank you for this suggestion.
> > I can use this. Before I call the serializer I will strip off all
> > whitespace in "whitespace-only" complex nodes because otherwise I do
> > not get a pretty-print:
> > For example:
> > String xml = "<root>" +
> > "                                  <child1>text</child1><child2>
> > </child2></root>";
> > results in :
> > <?xml version="1.0" encoding="UTF-16"?>
> > <root>                                  <child1>text</child1>
> >     <child2>   </child2>
> > </root>
> >
> > But stripping of this whitespace before will not be too difficult.
> >
> > I feel it is a pitty that the LSSerializer will not be maintained
> > anymore, because we do not have alternatives that supply the same
> > functionality.
>
> It is in Xalan. Their serializer started as a copy of the Xerces one
> (even has similar package names: org.apache.xml.serialize vs.
> org.apache.xml.serializer). We didn't want to duplicate the effort
> anymore and decided to combine forces and the Xalan one was chosen
> as the common codebase because it was better maintained and was
> making significant improvements to performance. Its LSSerializer
> implementation was written by a Xerces committer and I have made
> improvements and fixes to it too where I've found issues, so it's
> being jointly maintained, though in a different project. This is the
> alternative. It *is* an LSSerializer and there is no reason that it
> can't be updated / fixed to have similar behaviour, but that's only
> likely to happen if users report the problems they're having
> (patches are welcome), preferably in JIRA.
>
> > I am afraid that maybe in the future there may be new xml (or DOM)
> > feautures that have effects on the serialization. Then we are
> > totally dependent on other libraries to implement that functionality.
> >
> > But I understand you have to make choices where to spent the effort.
> >
> > Thanks
> > Dick Deneer
>
> Thanks.
>
> Michael Glavassevich
> XML Parser Development
> IBM Toronto Lab
> E-mail: mrglavas@ca.ibm.com
> E-mail: mrglavas@apache.org
Re: Loosing significant space in LSSerializer Michael Glavassevich <mrglavas@ca.ibm.com> urn:uuid:%3cOF61AF2187-22732401-ON85257676-00526147-85257676-00553896@ca-ibm-com%3e 2009-11-22T15:30:49Z 
Content-type: text/plain; charset=US-ASCII
Content-transfer-encoding: quoted-printable


Dick Deneer <dick.deneer@donkeydevelopment.com> wrote on 11/22/2009
06:33:28 AM:

> Michael,
>
> Thank you for this suggestion.
> I can use this. Before I call the serializer I will strip off all
> whitespace in "whitespace-only" complex nodes because otherwise I do
> not get a pretty-print:
> For example:
> String xml =3D "<root>" +
> "                                  <child1>text</child1><child2>
> </child2></root>";
> results in :
> <?xml version=3D"1.0" encoding=3D"UTF-16"?>
> <root>                                  <child1>text</child1>
>     <child2>   </child2>
> </root>
>
> But stripping of this whitespace before will not be too difficult.
>
> I feel it is a pitty that the LSSerializer will not be maintained
> anymore, because we do not have alternatives that supply the same
> functionality.

It is in Xalan. Their serializer started as a copy of the Xerces one (e=
ven
has similar package names: org.apache.xml.serialize vs.
org.apache.xml.serializer). We didn't want to duplicate the effort anym=
ore
and decided to combine forces and the Xalan one was chosen as the commo=
n
codebase because it was better maintained and was making significant
improvements to performance. Its LSSerializer implementation was writte=
n by
a Xerces committer and I have made improvements and fixes to it too whe=
re
I've found issues, so it's being jointly maintained, though in a differ=
ent
project. This is the alternative. It *is* an LSSerializer and there is =
no
reason that it can't be updated / fixed to have similar behaviour, but
that's only likely to happen if users report the problems they're havin=
g
(patches are welcome), preferably in JIRA.

> I am afraid that maybe in the future there may be new xml (or DOM)
> feautures that have effects on the serialization. Then we are
> totally dependent on other libraries to implement that functionality.=

>
> But I understand you have to make choices where to spent the effort.
>
> Thanks
> Dick Deneer

Thanks.

Michael Glavassevich
XML Parser Development
IBM Toronto Lab
E-mail: mrglavas@ca.ibm.com
E-mail: mrglavas@apache.org=
Re: Loosing significant space in LSSerializer Dick Deneer <dick.deneer@donkeydevelopment.com> urn:uuid:%3c2082D588-F9ED-4699-A8B7-E906E310A34A@donkeydevelopment-com%3e 2009-11-22T11:33:28Z 
Michael,

Thank you for this suggestion.
I can use this. Before I call the serializer I will strip off all  
whitespace in "whitespace-only" complex nodes because otherwise I do  
not get a pretty-print:
For example:
String xml = "<root>" +
				"                                  <child1>text</ 
child1><child2>   </child2></root>";
results in :
<?xml version="1.0" encoding="UTF-16"?>
<root>                                  <child1>text</child1>
     <child2>   </child2>
</root>

But stripping of this whitespace before will not be too difficult.

I feel it is a pitty that the LSSerializer will not be maintained  
anymore, because we do not have alternatives that supply the same  
functionality.
I am afraid that maybe in the future there may be new xml (or DOM)  
feautures that have effects on the serialization. Then we are totally  
dependent on other libraries to implement that functionality.


But I understand you have to make choices where to spent the effort.

Thanks
Dick Deneer


Op 21-nov-2009, om 20:07 heeft Michael Glavassevich het volgende  
geschreven:

> You should also be able to control whether spaces are preserved by  
> registering an LSSerializerFilter.
>
> When I added one to your test program:
>
>         if (useXerces)
>         {
>             domWriter = new DOMSerializerImpl();
>             domWriter.setFilter(new LSSerializerFilter() {
>                 public int getWhatToShow() {
>                     return LSSerializerFilter.SHOW_ALL;
>                 }
>                 public short acceptNode(Node n) {
>                     return LSSerializerFilter.FILTER_ACCEPT;
>                 }});
>         }
>
> the output I get is:
>
> Program started
> Xerces serializer will be used
> <?xml version="1.0" encoding="UTF-16"?>
> <root>
> <child1>text</child1>
> <child2> </child2>
> </root>
>
> Xalan serializer will be used
> <?xml version="1.0" encoding="UTF-16"?><root>
> <child1>text</child1>
> <child2> </child2>
> </root>
>
> which I believe is what you were expecting.
>
> Thanks.
>
> Michael Glavassevich
> XML Parser Development
> IBM Toronto Lab
> E-mail: mrglavas@ca.ibm.com
> E-mail: mrglavas@apache.org
>
> Dick Deneer <dick.deneer@donkeydevelopment.com> wrote on 11/21/2009  
> 01:19:27 PM:
>
> > Hi Jake,
> >
> >
> > I just tried your suggestion and the spaces are indeed preserved.
> > But still, I woud prefer another solution. I do not have any clue
> > about the xml (I use xerces in a xml editor) and I do not want to
> > change the xml.
> > And also I would like to stay with the LSSerializer (it also
> > serilalizes doctype nodes).
> > If there is another way please let me know.
> >
> > Thanks
> > Dick Deneer
> >
> >
> >
> > Op 21-nov-2009, om 19:03 heeft Jacob Kjome het volgende geschreven:
> >
> > > Have you tried xml:space="preserve"?
> > >
> > > Jake
> > >
> > > On 11/20/2009 4:36 PM, Dick Deneer wrote:
> > >> I am still using the deprecated LSSerializer because the xalan
> > >> serializer has issues with the pretty print.
> > >> But when I have simple elements with only space, the serializer
> > >> produces
> > >> empty elements. Is there a tweak to keep the spaces in this  
> elements?
> > >>
> > >> Sample xml:
> > >> <root><child1>text</child1><child2> </child2></root>
> > >> I attached a simple test program, that you can just run to see  
> the
> > >> results:
> > >>
> > >> Program started
> > >> Xerces serializer will be used
> > >> <?xml version="1.0" encoding="UTF-16"?>
> > >> <root>
> > >> <child1>text</child1>
> > >> <child2/>
> > >> </root>
> > >>
> > >> Xalan serializer will be used
> > >> <?xml version="1.0" encoding="UTF-16"?><root>
> > >> <child1>text</child1>
> > >> <child2> </child2>
> > >> </root>
> > >>
> > >> Regards
> > >> Dick Deneer
> > >>
> > >>  
> ---------------------------------------------------------------------
> > >> ---
> > >>
> > >
> > >  
> ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: j-users-unsubscribe@xerces.apache.org
> > > For additional commands, e-mail: j-users-help@xerces.apache.org
> > >
> >
> >
> >  
> ---------------------------------------------------------------------
> > To unsubscribe, e-mail: j-users-unsubscribe@xerces.apache.org
> > For additional commands, e-mail: j-users-help@xerces.apache.org
>
Re: Loosing significant space in LSSerializer Michael Glavassevich <mrglavas@ca.ibm.com> urn:uuid:%3cOFCE31A93D-D20934F1-ON85257676-0011C43D-85257676-0012B969@ca-ibm-com%3e 2009-11-22T03:24:30Z 
Content-type: text/plain; charset=ISO-8859-1
Content-transfer-encoding: quoted-printable


Hi Benson,

We're talking about two different implementations of the DOM Level 3
LSSerializer, the more recently developed one in Xalan (serializer.jar
which Xerces now ships and shares with Xalan) and the much older deprec=
ated
one in Xerces. If you're curious about the history on that, there's an =
FAQ
[1] on the website.

Some users have decided to keep using Xerces' deprecated serializer due=
 to
some quirks and issues with the currently available one from Xalan. Fol=
ks
really should be opening JIRA issues [2] against Xalan, so those proble=
ms
get addressed there. There's no intention to do any further development=
 or
fixes to the one in Xerces.

Thanks.

[1] http://xerces.apache.org/xerces2-j/faq-general.html#faq-6
[2] https://issues.apache.org/jira/browse/XALANJ

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

Benson Margulies <bimargulies@gmail.com> wrote on 11/21/2009 02:17:49 P=
M:

> Could I please ask for a bit of clarification? The only LSSerializer
> I'm aware of is the DOM level 3 stuff, which, I thought, was the
> opposite of obsolete. As someone pointed out here, unlike TraX, it
> will serialize doctypes and do other handy things. In general, I'm
> beginning to prefer the DOMImplementationLS to JAXP and TraX.

> On Sat, Nov 21, 2009 at 2:07 PM, Michael Glavassevich
<mrglavas@ca.ibm.com
> > wrote:
> You should also be able to control whether spaces are preserved by
> registering an LSSerializerFilter.
>
> When I added one to your test program:
>
> =A0 =A0 =A0 =A0 if (useXerces)
> =A0 =A0 =A0 =A0 {
> =A0 =A0 =A0 =A0 =A0 =A0 domWriter =3D new DOMSerializerImpl();
> =A0 =A0 =A0 =A0 =A0 =A0 domWriter.setFilter(new LSSerializerFilter() =
{
> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 public int getWhatToShow() {
> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 return LSSerializerFilter.SHO=
W_ALL;
> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 }
> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 public short acceptNode(Node n) {
> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 return LSSerializerFilter.FIL=
TER_ACCEPT;
> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 }});
> =A0 =A0 =A0 =A0 }
>
> the output I get is:
>
>
> Program started
> Xerces serializer will be used
> <?xml version=3D"1.0" encoding=3D"UTF-16"?>
> <root>
> <child1>text</child1>
> <child2> </child2>
>
> </root>
>
> Xalan serializer will be used
> <?xml version=3D"1.0" encoding=3D"UTF-16"?><root>
> <child1>text</child1>
> <child2> </child2>
> </root>

> which I believe is what you were expecting.
>
> Thanks.
>
> Michael Glavassevich
> XML Parser Development
> IBM Toronto Lab
> E-mail: mrglavas@ca.ibm.com
> E-mail: mrglavas@apache.org
>
> Dick Deneer <dick.deneer@donkeydevelopment.com> wrote on 11/21/2009
> 01:19:27 PM:
>
>
> > Hi Jake,
> >
> >
> > I just tried your suggestion and the spaces are indeed preserved.
> > But still, I woud prefer another solution. I do not have any clue
> > about the xml (I use xerces in a xml editor) and I do not want to
> > change the xml.
> > And also I would like to stay with the LSSerializer (it also
> > serilalizes doctype nodes).
> > If there is another way please let me know.
> >
> > Thanks
> > Dick Deneer
> >
> >
> >
> > Op 21-nov-2009, om 19:03 heeft Jacob Kjome het volgende geschreven:=

> >
> > > Have you tried xml:space=3D"preserve"?
> > >
> > > Jake
> > >
> > > On 11/20/2009 4:36 PM, Dick Deneer wrote:
> > >> I am still using the deprecated LSSerializer because the xalan
> > >> serializer has issues with the pretty print.
> > >> But when I have simple elements with only space, the serializer
> > >> produces
> > >> empty elements. Is there a tweak to keep the spaces in this
elements?
> > >>
> > >> Sample xml:
> > >> <root><child1>text</child1><child2> </child2></root>
> > >> I attached a simple test program, that you can just run to see t=
he
> > >> results:
> > >>
> > >> Program started
> > >> Xerces serializer will be used
> > >> <?xml version=3D"1.0" encoding=3D"UTF-16"?>
> > >> <root>
> > >> <child1>text</child1>
> > >> <child2/>
> > >> </root>
> > >>
> > >> Xalan serializer will be used
> > >> <?xml version=3D"1.0" encoding=3D"UTF-16"?><root>
> > >> <child1>text</child1>
> > >> <child2> </child2>
> > >> </root>
> > >>
> > >> Regards
> > >> Dick Deneer
> > >>
> > >>
---------------------------------------------------------------------
> > >> ---
> > >>
> > >
> > > -----------------------------------------------------------------=
----
> > > To unsubscribe, e-mail: j-users-unsubscribe@xerces.apache.org
> > > For additional commands, e-mail: j-users-help@xerces.apache.org
> > >
> >
> >
> > -------------------------------------------------------------------=
--
> > To unsubscribe, e-mail: j-users-unsubscribe@xerces.apache.org
> > For additional commands, e-mail: j-users-help@xerces.apache.org=
Re: Loosing significant space in LSSerializer Benson Margulies <bimargulies@gmail.com> urn:uuid:%3c61b5d9410911211117p4da6641fh49fa8316cbc83b41@mail-gmail-com%3e 2009-11-21T19:17:49Z 
Could I please ask for a bit of clarification? The only LSSerializer I'm
aware of is the DOM level 3 stuff, which, I thought, was the opposite of
obsolete. As someone pointed out here, unlike TraX, it will serialize
doctypes and do other handy things. In general, I'm beginning to prefer the
DOMImplementationLS to JAXP and TraX.

On Sat, Nov 21, 2009 at 2:07 PM, Michael Glavassevich
<mrglavas@ca.ibm.com>wrote:

> You should also be able to control whether spaces are preserved by
> registering an LSSerializerFilter.
>
> When I added one to your test program:
>
>         if (useXerces)
>         {
>             domWriter = new DOMSerializerImpl();
>             domWriter.setFilter(new LSSerializerFilter() {
>                 public int getWhatToShow() {
>                     return LSSerializerFilter.SHOW_ALL;
>                 }
>                 public short acceptNode(Node n) {
>                     return LSSerializerFilter.FILTER_ACCEPT;
>                 }});
>         }
>
> the output I get is:
>
>
> Program started
> Xerces serializer will be used
> <?xml version="1.0" encoding="UTF-16"?>
> <root>
>  <child1>text</child1>
>  <child2> </child2>
>
> </root>
>
> Xalan serializer will be used
> <?xml version="1.0" encoding="UTF-16"?><root>
>  <child1>text</child1>
>  <child2> </child2>
> </root>
>
> which I believe is what you were expecting.
>
> Thanks.
>
> Michael Glavassevich
> XML Parser Development
> IBM Toronto Lab
> E-mail: mrglavas@ca.ibm.com
> E-mail: mrglavas@apache.org
>
> Dick Deneer <dick.deneer@donkeydevelopment.com> wrote on 11/21/2009
> 01:19:27 PM:
>
>
> > Hi Jake,
> >
> >
> > I just tried your suggestion and the spaces are indeed preserved.
> > But still, I woud prefer another solution. I do not have any clue
> > about the xml (I use xerces in a xml editor) and I do not want to
> > change the xml.
> > And also I would like to stay with the LSSerializer (it also
> > serilalizes doctype nodes).
> > If there is another way please let me know.
> >
> > Thanks
> > Dick Deneer
> >
> >
> >
> > Op 21-nov-2009, om 19:03 heeft Jacob Kjome het volgende geschreven:
> >
> > > Have you tried xml:space="preserve"?
> > >
> > > Jake
> > >
> > > On 11/20/2009 4:36 PM, Dick Deneer wrote:
> > >> I am still using the deprecated LSSerializer because the xalan
> > >> serializer has issues with the pretty print.
> > >> But when I have simple elements with only space, the serializer
> > >> produces
> > >> empty elements. Is there a tweak to keep the spaces in this elements?
> > >>
> > >> Sample xml:
> > >> <root><child1>text</child1><child2> </child2></root>
> > >> I attached a simple test program, that you can just run to see the
> > >> results:
> > >>
> > >> Program started
> > >> Xerces serializer will be used
> > >> <?xml version="1.0" encoding="UTF-16"?>
> > >> <root>
> > >> <child1>text</child1>
> > >> <child2/>
> > >> </root>
> > >>
> > >> Xalan serializer will be used
> > >> <?xml version="1.0" encoding="UTF-16"?><root>
> > >> <child1>text</child1>
> > >> <child2> </child2>
> > >> </root>
> > >>
> > >> Regards
> > >> Dick Deneer
> > >>
> > >> ---------------------------------------------------------------------
> > >> ---
> > >>
> > >
> > > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: j-users-unsubscribe@xerces.apache.org
> > > For additional commands, e-mail: j-users-help@xerces.apache.org
> > >
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: j-users-unsubscribe@xerces.apache.org
> > For additional commands, e-mail: j-users-help@xerces.apache.org
>
Re: Loosing significant space in LSSerializer Michael Glavassevich <mrglavas@ca.ibm.com> urn:uuid:%3cOFE82F98E9-BB533770-ON85257675-0067F8C6-85257675-00690F8C@ca-ibm-com%3e 2009-11-21T19:07:32Z 
Content-type: text/plain; charset=US-ASCII

You should also be able to control whether spaces are preserved by
registering an LSSerializerFilter.

When I added one to your test program:

        if (useXerces)
        {
            domWriter = new DOMSerializerImpl();
            domWriter.setFilter(new LSSerializerFilter() {
                public int getWhatToShow() {
                    return LSSerializerFilter.SHOW_ALL;)
                }
                public short acceptNode(Node n) {
                    return LSSerializerFilter.FILTER_ACCEPT;
                }});
        }

the output I get is:

Program started
Xerces serializer will be used
<?xml version="1.0" encoding="UTF-16"?>
<root>
    <child1>text</child1>
    <child2>   </child2>>
</root>

Xalan serializer will be used
<?xml version="1.0" encoding="UTF-16"?><root>.
   <child1>text</child1>
   <child2>   </child2>>
</root>

which I believe is what you were expecting.

Thanks.

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

Dick Deneer <dick.deneer@donkeydevelopment.com> wrote on 11/21/2009
01:19:27 PM:

> Hi Jake,
>
>
> I just tried your suggestion and the spaces are indeed preserved.
> But still, I woud prefer another solution. I do not have any clue
> about the xml (I use xerces in a xml editor) and I do not want to
> change the xml.
> And also I would like to stay with the LSSerializer (it also
> serilalizes doctype nodes).
> If there is another way please let me know.
>
> Thanks
> Dick Deneer
>
>
>
> Op 21-nov-2009, om 19:03 heeft Jacob Kjome het volgende geschreven:
>
> > Have you tried xml:space="preserve"?
> >
> > Jake
> >
> > On 11/20/2009 4:36 PM, Dick Deneer wrote:
> >> I am still using the deprecated LSSerializer because the xalan
> >> serializer has issues with the pretty print.
> >> But when I have simple elements with only space, the serializer
> >> produces
> >> empty elements. Is there a tweak to keep the spaces in this elements?
> >>
> >> Sample xml:
> >> <root><child1>text</child1><child2> </child2></root>
> >> I attached a simple test program, that you can just run to see the
> >> results:
> >>
> >> Program started
> >> Xerces serializer will be used
> >> <?xml version="1.0" encoding="UTF-16"?>
> >> <root>
> >> <child1>text</child1>
> >> <child2/>
> >> </root>
> >>
> >> Xalan serializer will be used
> >> <?xml version="1.0" encoding="UTF-16"?><root>
> >> <child1>text</child1>
> >> <child2> </child2>
> >> </root>
> >>
> >> Regards
> >> Dick Deneer
> >>
> >> ---------------------------------------------------------------------
> >> ---
> >>
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: j-users-unsubscribe@xerces.apache.org
> > For additional commands, e-mail: j-users-help@xerces.apache.org
> >
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: j-users-unsubscribe@xerces.apache.org
> For additional commands, e-mail: j-users-help@xerces.apache.org
Re: Loosing significant space in LSSerializer Dick Deneer <dick.deneer@donkeydevelopment.com> urn:uuid:%3c4CCD4C3B-32AF-4D98-8C38-502AAA9DD88B@donkeydevelopment-com%3e 2009-11-21T18:19:27Z 
Hi Jake,


I just tried your suggestion and the spaces are indeed preserved.
But still, I woud prefer another solution. I do not have any clue  
about the xml (I use xerces in a xml editor) and I do not want to  
change the xml.
And also I would like to stay with the LSSerializer (it also  
serilalizes doctype nodes).
If there is another way please let me know.

Thanks
Dick Deneer



Op 21-nov-2009, om 19:03 heeft Jacob Kjome het volgende geschreven:

> Have you tried xml:space="preserve"?
>
> Jake
>
> On 11/20/2009 4:36 PM, Dick Deneer wrote:
>> I am still using the deprecated LSSerializer because the xalan
>> serializer has issues with the pretty print.
>> But when I have simple elements with only space, the serializer  
>> produces
>> empty elements. Is there a tweak to keep the spaces in this elements?
>>
>> Sample xml:
>> <root><child1>text</child1><child2> </child2></root>
>> I attached a simple test program, that you can just run to see the  
>> results:
>>
>> Program started
>> Xerces serializer will be used
>> <?xml version="1.0" encoding="UTF-16"?>
>> <root>
>> <child1>text</child1>
>> <child2/>
>> </root>
>>
>> Xalan serializer will be used
>> <?xml version="1.0" encoding="UTF-16"?><root>
>> <child1>text</child1>
>> <child2> </child2>
>> </root>
>>
>> Regards
>> Dick Deneer
>>
>> --------------------------------------------------------------------- 
>> ---
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: j-users-unsubscribe@xerces.apache.org
> For additional commands, e-mail: j-users-help@xerces.apache.org
>


---------------------------------------------------------------------
To unsubscribe, e-mail: j-users-unsubscribe@xerces.apache.org
For additional commands, e-mail: j-users-help@xerces.apache.org
Re: Loosing significant space in LSSerializer Jacob Kjome <hoju@visi.com> urn:uuid:%3c4B082B71-2090307@visi-com%3e 2009-11-21T18:03:29Z 
Have you tried xml:space="preserve"?

Jake

On 11/20/2009 4:36 PM, Dick Deneer wrote:
> I am still using the deprecated LSSerializer because the xalan
> serializer has issues with the pretty print.
> But when I have simple elements with only space, the serializer produces
> empty elements. Is there a tweak to keep the spaces in this elements?
>
> Sample xml:
> <root><child1>text</child1><child2> </child2></root>
> I attached a simple test program, that you can just run to see the results:
>
> Program started
> Xerces serializer will be used
> <?xml version="1.0" encoding="UTF-16"?>
> <root>
> <child1>text</child1>
> <child2/>
> </root>
>
> Xalan serializer will be used
> <?xml version="1.0" encoding="UTF-16"?><root>
> <child1>text</child1>
> <child2> </child2>
> </root>
>
> Regards
> Dick Deneer
>
> ------------------------------------------------------------------------
>

---------------------------------------------------------------------
To unsubscribe, e-mail: j-users-unsubscribe@xerces.apache.org
For additional commands, e-mail: j-users-help@xerces.apache.org
Loosing significant space in LSSerializer Dick Deneer <dick.deneer@donkeydevelopment.com> urn:uuid:%3c45DAB5D0-C20E-4E3D-B1B9-0ED7E48D774D@donkeydevelopment-com%3e 2009-11-20T22:36:36Z 
I am still using the deprecated LSSerializer  because the xalan  
serializer has issues with the pretty print.
But when I have simple elements with only space, the serializer  
produces empty elements. Is there a tweak to keep the spaces in this  
elements?

Sample xml:
<root><child1>text</child1><child2>   </child2></root>
I attached a simple test program, that you can just run to see the  
results:

Program started
Xerces serializer will be used
<?xml version="1.0" encoding="UTF-16"?>
<root>
     <child1>text</child1>
     <child2/>
</root>

Xalan serializer will be used
<?xml version="1.0" encoding="UTF-16"?><root>
    <child1>text</child1>
    <child2>   </child2>
</root>

Regards
Dick Deneer
Re: xs:any namespace resolution Michael Glavassevich <mrglavas@ca.ibm.com> urn:uuid:%3cOF65E3570F-7D5A61E0-ON85257673-00615001-85257673-007770B2@ca-ibm-com%3e 2009-11-19T21:44:19Z 
Content-type: text/plain; charset=ISO-8859-1
Content-transfer-encoding: quoted-printable


Ajay,

If you want schemas to be dynamically loaded by the validator you need =
to
use the SchemaFactory.newSchema() method [1] (the one with no parameter=
s).
JAXP doesn't let you mix that with pre-loading of schemas. See [2][3] i=
n
the mailing list archives for more details.

Thanks.

[1]
http://xerces.apache.org/xerces2-j/javadocs/api/javax/xml/validation/Sc=
hemaFactory.html#newSchema
()
[2] http://markmail.org/message/5xe4u5njgxkiosk7
[3] http://markmail.org/message/4nhwp7ggi6fytqfg

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

ajay bhadauria <abhadauria@yahoo.com> wrote on 11/19/2009 12:25:17 PM:

> Michael,
>
> Sorry. I was over excited. I was doing the same way as you suggested
> but my LSResourceResolver is not getting called which means that I
> am missing something which I am not aware of it.
>
> The Test2.xml which I attached in the previous mail, the tag
> "ns1:Document" contains namespace xmlns:ns1=3D"urn:swift:xsd:$xtsn.
> 998.001.01" which is on the 2.xsd.
>
> Please find the attached Code where I set LSresourceResolver to
Validator.
>
> Thanks
> Ajay
> --- On Thu, 11/19/09, Michael Glavassevich <mrglavas@ca.ibm.com> wrot=
e:
>
> > From: Michael Glavassevich <mrglavas@ca.ibm.com>
> > Subject: Re: xs:any namespace resolution
> > To: j-users@xerces.apache.org
> > Date: Thursday, November 19, 2009, 8:32 PM
> >
> > (Ajay, patience. In the future, please don't
> > post the same message over and over again to the list. We
> > heard you the first time.)
> >
> >
> >
> > Try writing an LSResourceResolver (which you would
> > register with the validator) and have that return the 2nd
> > schema document on the request with its target
> > namespace.
> >
> >
> >
> > Thanks.
> >
> >
> >
> > Michael Glavassevich
> >
> > XML Parser Development
> >
> > IBM Toronto Lab
> >
> > E-mail: mrglavas@ca.ibm.com
> >
> > E-mail: mrglavas@apache.org
> >
> >
> >
> > ajay bhadauria <abhadauria@yahoo.com> wrote on
> > 11/19/2009 09:15:03 AM:
> >
> >
> >
> > > Hi,
> >
> > >
> >
> > > I do knot know much about xs:any construct and I
> > =A0am new to this and
> >
> > > I read it but I do not know how I can tell the
> > validator to use
> >
> > > namespace (only runtime) which is defined in the
> > different schema.
> >
> > >
> >
> > > Using
> >
> > > <xs:any
> >
> > > > =A0namespace=3D"##any"
> > processContents=3D"strict"/> construct,
> >
> > >
> >
> > > I am vlidating xml instance with Validator which has a
> > main schema
> >
> > > but validator does not know second schema.
> >
> > >
> >
> > > Now, =A0how I can tell the validator during
> > validation time about the
> >
> > > second schema to which some elements belong to the
> > namespace which
> >
> > > is defined in the second schema.
> >
> > >
> >
> > > Thanks
> >
> > > ajay
> >
> > >
> >
> > > --- On Thu, 11/19/09, ajay bhadauria
> > <abhadauria@yahoo.com> wrote:
> >
> > >
> >
> > > > From: ajay bhadauria
> > <abhadauria@yahoo.com>
> >
> > > > Subject: Re: xs:any namespace resolution
> >
> > > > To: j-users@xerces.apache.org
> >
> > > > Date: Thursday, November 19, 2009, 6:38 AM
> >
> > > > Hi,
> >
> > > >
> >
> > > > I am using <xs:any
> >
> > > > > namespace=3D"##any"
> > processContents=3D"strict"/> and I
> >
> > > > am validating xml instance which is having
> > elements which
> >
> > > > belong to the different namespace and
> > corresponding to this
> >
> > > > namespace, schema is not pre-loaded. I mean yhat
> > external
> >
> > > > schema is not pre-loaded.
> >
> > > >
> >
> > > > How do I tell Java Validator about this external
> > schema so
> >
> > > > that xml instance is validated successfully ?
> >
> > > >
> >
> > > >
> >
> > > > Is there any way I can tell the validator at the
> > time of
> >
> > > > validation only about external schema which is
> > not
> >
> > > > pre-loaded with main schema?
> >
> > > >
> >
> > > > Help me in understanding whether it can be done
> > ???
> >
> > > > Thanks
> >
> > > > Ajay
> >
> > > >
> >
> > > > --- On Thu, 11/19/09, ajay bhadauria
> > <abhadauria@yahoo.com>
> >
> > > > wrote:
> >
> > > >
> >
> > > > > From: ajay bhadauria
> > <abhadauria@yahoo.com>
> >
> > > > > Subject: xs:any namespace resolution
> >
> > > > > To: j-users@xerces.apache.org
> >
> > > > > Date: Thursday, November 19, 2009, 12:48 AM
> >
> > > > > Hi,
> >
> > > > >
> >
> > > > > I have schema file 1.xsd which has xs:any
> > schema
> >
> > > > construct
> >
> > > > >
> >
> > > > > <xs:complexType
> > name=3D"ExtensionEnvelope">
> >
> > > > >
> >
> > > > =A0=A0=A0<xs:sequence>
> >
> > > > >
> >
> > > > =A0=A0=A0<xs:any
> >
> > > > > namespace=3D"##any"
> > processContents=3D"strict"/>
> >
> > > > >
> >
> > > > =A0=A0=A0</xs:sequence>
> >
> > > > >=A0 =A0=A0=A0</xs:complexType>
> >
> > > > >
> >
> > > > > And I try to validate xml instance (
> > test2.xml )
> >
> > > > against
> >
> > > > > this schema, it gave the following error
> >
> > > > >=A0 =A0 =A0 cvc-complex-type.2.4.c: The
> >
> > > > > matching wildcard is strict, but no
> > declaration can be
> >
> > > > found
> >
> > > > > for element 'ns1:Document'.
> >
> > > > >
> >
> > > > > However, the namespace which the Validator
> > is looking
> >
> > > > for
> >
> > > > > is in other xsd file (2.xsd).
> >
> > > > >
> >
> > > > > How do I tell Validator the location of
> > 2.xsd file
> >
> > > > during
> >
> > > > > validation ?
> >
> > > > >
> >
> > > > > The test.xml has some elements which belong
> > to the
> >
> > > > > namespace urn:swift:xsd:$xtsn.998.001.01
> > which is
> >
> > > > defined in
> >
> > > > > the 2.xsd file.
> >
> > > > >
> >
> > > > >
> >
> > > > >
> >
> > > > >
> >
> > > >
> > -------------------------------------------------------------------=
--
> >
> > > > > To unsubscribe, e-mail:
> > j-users-unsubscribe@xerces.apache.org
> >
> > > > > For additional commands, e-mail:
> > j-users-help@xerces.apache.org
> >
> > > >
> >
> > > >
> >
> > > >
> >
> > > >
> >
> > > >
> > -------------------------------------------------------------------=
--
> >
> > > > To unsubscribe, e-mail:
> > j-users-unsubscribe@xerces.apache.org
> >
> > > > For additional commands, e-mail:
> > j-users-help@xerces.apache.org
> >
> > >
> >
> > >
> >
> > >
> > -------------------------------------------------------------------=
--
> >
> > > To unsubscribe, e-mail:
> > j-users-unsubscribe@xerces.apache.org
> >
> > > For additional commands, e-mail:
> > j-users-help@xerces.apache.org
> >
> >
>
>
>       [attachment "SchemaReader.java" deleted by Michael
> Glavassevich/Toronto/IBM]
> ---------------------------------------------------------------------=

> To unsubscribe, e-mail: j-users-unsubscribe@xerces.apache.org
> For additional commands, e-mail: j-users-help@xerces.apache.org=
Re: xs:any namespace resolution ajay bhadauria <abhadauria@yahoo.com> urn:uuid:%3c817568-79294-qm@web111511-mail-gq1-yahoo-com%3e 2009-11-19T17:25:17Z 
Michael,

Sorry. I was over excited. I was doing the same way as you suggested but my LSResourceResolver
is not getting called which means that I am missing something which I am not aware of it.


The Test2.xml which I attached in the previous mail, the tag "ns1:Document" contains namespace
xmlns:ns1="urn:swift:xsd:$xtsn.998.001.01" which is on the 2.xsd.

Please find the attached Code where I set LSresourceResolver to Validator.

Thanks
Ajay 
--- On Thu, 11/19/09, Michael Glavassevich <mrglavas@ca.ibm.com> wrote:

> From: Michael Glavassevich <mrglavas@ca.ibm.com>
> Subject: Re: xs:any namespace resolution
> To: j-users@xerces.apache.org
> Date: Thursday, November 19, 2009, 8:32 PM
> 
> (Ajay, patience. In the future, please don't
> post the same message over and over again to the list. We
> heard you the first time.)
> 
> 
> 
> Try writing an LSResourceResolver (which you would
> register with the validator) and have that return the 2nd
> schema document on the request with its target
> namespace.
> 
> 
> 
> Thanks.
> 
> 
> 
> Michael Glavassevich
> 
> XML Parser Development
> 
> IBM Toronto Lab
> 
> E-mail: mrglavas@ca.ibm.com
> 
> E-mail: mrglavas@apache.org
> 
> 
> 
> ajay bhadauria <abhadauria@yahoo.com> wrote on
> 11/19/2009 09:15:03 AM:
> 
> 
> 
> > Hi,
> 
> > 
> 
> > I do knot know much about xs:any construct and I
>  am new to this and
> 
> > I read it but I do not know how I can tell the
> validator to use 
> 
> > namespace (only runtime) which is defined in the
> different schema.
> 
> >  
> 
> > Using  
> 
> > <xs:any
> 
> > >  namespace="##any"
> processContents="strict"/> construct, 
> 
> > 
> 
> > I am vlidating xml instance with Validator which has a
> main schema 
> 
> > but validator does not know second schema.  
> 
> > 
> 
> > Now,  how I can tell the validator during
> validation time about the 
> 
> > second schema to which some elements belong to the
> namespace which 
> 
> > is defined in the second schema.   
> 
> > 
> 
> > Thanks
> 
> > ajay
> 
> > 
> 
> > --- On Thu, 11/19/09, ajay bhadauria
> <abhadauria@yahoo.com> wrote:
> 
> > 
> 
> > > From: ajay bhadauria
> <abhadauria@yahoo.com>
> 
> > > Subject: Re: xs:any namespace resolution
> 
> > > To: j-users@xerces.apache.org
> 
> > > Date: Thursday, November 19, 2009, 6:38 AM
> 
> > > Hi,
> 
> > > 
> 
> > > I am using <xs:any
> 
> > > > namespace="##any"
> processContents="strict"/> and I
> 
> > > am validating xml instance which is having
> elements which
> 
> > > belong to the different namespace and
> corresponding to this
> 
> > > namespace, schema is not pre-loaded. I mean yhat
> external
> 
> > > schema is not pre-loaded.
> 
> > > 
> 
> > > How do I tell Java Validator about this external
> schema so
> 
> > > that xml instance is validated successfully ?
> 
> > > 
> 
> > > 
> 
> > > Is there any way I can tell the validator at the
> time of
> 
> > > validation only about external schema which is
> not
> 
> > > pre-loaded with main schema?
> 
> > > 
> 
> > > Help me in understanding whether it can be done
> ???
> 
> > > Thanks
> 
> > > Ajay 
> 
> > > 
> 
> > > --- On Thu, 11/19/09, ajay bhadauria
> <abhadauria@yahoo.com>
> 
> > > wrote:
> 
> > > 
> 
> > > > From: ajay bhadauria
> <abhadauria@yahoo.com>
> 
> > > > Subject: xs:any namespace resolution
> 
> > > > To: j-users@xerces.apache.org
> 
> > > > Date: Thursday, November 19, 2009, 12:48 AM
> 
> > > > Hi,
> 
> > > > 
> 
> > > > I have schema file 1.xsd which has xs:any
> schema
> 
> > > construct
> 
> > > >  
> 
> > > > <xs:complexType
> name="ExtensionEnvelope">
> 
> > > >     
> 
> > >    <xs:sequence>
> 
> > > >         
> 
> > >    <xs:any
> 
> > > > namespace="##any"
> processContents="strict"/>
> 
> > > >     
> 
> > >    </xs:sequence>
> 
> > > >     </xs:complexType>
> 
> > > > 
> 
> > > > And I try to validate xml instance (
> test2.xml )
> 
> > > against
> 
> > > > this schema, it gave the following error
> 
> > > >      cvc-complex-type.2.4.c: The
> 
> > > > matching wildcard is strict, but no
> declaration can be
> 
> > > found
> 
> > > > for element 'ns1:Document'.
> 
> > > > 
> 
> > > > However, the namespace which the Validator
> is looking
> 
> > > for
> 
> > > > is in other xsd file (2.xsd). 
> 
> > > > 
> 
> > > > How do I tell Validator the location of
> 2.xsd file
> 
> > > during
> 
> > > > validation ? 
> 
> > > > 
> 
> > > > The test.xml has some elements which belong
> to the
> 
> > > > namespace urn:swift:xsd:$xtsn.998.001.01
> which is
> 
> > > defined in
> 
> > > > the 2.xsd file.
> 
> > > > 
> 
> > > > 
> 
> > > >       
> 
> > > >
> 
> > >
> ---------------------------------------------------------------------
> 
> > > > To unsubscribe, e-mail:
> j-users-unsubscribe@xerces.apache.org
> 
> > > > For additional commands, e-mail:
> j-users-help@xerces.apache.org
> 
> > > 
> 
> > > 
> 
> > >       
> 
> > > 
> 
> > >
> ---------------------------------------------------------------------
> 
> > > To unsubscribe, e-mail:
> j-users-unsubscribe@xerces.apache.org
> 
> > > For additional commands, e-mail:
> j-users-help@xerces.apache.org
> 
> >       
> 
> > 
> 
> >
> ---------------------------------------------------------------------
> 
> > To unsubscribe, e-mail:
> j-users-unsubscribe@xerces.apache.org
> 
> > For additional commands, e-mail:
> j-users-help@xerces.apache.org
> 
>
Re: xs:any namespace resolution Michael Glavassevich <mrglavas@ca.ibm.com> urn:uuid:%3cOFD3A5C0B5-32985991-ON85257673-0051C79F-85257673-0052AD6F@ca-ibm-com%3e 2009-11-19T15:02:46Z 
Content-type: text/plain; charset=ISO-8859-1
Content-transfer-encoding: quoted-printable


(Ajay, patience. In the future, please don't post the same message over=
 and
over again to the list. We heard you the first time.)

Try writing an LSResourceResolver (which you would register with the
validator) and have that return the 2nd schema document on the request =
with
its target namespace.

Thanks.

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

ajay bhadauria <abhadauria@yahoo.com> wrote on 11/19/2009 09:15:03 AM:

> Hi,
>
> I do knot know much about xs:any construct and I  am new to this and
> I read it but I do not know how I can tell the validator to use
> namespace (only runtime) which is defined in the different schema.
>
> Using
> <xs:any
> >  namespace=3D"##any" processContents=3D"strict"/> construct,
>
> I am vlidating xml instance with Validator which has a main schema
> but validator does not know second schema.
>
> Now,  how I can tell the validator during validation time about the
> second schema to which some elements belong to the namespace which
> is defined in the second schema.
>
> Thanks
> ajay
>
> --- On Thu, 11/19/09, ajay bhadauria <abhadauria@yahoo.com> wrote:
>
> > From: ajay bhadauria <abhadauria@yahoo.com>
> > Subject: Re: xs:any namespace resolution
> > To: j-users@xerces.apache.org
> > Date: Thursday, November 19, 2009, 6:38 AM
> > Hi,
> >
> > I am using <xs:any
> > > namespace=3D"##any" processContents=3D"strict"/> and I
> > am validating xml instance which is having elements which
> > belong to the different namespace and corresponding to this
> > namespace, schema is not pre-loaded. I mean yhat external
> > schema is not pre-loaded.
> >
> > How do I tell Java Validator about this external schema so
> > that xml instance is validated successfully ?
> >
> >
> > Is there any way I can tell the validator at the time of
> > validation only about external schema which is not
> > pre-loaded with main schema?
> >
> > Help me in understanding whether it can be done ???
> > Thanks
> > Ajay
> >
> > --- On Thu, 11/19/09, ajay bhadauria <abhadauria@yahoo.com>
> > wrote:
> >
> > > From: ajay bhadauria <abhadauria@yahoo.com>
> > > Subject: xs:any namespace resolution
> > > To: j-users@xerces.apache.org
> > > Date: Thursday, November 19, 2009, 12:48 AM
> > > Hi,
> > >
> > > I have schema file 1.xsd which has xs:any schema
> > construct
> > >
> > > <xs:complexType name=3D"ExtensionEnvelope">
> > >
> > =A0=A0=A0<xs:sequence>
> > >
> > =A0=A0=A0<xs:any
> > > namespace=3D"##any" processContents=3D"strict"/>
> > >
> > =A0=A0=A0</xs:sequence>
> > >=A0 =A0=A0=A0</xs:complexType>
> > >
> > > And I try to validate xml instance ( test2.xml )
> > against
> > > this schema, it gave the following error
> > >=A0 =A0 =A0 cvc-complex-type.2.4.c: The
> > > matching wildcard is strict, but no declaration can be
> > found
> > > for element 'ns1:Document'.
> > >
> > > However, the namespace which the Validator is looking
> > for
> > > is in other xsd file (2.xsd).
> > >
> > > How do I tell Validator the location of 2.xsd file
> > during
> > > validation ?
> > >
> > > The test.xml has some elements which belong to the
> > > namespace urn:swift:xsd:$xtsn.998.001.01 which is
> > defined in
> > > the 2.xsd file.
> > >
> > >
> > >
> > >
> > -------------------------------------------------------------------=
--
> > > To unsubscribe, e-mail: j-users-unsubscribe@xerces.apache.org
> > > For additional commands, e-mail: j-users-help@xerces.apache.org
> >
> >
> >
> >
> > -------------------------------------------------------------------=
--
> > To unsubscribe, e-mail: j-users-unsubscribe@xerces.apache.org
> > For additional commands, e-mail: j-users-help@xerces.apache.org
>
>
> ---------------------------------------------------------------------=

> To unsubscribe, e-mail: j-users-unsubscribe@xerces.apache.org
> For additional commands, e-mail: j-users-help@xerces.apache.org=
Re: xs:any namespace resolution ajay bhadauria <abhadauria@yahoo.com> urn:uuid:%3c144319-39589-qm@web111512-mail-gq1-yahoo-com%3e 2009-11-19T14:15:03Z 
Hi,

I do knot know much about xs:any construct and I  am new to this and I read it but I do not
know how I can tell the validator to use namespace (only runtime) which is defined in the
different schema.
 
Using  
<xs:any
>  namespace="##any" processContents="strict"/> construct, 

I am vlidating xml instance with Validator which has a main schema but validator does not
know second schema.  

Now,  how I can tell the validator during validation time about the second schema to which
some elements belong to the namespace which is defined in the second schema.   

Thanks
ajay

--- On Thu, 11/19/09, ajay bhadauria <abhadauria@yahoo.com> wrote:

> From: ajay bhadauria <abhadauria@yahoo.com>
> Subject: Re: xs:any namespace resolution
> To: j-users@xerces.apache.org
> Date: Thursday, November 19, 2009, 6:38 AM
> Hi,
> 
> I am using <xs:any
> > namespace="##any" processContents="strict"/> and I
> am validating xml instance which is having elements which
> belong to the different namespace and corresponding to this
> namespace, schema is not pre-loaded. I mean yhat external
> schema is not pre-loaded.
> 
> How do I tell Java Validator about this external schema so
> that xml instance is validated successfully ?
> 
> 
> Is there any way I can tell the validator at the time of
> validation only about external schema which is not
> pre-loaded with main schema?
> 
> Help me in understanding whether it can be done ???
> Thanks
> Ajay 
> 
> --- On Thu, 11/19/09, ajay bhadauria <abhadauria@yahoo.com>
> wrote:
> 
> > From: ajay bhadauria <abhadauria@yahoo.com>
> > Subject: xs:any namespace resolution
> > To: j-users@xerces.apache.org
> > Date: Thursday, November 19, 2009, 12:48 AM
> > Hi,
> > 
> > I have schema file 1.xsd which has xs:any schema
> construct
> >  
> > <xs:complexType name="ExtensionEnvelope">
> >     
>    <xs:sequence>
> >         
>    <xs:any
> > namespace="##any" processContents="strict"/>
> >     
>    </xs:sequence>
> >     </xs:complexType>
> > 
> > And I try to validate xml instance ( test2.xml )
> against
> > this schema, it gave the following error
> >      cvc-complex-type.2.4.c: The
> > matching wildcard is strict, but no declaration can be
> found
> > for element 'ns1:Document'.
> > 
> > However, the namespace which the Validator is looking
> for
> > is in other xsd file (2.xsd). 
> > 
> > How do I tell Validator the location of 2.xsd file
> during
> > validation ? 
> > 
> > The test.xml has some elements which belong to the
> > namespace urn:swift:xsd:$xtsn.998.001.01 which is
> defined in
> > the 2.xsd file.
> > 
> > 
> >       
> >
> ---------------------------------------------------------------------
> > To unsubscribe, e-mail: j-users-unsubscribe@xerces.apache.org
> > For additional commands, e-mail: j-users-help@xerces.apache.org
> 
> 
>       
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: j-users-unsubscribe@xerces.apache.org
> For additional commands, e-mail: j-users-help@xerces.apache.org
> 
> 


      

---------------------------------------------------------------------
To unsubscribe, e-mail: j-users-unsubscribe@xerces.apache.org
For additional commands, e-mail: j-users-help@xerces.apache.org
Re: xs:any namespace resolution ajay bhadauria <abhadauria@yahoo.com> urn:uuid:%3c681174-21047-qm@web111507-mail-gq1-yahoo-com%3e 2009-11-19T01:08:36Z 
Hi,

I am using <xs:any
> namespace="##any" processContents="strict"/> and I am validating xml instance which
is having elements which belong to the different namespace and corresponding to this namespace,
schema is not pre-loaded. I mean yhat external schema is not pre-loaded.

How do I tell Java Validator about this external schema so that xml instance is validated
successfully ?


Is there any way I can tell the validator at the time of validation only about external schema
which is not pre-loaded with main schema?

Help me in understanding whether it can be done ???
Thanks
Ajay 

--- On Thu, 11/19/09, ajay bhadauria <abhadauria@yahoo.com> wrote:

> From: ajay bhadauria <abhadauria@yahoo.com>
> Subject: xs:any namespace resolution
> To: j-users@xerces.apache.org
> Date: Thursday, November 19, 2009, 12:48 AM
> Hi,
> 
> I have schema file 1.xsd which has xs:any schema construct
>  
> <xs:complexType name="ExtensionEnvelope">
>         <xs:sequence>
>             <xs:any
> namespace="##any" processContents="strict"/>
>         </xs:sequence>
>     </xs:complexType>
> 
> And I try to validate xml instance ( test2.xml ) against
> this schema, it gave the following error
>      cvc-complex-type.2.4.c: The
> matching wildcard is strict, but no declaration can be found
> for element 'ns1:Document'.
> 
> However, the namespace which the Validator is looking for
> is in other xsd file (2.xsd). 
> 
> How do I tell Validator the location of 2.xsd file during
> validation ? 
> 
> The test.xml has some elements which belong to the
> namespace urn:swift:xsd:$xtsn.998.001.01 which is defined in
> the 2.xsd file.
> 
> 
>       
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: j-users-unsubscribe@xerces.apache.org
> For additional commands, e-mail: j-users-help@xerces.apache.org


      

---------------------------------------------------------------------
To unsubscribe, e-mail: j-users-unsubscribe@xerces.apache.org
For additional commands, e-mail: j-users-help@xerces.apache.org
Re: How to add new node to the document and attach it with its correct PSVI ? Michael Glavassevich <mrglavas@ca.ibm.com> urn:uuid:%3cOF8060BBB7-9DEB3378-ON85257672-00746C82-85257672-0074F3BD@ca-ibm-com%3e 2009-11-18T21:17:08Z 
Content-type: text/plain; charset=ISO-8859-1
Content-transfer-encoding: quoted-printable


You should be looking at the *source code* of the samples. They're
primarily meant to educate developers on how to use the APIs, not so mu=
ch
for direct consumption by your application.

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

Omar Hamed <omhmmmk@gmail.com> wrote on 11/18/2009 03:05:38 AM:

> I have been searching the mailing list for the past two days with no
clue.
> Regarding the samples, I don't understand it, like "java
> jaxp.SourceValidator (options) ..." how could I use this in my code ?=
?
>
> Thanks in advance,,
> Omar Hamed

> On Sun, Nov 15, 2009 at 9:50 PM, Michael Glavassevich
<mrglavas@ca.ibm.com
> > wrote:
> Omar Hamed <omhmmmk@gmail.com> wrote on 11/15/2009 02:26:24 PM:
>
>
> > The JAXP samples will generate the data access classes and the bean=
s
> > that represent the grammar specified in the XSD, am I right ?
>
>
> No. You must be thinking of *JAXB*. That's something entirely
> different and not supported by Xerces.
>
> Please take a look at the samples and FAQs in the documentation. If
> you're still not sure after reviewing that I suggest that you search
> the mailing list archives [1] where you'll find many past
> discussions on DOM and PSVI.
>
>
> > What I want to do is to get the PSVI dynamically while my
> > application is running.
> >
> > I hope it's clear now.

> Thanks.
>
> [1] http://xerces-j-users.markmail.org/
>
>
> Michael Glavassevich
> XML Parser Development
> IBM Toronto Lab
> E-mail: mrglavas@ca.ibm.com
> E-mail: mrglavas@apache.org=
xs:any namespace resolution ajay bhadauria <abhadauria@yahoo.com> urn:uuid:%3c139662-23515-qm@web111502-mail-gq1-yahoo-com%3e 2009-11-18T19:18:10Z 
Hi,

I have schema file 1.xsd which has xs:any schema construct
 
<xs:complexType name="ExtensionEnvelope">
        <xs:sequence>
            <xs:any namespace="##any" processContents="strict"/>
        </xs:sequence>
    </xs:complexType>

And I try to validate xml instance ( test2.xml ) against this schema, it gave the following
error
     cvc-complex-type.2.4.c: The matching wildcard is strict, but no declaration can be found
for element 'ns1:Document'.

However, the namespace which the Validator is looking for is in other xsd file (2.xsd). 

How do I tell Validator the location of 2.xsd file during validation ? 

The test.xml has some elements which belong to the namespace urn:swift:xsd:$xtsn.998.001.01
which is defined in the 2.xsd file.
Re: How to add new node to the document and attach it with its correct PSVI ? Omar Hamed <omhmmmk@gmail.com> urn:uuid:%3c7a8f50790911180005k21426338k2332bcf31cdfbd6b@mail-gmail-com%3e 2009-11-18T08:05:38Z 
I have been searching the mailing list for the past two days with no clue.
Regarding the samples, I don't understand it, like "java
jaxp.SourceValidator (options) ..." how could I use this in my code ??

Thanks in advance,
Omar Hamed

On Sun, Nov 15, 2009 at 9:50 PM, Michael Glavassevich
<mrglavas@ca.ibm.com>wrote:

> Omar Hamed <omhmmmk@gmail.com> wrote on 11/15/2009 02:26:24 PM:
>
>
> > The JAXP samples will generate the data access classes and the beans
> > that represent the grammar specified in the XSD, am I right ?
>
>
> No. You must be thinking of *JAXB*. That's something entirely different and
> not supported by Xerces.
>
> Please take a look at the samples and FAQs in the documentation. If you're
> still not sure after reviewing that I suggest that you search the mailing
> list archives [1] where you'll find many past discussions on DOM and PSVI.
>
>
> > What I want to do is to get the PSVI dynamically while my
> > application is running.
> >
> > I hope it's clear now.
>
> Thanks.
>
> [1] http://xerces-j-users.markmail.org/
>
>
> Michael Glavassevich
> XML Parser Development
> IBM Toronto Lab
> E-mail: mrglavas@ca.ibm.com
> E-mail: mrglavas@apache.org
>
>


-- 
0µªΓ
Can't get type of the newly added elements Omar Hamed <omhmmmk@gmail.com> urn:uuid:%3c7a8f50790911172357g298c2bd2vf94191c1bc5b0ac8@mail-gmail-com%3e 2009-11-18T07:57:18Z 
Hi,
     I have a problem that I can't re-parse the xml document after adding
nodes to it so that I can retrieve the new elements type.

here is the code:
public static void main(String[] args){

     DocumentBuilderFactory parserFactory =
DocumentBuilderFactory.newInstance();
     SchemaFactory factory =
SchemaFactory.newInstance(XMLConstants.W3C_XML_SCHEMA_NS_URI);

            Source schemaFile = new StreamSource(new File("test.xsd"));
            Schema schema = factory.newSchema(schemaFile);

            parserFactory.setSchema(schema);

            DocumentBuilder parser = parserFactory.newDocumentBuilder();
            Document document = parser.parse(new File("test.xml"));


            Node promoTag =
document.getElementsByTagName("promotion_period").item(0); // get element

            Element endElm = document.createElement("end_date");            //
add new element
            endElm.setTextContent("2007-05-10");
            promoTag.appendChild(endElm);

            ((Element)
document.getElementsByTagName("end_date").item(0)).getSchemaTypeInfo().getTypeName();
// [1] returns null
}

At point #1: I think I need something like re-parse or re-validate the
document so that I can attach the added node with its type.

I have the same issue if I'm working with the XERCES ElementPSVI.

I don't know what is missing or how can I do that.

Thanks in advance
Omar Mostafa