Re: [JBoss-user] SAXParse Excpetion
Hi Scott, First of all the reason I needed the xerces parser was to be able to use some DOM2 features like importNode as well as some features of XALAN 2.0.1 To specify the xerces parser rather than the crimson I simply changed the run.bat to specify the new JAXP information: set CLASSPATH=%CLASSPATH%;../lib/ext/xerces.jar set JAXP=-Djavax.xml.parsers.DocumentBuilderFactory=org.apache.xerces.jaxp.DocumentBuilderFactoryImpl set JAXP=%JAXP% -Djavax.xml.parsers.SAXParserFactory=org.apache.xerces.jaxp.SAXParserFactoryImpl I then put the xerces.jar, and xalan.jar into the lib/ext directory. Andrew Edgar Scott M Stark wrote: Then how are you specifying the JAXP properties to use xerces rather than crimson? - Original Message - From: "Andrew Edgar" [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Tuesday, April 17, 2001 11:44 AM Subject: Re: [JBoss-user] SAXParse Excpetion 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 ___ JBoss-user mailing list [EMAIL PROTECTED] http://lists.sourceforge.net/lists/listinfo/jboss-user S/MIME Cryptographic Signature
[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. [Container factory] at org.apache.xerces.framework.XMLParser.reportError(XMLParser.java:1060) [Container factory] at org.apache.xerces.readers.DefaultEntityHandler.startReadingFromDocument(DefaultEntityHandler.java:541) [Container factory] at org.apache.xerces.framework.XMLParser.parseSomeSetup(XMLParser.java:309) [Container factory] at org.apache.xerces.framework.XMLParser.parse(XMLParser.java:951) [Container factory] at org.apache.xerces.jaxp.DocumentBuilderImpl.parse(DocumentBuilderImpl.java:123) [Container factory] at javax.xml.parsers.DocumentBuilder.parse(DocumentBuilder.java:137) [Container factory] at org.jboss.metadata.XmlFileLoader.getDocument(XmlFileLoader.java:148) [Container factory] at org.jboss.metadata.XmlFileLoader.getDocument(XmlFileLoader.java:132) [Container factory] at org.jboss.metadata.XmlFileLoader.load(XmlFileLoader.java:106) [Container factory] at org.jboss.ejb.ContainerFactory.deploy(ContainerFactory.java:388) [Container factory] at org.jboss.ejb.ContainerFactory.deploy(ContainerFactory.java:334) [Container factory] at org.jboss.ejb.ContainerFactory.deploy(ContainerFactory.java:275) [Container factory] at java.lang.reflect.Method.invoke(Native Method) [Container factory] at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1628) [Container factory] at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1523) [Container factory] at org.jboss.deployment.J2eeDeployer.startApplication(J2eeDeployer.java:435) [Container factory] at org.jboss.deployment.J2eeDeployer.deploy(J2eeDeployer.java:178) [Container factory] at java.lang.reflect.Method.invoke(Native Method) [Container factory] at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1628) [Container factory] at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1523) [Container factory] at org.jboss.ejb.AutoDeployer.deploy(AutoDeployer.java:358) [Container factory] at org.jboss.ejb.AutoDeployer.run(AutoDeployer.java:221) [Container factory] at org.jboss.ejb.AutoDeployer.startService(AutoDeployer.java:332) [Container factory] at org.jboss.util.ServiceMBeanSupport.start(ServiceMBeanSupport.java:93) [Container factory] at java.lang.reflect.Method.invoke(Native Method) [Container factory] at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1628) [Container factory] at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1523) [Container factory] at org.jboss.util.ServiceControl.start(ServiceControl.java:97) [Container factory] at java.lang.reflect.Method.invoke(Native Method) [Container factory] at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1628) [Container factory] at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1523) [Container factory] at org.jboss.Main.init(Main.java:203) [Container factory] at org.jboss.Main$1.run(Main.java:107) [Container factory] at java.security.AccessController.doPrivileged(Native Method) [Container factory] at org.jboss.Main.main(Main.java:103) [Container factory] org.jboss.ejb.DeploymentException: The encoding "Cp1252" is not supported., Cause:org.xml.sax.SAXParseException: The encoding "Cp1252" is no t supported. [Container factory] at org.jboss.metadata.XmlFileLoader.getDocument(XmlFileLoader.java:153) [Container factory] at org.jboss.metadata.XmlFileLoader.getDocument(XmlFileLoader.java:132) [Container factory] at org.jboss.metadata.XmlFileLoader.load(XmlFileLoader.java:106) [Container factory] at org.jboss.ejb.ContainerFactory.deploy(ContainerFactory.java:388) [Container factory] at org.jboss.ejb.ContainerFactory.deploy(ContainerFactory.java:334) [Container factory] at org.jboss.ejb.ContainerFactory.deploy(ContainerFactory.java:275) [Container factory] at java.lang.reflect.Method.invoke(Native Method) [Container factory] at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1628) [Container factory] at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1523) [Container factory] at org.jboss.deployment.J2eeDeployer.startApplication(J2eeDeployer.java:435) [Container factory] at
Re: [JBoss-user] SAXParse Excpetion
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
