On Feb 17, 2010, at 12:38 AM, Tatu Saloranta wrote:
> On Tue, Feb 16, 2010 at 9:54 AM, Phil Griffin
> <phil.griffin_at_oracle.com> wrote:
>> I recently updated our Jersey jars to 1.1.4.1 and began getting a
>> JAXP
>> parser registry exception for a non-supported feature (in the
>> factory I'm
>> required to use). Is there a way to disable the
>> com.sun.jersey.core.provider.jaxb.AbstractJAXBProvider or Jersey from
>> expecting this feature?
>>
>> WebLogicSAXParser cannot be created.SAX feature
>> @ 'http://xml.org/sax/features/external-general-entities' not
>> supported
>
> Would it not be possible to configure your system to use a better
> parser? Like Xerces or Woodstox/SAX?
>
In my experience it is usually a version of Xerces that result in such
warnings. This does not happen with JAXP as distributed with the JDK
(nor at least with versions of GF that might ship with a different
version of a JAXP impl to that in the JDK).
> If not, it should be possible to allow overriding SAX factory to use
> for Jersey.
>
That can do done via JAXP mechanisms (as you of course know!) but are
referring to the developer setting a property via Jersey? e.g. here is
the name of the SAXParserFactory class to use?
Paul.