> I changed "all" to "sequence" and it still only validates against the
first
> item in .
If you turn on schema-full-checking feature (-f on the samples), you'll get
more errors on your schema. You have a choice of two groups, which contain
elements with the same name but different type. This viol
Title: Creating New Parser Configurations in Xerces 2.0
Hi,
I've been looking at creating a new Parser Configuration which removes everything to do with DTD processing by extending the StandardParserConfiguration class as shown in the example for a NonValidatingParserConfiguration.
I not
I changed "all" to "sequence" and it still only validates against the first
item in .
What could be the problem?
Thanks,
Sean
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
Sent: Friday, February 01, 2002 12:21
"Nestel, Frank ISC 6" wrote:
> But there seems to be a minor problem occuring when I create new
> Parsers. Below is a stack trace. The thing I don't understand is,
> that the
Under what circumstances do you encounter this problem? (OS,
JVM, etc, etc.)
--
Andy Clark * [EMAIL PROTECTED]
-
Hi All,
I used the ASBuilder example in the xerces-2_0_0 to validate a soap message
which contains the encodingStyle attribute in the Envelope
element. However, this example gave me an error like
cvc-complex-type.3.2.2: Attribute 'SOAP-ENV:encodingStyle' is not allowed
to appear in element 'SO
This is a bug in the new release. It's been fixed in CVS.
>From the home page of Xerces-2 project
"http://xml.apache.org/xerces2-j/index.html";, there is a link to the latest
jar files. Downloading these files should solve your problem.
Cheers,
Sandy Gao
Software Developer, IBM Canada
(1-905) 413
Please take me off the mailing list!
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Title: Xerces backward Compatibility
Frank,
I went
through the same scenario as yourself recently.
Officially, BEA have a disclaimer saying that you may have problems if
you use another parser such as version 1.4.4. Basically, they
won't provide support if you use a different parser and
Hi,
getting Xerces from Xerces-2.0.0-bin instead of Xerces-2.0.0-tools
I finally end up with a fairly smooth running Application.
Overall Xerces-2.0.0 is looking great!
But there seems to be a minor problem occuring when I create new
Parsers. Below is a stack trace. The thing I don't understand
Hi everybody
thanks for help.
Actually I tried that with
"http://www.w3.org/2001/XMLSchema-instance"once before, but I forgot to save the filesAnyway, I fixed that now, but I get a new ErrorGeneral Schema Error: Grammar with uri 2: http://www.zhwin.ch/schnemac/Req , can not foundDoes x
Guillaume Potard wrote:
> i just managed to compile them.. it wasnt looking at the class path
> properly, I think it is really cumbersome that you have to specify the path
> of each jar file after -classpath option ( I am using command line) . Do you
> know a way around this ?
If you download the
I had some mysterious problems with Xerces for a while: it all
came down to versions of Java, really. Which one are you using? I
suppose the next question is, are you sure? As I recall,
ClassLoader.getSystemResource() will tell you
which jar a class actually came from (if you really think
Thank you for your reply,
i just managed to compile them.. it wasnt looking at the class path
properly, I think it is really cumbersome that you have to specify the path
of each jar file after -classpath option ( I am using command line) . Do you
know a way around this ?
Anyway now i can start d
14 matches
Mail list logo
