yeah, tried that: that's what I meant when I said I'd set system properti=
es,
but forgot to say which system properties I meant! It didn't work for me=
-
NPE's got generated at some point but will need to check where later, I'v=
e no
access to that machine at present.
Cheers,
On Fri, March 3, 2006 08:00, Juergen Hoeller wrote:
> Resin seems to override the default XML parser and set its own there -
> probably without schema support. So I guess you need to figure how to m=
ake
> Resin use JDK 5's default XML parser (which would be Xerces and hence f=
ine)
> instead.
>
> Juergen
>
>
> -----Original Message-----
> From: spr...@li...
> [mailto:spr...@li...] On Behal=
f Of
> da...@da...
> Sent: Friday, March 03, 2006 12:37 AM
> To: spr...@li...
> Subject: [Springframework-developer] XSD and Resin
>
> has anyone deployed a Spring app using 2.0 schema into Resin? I get an
> exception as the parser can't handle schema:
>
> [23:35:15.067] org.springframework.beans.FatalBeanException: Unable to
> validate using XSD: Your JAXP provider
> [org.apache.crimson.jaxp.DocumentBuilderFactoryImpl@a7dd39] does not su=
pport
> XML Schema. Are you running on Java 1.4 or below with Apache Crimson?
> Upgrade to Apache Xerces (or Java 1.5) for full XSD support.
>
> I'm certainly running on JDK 5, I've also tried setting system properti=
es as
> java_args in the resin httpd.sh startup file to no avail.
>
> Cheers,
> --
> Darren Davison
> Public Key: 0xDD356B0D
--=20
Darren Davison
Public Key: 0xDD356B0D
|