I tried that. It came back with exactly the same error. Trying really invalid
values like "BADENCODING" returned saying that "BADENCODING" not supported but when
specifying either Cp1252 or UTF-8 I got the same error saying Cp1252 was not
supported.
Thanks,
Andrew
Scott M Stark wrote:
> Try using UTF-8 as the encoding rather than Cp1252
>
> ----- Original Message -----
> From: "Andrew Edgar" <[EMAIL PROTECTED]>
> To: <[EMAIL PROTECTED]>
> Sent: Tuesday, April 17, 2001 9:56 AM
> Subject: [JBoss-user] SAXParse Excpetion
>
> > I'm using jboss 2.2 final with Tomcat. I want to use the Xerces 1.2.1
> > parser and not the crimson parser.
> >
> > When I do this when deploying I get the attached error: Is this a
> > configuration issue as to how to setup the parser? The same XML's
> > (jboss.xml and ejb-jar.xml) worked when using crimson.
> >
> > Thanks,
> >
> > Andrew Edgar
> > Senior Software Engineer
> > SLMsoft.com Inc.
> >
> > [Container factory]
> > Deploying:file:/C:/jboss/jboss-tomcat-2.2/jboss-2.2/tmp/deploy/Default/FTS.jar
> >
> > [Container factory] The encoding "Cp1252" is not supported.:0:0
> > [Container factory] org.xml.sax.SAXParseException: The encoding "Cp1252"
> > is not
> > supported.
>
> _______________________________________________
> JBoss-user mailing list
> [EMAIL PROTECTED]
> http://lists.sourceforge.net/lists/listinfo/jboss-user
S/MIME Cryptographic Signature