Hi Michael,
We committed a fix for this issue to SVN (revision, 1356945).
@ Jorge: you may verify the fix as appropriate.
On Wed, Jun 27, 2012 at 3:37 AM, Michael Glavassevich
wrote:
> I agree. I would expect a SAXException thrown from an ErrorHandler (in any
> context) to propagate up the st
Hi Michael,
Thanks for the clarification.
We'll try to solve this bug.
On Wed, Jun 27, 2012 at 3:37 AM, Michael Glavassevich
wrote:
> I agree. I would expect a SAXException thrown from an ErrorHandler (in any
> context) to propagate up the stack. If this is getting swallowed somewhere
> in X
I agree. I would expect a SAXException thrown from an ErrorHandler (in any
context) to propagate up the stack. If this is getting swallowed somewhere
in Xerces then it's a bug.
Michael Glavassevich
XML Technologies and WAS Development
IBM Toronto Lab
E-mail: mrgla...@ca.ibm.com
E-mail: mrgla...@
Hey Mukul,
Yup, you pointed me in the right direction -- thanks...but I still think
there's a bug.
If you look at the docs to ErrorHandler:
http://docs.oracle.com/javase/6/docs/api/org/xml/sax/ErrorHandler.html
It says that: " it is up to the application to decide whether to throw an
excepti
Hi Jorge,
I think, this error is not specific to XSD assertions. Setting a
error handler on the JAXP validator object would solve this problem.
Following are the proposed changes to solve this issue,
Validator v = s.newValidator();
v.setErrorHandler(new ErrHandler());
v.validate(new StreamSour
Hey Guys,
Can you give me a hand. I'm getting a weird error that I cannot replicate with
jaxp.SourceValidator so I know I must be doing something wrong, but I can't
tell what.
My code looks like this:
package com.rackspace.xerces;
import javax.xml.validation.*;
import javax.xml.transform.str
