On Mon, Mar 1, 2010 at 12:14 PM, Mike Baranczak <mbaranczak_at_gmail.com> wrote:
>
> Paul, you are correct, I mis-spoke. This is not a bug in Jersey, it's a
> missing feature in some versions of Xerces.
>
> The best solution: don't add any Xerces jars to your application's
> classpath, then the JRE's built-in parser will be used instead. I can't do
> that, since my project has an indirect dependency on an old version of
> Xerces, and Xerces registers itself as the default parser.
Ah. This explains it. But it is also bit surprising -- more often it
has been that JDK bundled version is bit old (that is just another way
of saying that your deployment really does have rather older version
:) ).
Fortunately you can define override in this case.
I understand that you don't have much control over this, which is unfortunate.
Another way to go about this might be for Jersey to define minimum
level of Xerces that it requires -- preferably something that stable
JVMs bundle with. That could help developers define why exactly they
must be able to use never versions of Xerces (etc); because it is a
requirement.
-+ Tatu +-