[opencms-dev] Why are OpenCMS using encoding?

[Alexander Kandzior]

The stack trace clearly shows you are not using OpenCms 6 alpha 1.
 
com.opencms.core.OpenCmsHttpServlet...
 
must be org.opencms... for OpenCms 6.0a1.

Best Regards,
Alex.

Alexander Kandzior
Alkacon Software - The OpenCms Experts
http://www.alkacon.com <http://www.alkacon.com/> 



 



  _____  

From: opencms-dev-bounces at opencms.org
[mailto:opencms-dev-bounces at opencms.org] On Behalf Of Jonas Karlsson, Webb
och PC-support
Sent: Saturday, October 02, 2004 4:36 PM
To: 'Tristan Tarrant'; opencms-dev at opencms.org
Subject: RE: [opencms-dev] Why are OpenCMS using encoding?



I’m sorry, but it isn’t true that version 6.0 solves the problem with the
encoding. I used version 6.0, and everything went well according to the
installation wizard. But when I wanted to start using OmpenCMS by surfing to
http://www.webbpcsupport.com:8080//opencms/opencms/system/login/
<http://www.webbpcsupport.com:8080/opencms/opencms/system/login/>  I got the
following exception: 

 

HTTP Status 500 - 


  _____  


type Exception report

message 

description The server encountered an internal error () that prevented it
from fulfilling this request.

exception 

javax.servlet.ServletException: OpenCms initialization error!

 

Trouble creating the com.opencms.core.CmsObject. Please check the root cause
for more information.

 

 

 
com.opencms.core.OpenCmsHttpServlet.init(OpenCmsHttpServlet.java:248)

 
org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:164
)

 
org.apache.coyote.tomcat5.CoyoteAdapter.service(CoyoteAdapter.java:206)

 
org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:833)

 
org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.processConne
ction(Http11Protocol.java:732)

 
org.apache.tomcat.util.net.TcpWorkerThread.runIt(PoolTcpEndpoint.java:619)

 
org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.jav
a:688)

        java.lang.Thread.run(Thread.java:534)

root cause 

java.lang.Exception: OpenCms startup failure: System file.encoding
'ANSI_X3.4-1968' not equal to OpenCms encoding 'UTF-8'

        com.opencms.core.OpenCms.<init>(OpenCms.java:211)

 
com.opencms.core.OpenCmsHttpServlet.init(OpenCmsHttpServlet.java:242)

 
org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:164
)

 
org.apache.coyote.tomcat5.CoyoteAdapter.service(CoyoteAdapter.java:206)

 
org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:833)

 
org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.processConne
ction(Http11Protocol.java:732)

 
org.apache.tomcat.util.net.TcpWorkerThread.runIt(PoolTcpEndpoint.java:619)

 
org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.jav
a:688)

        java.lang.Thread.run(Thread.java:534)

note The full stack trace of the root cause is available in the Tomcat logs.


  _____  


Apache Tomcat/5.0.19

 Apparently version 6.0 doesn’t solve the encoding problem. 

 

Regards

 

Jonas Karlsson, Linköping

 

 

On Fri, 2004-10-01 at 14:29 +0200, Jonas Karlsson, Webb och PC-support
wrote:



The question may sound stupid, but all the talk about internationalization
and everything doesn’t work out that well out in the field. When you are not
in control over a system, but only controls a web application inside Tomcat,
and can’t control which Java-version that runs or how to start it, the
encoding problem is indeed frustrating. Why can’t OpenCMS think of a
solution but to start Tomcat with “right” encoding? Due to this rather silly
thing, I can’t get OpenCMS running and since I work for a company that
planed to recommend customers to use OpenCMS, in fact we thought about
financing a part of our costs by consulting on OpenCMS, and noting of this
can be realised. It’s a pity! Even though I like OpenCMS, I like the idea
with Open Source, I simple have to look somewhere else.  

That is why in OpenCMS 6.0 the developers have solved the problem bu not
requiring changes to the environment.
We are using it now for a large customer. It works very well.

Tristan 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://webmail.opencms.org/pipermail/opencms-dev/attachments/20041003/25e790a8/attachment.htm>