Xerces Release Binaries - To Compress or Not To Compress...

[Rick Bullotta <Ri...@lighthammer.com>]

I noticed between the 1.2.2 and 1.2.3 release, there was a difference in the
size of the resultant .JAR file - 1.2.2 being compressed, and 1.2.3 not
(Xalan 1.2.2, for that matter, was compressed).  Any pros/cons for either
approach and what is the "recommended" mode?

Regards,

Rick Bullotta
CTO
Lighthammer

-----Original Message-----
From: Eric Ye [mailto:ericye@locus.apache.org]
Sent: Thursday, December 07, 2000 13:22
To: xerces-j-dev@xml.apache.org
Subject: Re: Namespace problems in Xerces-J 1.2.3


You are wrong this time, Neil :-)

Actually, there seems to be a bug in the none deferred DOM implementation,
try this:

java dom.DOMCount -D http://www.w3.org/2000/04/xml.xsd

I am looking into this, also I will consult with Arnaud on this.
_____


Eric Ye * IBM, JTC - Silicon Valley * ericye@locus.apache.org

----- Original Message -----
From: <ne...@ca.ibm.com>
To: <xe...@xml.apache.org>
Sent: Thursday, December 07, 2000 7:59 AM
Subject: Re: Namespace problems in Xerces-J 1.2.3


>
>
> Hi Ramesh,
>
> I was able to get the same error with Xerces 1.2.3, and your documents
seem
> perfectly valid to me.  I'll try and see if I can figure this out (though
> it is probably related to the bug which Eric fixed earlier this week).
>
> Cheers,
> Neil
>
> Neil Graham
> XML Parser Development
> IBM Toronto Lab
> Phone:  416-448-3519, T/L 778-3519
> E-mail:  neilg@ca.ibm.com
>
>
>
> Ramesh Gupta <ra...@eNode.com> on 12/07/2000 08:57:08 AM
>
> Please respond to xerces-j-dev@xml.apache.org
>
> To:   xerces-j-dev@xml.apache.org
> cc:
> Subject:  Namespace problems in Xerces-J 1.2.3
>
>
>
>
> I just tried to move from Xerces 1.2.1 to 1.2.3 and found that my
documents
> that validated fine before no longer do so.
>
> Parsing a bare instance document [1] with a simple schema [2] produces the
> following error in Xerces 1.2.3:
> org.w3c.dom.DOMException: DOM003 Namespace error
>
> If I remove the <import> element from the schema, the error goes away!
>
> [1] Instance document
> =====================
> <?xml version="1.0" encoding="UTF-8"?>
> <foo    xmlns="FooNamespace"
>         xmlns:xsi="http://www.w3.org/1999/XMLSchema-instance"
>         xsi:schemaLocation="FooNamespace http://localhost/fooSchema.xsd">
> </foo>
>
> [2] Schema
> ==========
> <?xml version="1.0" encoding="UTF-8"?>
> <schema    xmlns="http://www.w3.org/1999/XMLSchema"
>         targetNamespace="FooNamespace"
>         xmlns:xsi="http://www.w3.org/1999/XMLSchema-instance"
>         xsi:schemaLocation="http://www.w3.org/1999/XMLSchema
> http://www.w3.org/1999/XMLSchema.xsd">
>
>     <import    namespace="http://www.w3.org/XML/1998/namespace"
>             schemaLocation="http://www.w3.org/2000/04/xml.xsd"/>
>
>     <element    name="foo">
>         <complexContent/>
>     </element>
>
> </schema>
>
>
> on 12/3/00 2:00 PM, Eric Ye at ericye@locus.apache.org wrote:
>
> > Yes, the schema that uses <xsd:schema...> tags will not work with
> > Xerces1.2.2, and believe it or not, it was due to a more compiant DOM
> Level
> > 2 implementation, and we didn't have enough schema test cases to unveil
> this
> > problem.
> >
> > I already fixed this problem, you could either check out the latest
> source
> > from CVS or wait for next release.
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: xerces-j-dev-unsubscribe@xml.apache.org
> For additional commands, e-mail: xerces-j-dev-help@xml.apache.org
>
>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: xerces-j-dev-unsubscribe@xml.apache.org
> For additional commands, e-mail: xerces-j-dev-help@xml.apache.org
>
>


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