[prev in list] [next in list] [prev in thread] [next in thread] 

List:       xmlbeans-user
Subject:    RE: Fatal errors with the Piccolo parser and invalid xml header
From:       "Wing Yew Poon" <wpoon () bea ! com>
Date:       2006-08-04 17:57:53
Message-ID: F91503BC8AA6384BA2FFED03EF8E392C01550729 () repbex01 ! amer ! bea ! com
[Download RAW message or body]

Perhaps you are not logged in?
Anyone is free to find issues. You must register and login if you want
to create, comment, vote, or watch issues. 
- Wing Yew

-----Original Message-----
From: Ken Robinson [mailto:ken.robinson@apollogrp.edu] 
Sent: Friday, August 04, 2006 9:37 AM
To: user@xmlbeans.apache.org
Subject: RE: Fatal errors with the Piccolo parser and invalid xml header

I tried to file a bug with JIRA, but I couldn't find anywhere on the
form to submit a new issue.

-----Original Message-----
From: Cezar Andrei [mailto:cezar@bea.com] 
Sent: Thursday, August 03, 2006 7:29 PM
To: user@xmlbeans.apache.org
Subject: RE: Fatal errors with the Piccolo parser and invalid xml header


Ken,

There isn't a public API to reset the context piccolo instance. Please
do file a bug with a repro in the JIRA so we can take a look at it.

In the meantime, you can use XmlOptions setLoadUseXMLReader (XMLReader
xmlReader) to use your own instance of Piccolo or any other SAX parser.

Cezar

> -----Original Message-----
> From: Ken Robinson [mailto:ken.robinson@apollogrp.edu]
> Sent: Thursday, August 03, 2006 5:31 PM
> To: user@xmlbeans.apache.org
> Subject: Fatal errors with the Piccolo parser and invalid xml header
> 
> We've encountered a particularly nasty problem with the default
piccolo
> parser and invalid xml headers.  If the xml being parsed (via
> XmlObject.Factory.parse()) has a bad header (like <?xml
> encoding="UTF-8">), a reasonable exception is thrown.  This particular
> exception also appears to leave the piccolo instance in some sort of
> invalid state.  Unfortunately, the instance also remains in the
> tl_saxLoaders ThreadLocal inside SystemCache, causing all subsequent
> parses in the same thread to fail with NullPointerExceptions inside
the
> piccolo code.  We've been able to replicate this issue with every
> version of XmlBeans from 2.0.0-beta1 through 2.2.0.  Is there any
> likelyhood of getting this fixed, or barring that, is there any public
> API for forcing the bad parser out of the ThreadLocal?
> 
> Thanks,
> Ken
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: user-unsubscribe@xmlbeans.apache.org
> For additional commands, e-mail: user-help@xmlbeans.apache.org

_______________________________________________________________________
Notice:  This email message, together with any attachments, may contain
information  of  BEA Systems,  Inc.,  its subsidiaries  and  affiliated
entities,  that may be confidential,  proprietary,  copyrighted  and/or
legally privileged, and is intended solely for the use of the individual
or entity named in this message. If you are not the intended recipient,
and have received this message in error, please immediately return this
by email and then delete it.

---------------------------------------------------------------------
To unsubscribe, e-mail: user-unsubscribe@xmlbeans.apache.org
For additional commands, e-mail: user-help@xmlbeans.apache.org


---------------------------------------------------------------------
To unsubscribe, e-mail: user-unsubscribe@xmlbeans.apache.org
For additional commands, e-mail: user-help@xmlbeans.apache.org


---------------------------------------------------------------------
To unsubscribe, e-mail: user-unsubscribe@xmlbeans.apache.org
For additional commands, e-mail: user-help@xmlbeans.apache.org


[prev in list] [next in list] [prev in thread] [next in thread]