Hi,

I just experienced exactly the same problem as you described. My CLASSPATH
environment contained references to some old SOAP and xerces jar-files. Try
unsetting the CLASSPATH environment variable from the console window where
you run run.bat (or simple change the line "set
CLASSPATH=%CLASSPATH%;run.jar" to "set CLASSPATH=;run.jar" in run.bat).

I think this will solve your problem.

Regards,
Per

> Hi all,
>
> I was on holliday for 3 weeks.
> Now i took the last source code jboss 21 pre from VCS and
> traying to run project.
>
> I do getting such errors:
> Any sugestions ? should i revome
> <?xml version="1.0" encoding="Cp1252"? > "Cp1252" from my xml files?
>
>
> [Container factory] The encoding "Cp1252" is not supported.:0:0
> [Container factory] org.jboss.ejb.DeploymentException: The
> encoding "Cp1252" is
> not supported.
> [Container factory]     at
> org.jboss.metadata.XmlFileLoader.getDocument(XmlFileL
> oader.java:167)
> [Container factory]     at
> org.jboss.metadata.XmlFileLoader.getDocument(XmlFileL
> oader.java:132)
> [Container factory]     at
> org.jboss.metadata.XmlFileLoader.load(XmlFileLoader.j
> ava:89)
> [Container factory]     at
> org.jboss.ejb.ContainerFactory.deploy(ContainerFactor
> y.java:328)
> [Container factory]     at
> org.jboss.ejb.ContainerFactory.deploy(ContainerFactor
> y.java:259)
> [Container factory]     at
> java.lang.reflect.Method.invoke(Native Method)
> [Container factory]     at
> com.sun.management.jmx.MBeanServerImpl.invoke(MBeanSe
> rverImpl.java:1628)
> [Container factory]     at
> com.sun.management.jmx.MBeanServerImpl.invoke(MBeanSe
> rverImpl.java:1523)
> [Container factory]     at
> org.jboss.deployment.J2eeDeployer.startApplication(J2
> eeDeployer.java:424)
> [Container factory]     at
> org.jboss.deployment.J2eeDeployer.deploy(J2eeDeployer
> .java:176)
> [Container factory]     at
> java.lang.reflect.Method.invoke(Native Method)
> [Container factory]     at
> com.sun.management.jmx.MBeanServerImpl.invoke(MBeanSe
> rverImpl.java:1628)
> [Container factory]     at
> com.sun.management.jmx.MBeanServerImpl.invoke(MBeanSe
> rverImpl.java:1523)
> [Container factory]     at
> org.jboss.ejb.AutoDeployer.deploy(AutoDeployer.java:3
> 58)
> [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(ServiceMBean
> Support.java:93)
> [Container factory]     at
> java.lang.reflect.Method.invoke(Native Method)
> [Container factory]     at
> com.sun.management.jmx.MBeanServerImpl.invoke(MBeanSe
> rverImpl.java:1628)
> [Container factory]     at
> com.sun.management.jmx.MBeanServerImpl.invoke(MBeanSe
> rverImpl.java:1523)
> [Container factory]     at
> org.jboss.util.ServiceControl.start(ServiceControl.ja
> va:97)
> [Container factory]     at
> java.lang.reflect.Method.invoke(Native Method)
> [Container factory]     at
> com.sun.management.jmx.MBeanServerImpl.invoke(MBeanSe
> rverImpl.java:1628)
> [Container factory]     at
> com.sun.management.jmx.MBeanServerImpl.invoke(MBeanSe
> rverImpl.java:1523)
> [Container factory]     at org.jboss.Main.<init>(Main.java:160)
> [Container factory]     at org.jboss.Main$1.run(Main.java:89)
> [Container factory]     at
> java.security.AccessController.doPrivileged(Native Me
> thod)
> [Container factory]     at org.jboss.Main.main(Main.java:85)
> [J2EE Deployer Default] Starting contact.jar failed!
>
>
>
> On Thu, 4 Jan 2001 21:05:43 +0100, Benjamin Broll wrote:
>
> >Hi all,
> >
> >besides the problem I outlined in one of my last mails, I'm
> experiencing
> >another (quite annoying) problem during the change from 2.0-final to
> >pre-2.1. Now, when I want to deploy my .ear file which
> perfectly ran on 2.0,
> >jBoss (or the XML-Parser) complains that my installation is
> not capable of
> >the encoding "Cp1252" as it is used in jboss.xml. Even when
> I change the
> >encoding, jBoss still complains during deployment.
> >
> >But since I already worked with this encoding successfully I
> cannot believe
> >the parser. How can I solve this issue? Am I somehow able to add the
> >encoding to the encodings supported in my system?
> >
> >Thanks for any help,
> >
> >.bbr



--
--------------------------------------------------------------
To subscribe:        [EMAIL PROTECTED]
To unsubscribe:      [EMAIL PROTECTED]
List Help?:          [EMAIL PROTECTED]

Reply via email to