Hi Neil !
> [..]
> All right, I'm convinced. Change made in CVS.
Thanx.
*hmm* had a look at the fix.
That was done a little bit different than what I suggested, but that
doesn´t matter much.
parser.setEntityResolver( (fEntityResolver != null)?
(fEntityResolver):(new Resolver()) );
What I
Hi Scott and all,
Xerces1 should now have META-INF/services properly working as well in both
its ant and make-based builds. When Xerces 1.4.2 comes out--probably on
Friday--this will be fixed.
BTW: Anyone have anything pressing they'd like to see included in Xerces
1.4.2? This could be the la
Or try changing xsd:simpleContent to xsd:ComplexContent
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, July 17, 2001 6:31 AM
To: [EMAIL PROTECTED]
Subject: Re: Please, can someone help me? It´s Urgent!
Hi Nelson,
The following lines cause trouble.
At 09:11 AM 7/17/2001 -0500, you wrote:
>I have Xerces 1.4.1.
>
>When I set the http://xml.org/sax/features/external-general-entities feature
>to false, the parser return SAXNotSupportedException.
>
>Does anyone know anything else I need to set?
>Or, is there future plan to support this?
I believ
I have Xerces 1.4.1.
When I set the http://xml.org/sax/features/external-general-entities feature
to false, the parser return SAXNotSupportedException.
Does anyone know anything else I need to set?
Or, is there future plan to support this?
--
Hi Nelson,
The following lines cause trouble. According to schema spec (and the error
message), the only possible children of "extension" (in simpleContent) are
annotation, attribute, attributeGroup, and anyAttribute. So maxLength is
not allowed. Try change extension to restriction, which allows
On Mon, 16 Jul 2001 [EMAIL PROTECTED] wrote:
> Archives for mailing lists are not curretly avaliable, so I'm sorry if this
> question has already been asked by someone else.
>
> Is the xsd schema namespace "http://www.w3.org/2000/10/XMLSchema"; supported
> or I need to switch to "http://www.w3.o
