You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@turbine.apache.org by Nathan Mcminn <NM...@theblragency.com> on 2003/09/18 16:59:40 UTC
Turbine path issue
Hey all,
Whenever I try to hit my web app, all I get back is the
following error message:
Horrible Exception: java.lang.ClassNotFoundException:
Requested Page not found: Default
Turbine looked in the following modules.packages path:
[com.nequalsone.modules, org.apache.turbine.modules]
It is running under tomcat 4.1.12, jdk 1.4.0. I have checked, and in my
app jar file in %tomcat_home%/common/lib there does exist a class called
com.nequalsone.modules.screens.Default. Default extends a class called
SecureScreen, which in turn extends VelocitySecureScreen. I have pasted
the entire exception trace below:
Horrible Exception: java.lang.ClassNotFoundException:
Requested Page not found: Default
Turbine looked in the following modules.packages path:
[com.nequalsone.modules, org.apache.turbine.modules]
at
org.apache.turbine.modules.PageLoader.getInstance(PageLoader.java:190)
at
org.apache.turbine.modules.PageLoader.exec(PageLoader.java:135)
at org.apache.turbine.Turbine.doGet(Turbine.java:792)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:740)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at
org.apache.catalina.servlets.InvokerServlet.serveRequest(InvokerServlet.
java:458)
at
org.apache.catalina.servlets.InvokerServlet.doGet(InvokerServlet.java:18
0)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:740)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(Applica
tionFilterChain.java:247)
at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilt
erChain.java:193)
at
org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValv
e.java:260)
at
org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.i
nvokeNext(StandardPipeline.java:643)
at
org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:4
80)
at
org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995)
at
org.apache.catalina.core.StandardContextValve.invoke(StandardContextValv
e.java:191)
at
org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.i
nvokeNext(StandardPipeline.java:643)
at
org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:4
80)
at
org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995)
at
org.apache.catalina.core.StandardContext.invoke(StandardContext.java:239
6)
at
org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java
:180)
at
org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.i
nvokeNext(StandardPipeline.java:643)
at
org.apache.catalina.valves.ErrorDispatcherValve.invoke(ErrorDispatcherVa
lve.java:170)
at
org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.i
nvokeNext(StandardPipeline.java:641)
at
org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java
:172)
at
org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.i
nvokeNext(StandardPipeline.java:641)
at
org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:469
)
at
org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.i
nvokeNext(StandardPipeline.java:641)
at
org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:4
80)
at
org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995)
at
org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.
java:174)
at
org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.i
nvokeNext(StandardPipeline.java:643)
at
org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:4
80)
at
org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995)
at
org.apache.coyote.tomcat4.CoyoteAdapter.service(CoyoteAdapter.java:223)
at
org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:40
5)
at
org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.processC
onnection(Http11Protocol.java:380)
at
org.apache.tomcat.util.net.TcpWorkerThread.runIt(PoolTcpEndpoint.java:50
8)
at
org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool
.java:533)
at java.lang.Thread.run(Thread.java:536)
--------------------------------------------
Nathan McMinn
Application Developer
NequalsOne - HealthCare marketing tools
mailto:nmcminn@NequalsOne.com
http://www.NequalsOne.com
---------------------------------------------------------------------
To unsubscribe, e-mail: turbine-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: turbine-user-help@jakarta.apache.org
Re: Charset encoding issue
Posted by Mauro Piccini <mp...@tin.it>.
On Friday, September 19, 2003, at 01:27 AM, Scott Eade wrote:
> Mauro Piccini wrote:
>
>> I have some problem related to encoding.
>> I'm sending data to a Turbine application with special chars. Data
>> are correctly stored in the db but when I ask back for the data and I
>> print them ina a Velocity template, I only see strange characters.
>>
>> In TurbineResource.properties I have:
>> services.VelocityService.input.encoding=iso-8859-1
>> services.VelocityService.output.encoding=iso-8859-1
>> ....
>> locale.default.charset=iso-8859-1
>>
>> and in the template :
>> $page.setHttpEquiv("Content-Type","text/html; charset=iso-8859-1")
>>
>> I'm using turbine 2.3.
>>
>> I've tried all the combination of this parameters but nothing seems
>> to change.
>
> This may seem somewhat counter intuitive since the data is stored
> correctly, but can you confirm that you are setting the correct
> encoding in your JDBC driver configuration.
>
> Scott
>
Altought count intuituve, it is true!
After changing mysql jdbc driver from mm.mysql-2.0.13-bin.jar (a very
old version) to mysql-connector-java.3.0.8.jar ( latest stable ) it all
works.
Thank you very much!
Mauro Piccini
-------------
Muteki
Re: Charset encoding issue
Posted by Mauro Piccini <mp...@tin.it>.
On Friday, September 19, 2003, at 01:27 AM, Scott Eade wrote:
> Mauro Piccini wrote:
>
>> I have some problem related to encoding.
>> I'm sending data to a Turbine application with special chars. Data
>> are correctly stored in the db but when I ask back for the data and I
>> print them ina a Velocity template, I only see strange characters.
>>
>> In TurbineResource.properties I have:
>> services.VelocityService.input.encoding=iso-8859-1
>> services.VelocityService.output.encoding=iso-8859-1
>> ....
>> locale.default.charset=iso-8859-1
>>
>> and in the template :
>> $page.setHttpEquiv("Content-Type","text/html; charset=iso-8859-1")
>>
>> I'm using turbine 2.3.
>>
>> I've tried all the combination of this parameters but nothing seems
>> to change.
>
> This may seem somewhat counter intuitive since the data is stored
> correctly, but can you confirm that you are setting the correct
> encoding in your JDBC driver configuration.
>
> Scott
>
Altought count intuituve, it is true!
After changing mysql jdbc driver from mm.mysql-2.0.13-bin.jar (a very
old version) to mysql-connector-java.3.0.8.jar ( latest stable ) it all
works.
Thank you very much!
Mauro Piccini
-------------
Muteki
---------------------------------------------------------------------
To unsubscribe, e-mail: turbine-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: turbine-user-help@jakarta.apache.org
Re: Charset encoding issue
Posted by Scott Eade <se...@backstagetech.com.au>.
Mauro Piccini wrote:
> I have some problem related to encoding.
> I'm sending data to a Turbine application with special chars. Data are
> correctly stored in the db but when I ask back for the data and I
> print them ina a Velocity template, I only see strange characters.
>
> In TurbineResource.properties I have:
> services.VelocityService.input.encoding=iso-8859-1
> services.VelocityService.output.encoding=iso-8859-1
> ....
> locale.default.charset=iso-8859-1
>
> and in the template :
> $page.setHttpEquiv("Content-Type","text/html; charset=iso-8859-1")
>
> I'm using turbine 2.3.
>
> I've tried all the combination of this parameters but nothing seems to
> change.
This may seem somewhat counter intuitive since the data is stored
correctly, but can you confirm that you are setting the correct encoding
in your JDBC driver configuration.
Scott
--
Scott Eade
Backstage Technologies Pty. Ltd.
http://www.backstagetech.com.au
Re: Charset encoding issue
Posted by Scott Eade <se...@backstagetech.com.au>.
Mauro Piccini wrote:
> I have some problem related to encoding.
> I'm sending data to a Turbine application with special chars. Data are
> correctly stored in the db but when I ask back for the data and I
> print them ina a Velocity template, I only see strange characters.
>
> In TurbineResource.properties I have:
> services.VelocityService.input.encoding=iso-8859-1
> services.VelocityService.output.encoding=iso-8859-1
> ....
> locale.default.charset=iso-8859-1
>
> and in the template :
> $page.setHttpEquiv("Content-Type","text/html; charset=iso-8859-1")
>
> I'm using turbine 2.3.
>
> I've tried all the combination of this parameters but nothing seems to
> change.
This may seem somewhat counter intuitive since the data is stored
correctly, but can you confirm that you are setting the correct encoding
in your JDBC driver configuration.
Scott
--
Scott Eade
Backstage Technologies Pty. Ltd.
http://www.backstagetech.com.au
---------------------------------------------------------------------
To unsubscribe, e-mail: turbine-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: turbine-user-help@jakarta.apache.org
Re: AW: Charset encoding issue
Posted by Mauro Piccini <mp...@tin.it>.
Linux and MacOsX, same problem and same solution (change the mysql jdbc
driver)
Bye
Mauro Piccini
-------------
Muteki
On Friday, September 19, 2003, at 05:55 PM, Jürgen Hoffmann wrote:
> Hi Mauro
>
> What Operating System does your application run on? Linux or Windows
>
> Kind regards
>
> Jürgen Hoffmann
>
> -----Ursprüngliche Nachricht-----
> Von: Mauro Piccini [mailto:piccini@muteki.it]
> Gesendet: Donnerstag, 18. September 2003 19:22
> An: Turbine Users List
> Betreff: Charset encoding issue
>
>
> Hi.
>
> I have some problem related to encoding.
> I'm sending data to a Turbine application with special chars. Data are
> correctly stored in the db but when I ask back for the data and I print
> them ina a Velocity template, I only see strange characters.
>
> In TurbineResource.properties I have:
> services.VelocityService.input.encoding=iso-8859-1
> services.VelocityService.output.encoding=iso-8859-1
> ....
> locale.default.charset=iso-8859-1
>
> and in the template :
> $page.setHttpEquiv("Content-Type","text/html; charset=iso-8859-1")
>
> I'm using turbine 2.3.
>
> I've tried all the combination of this parameters but nothing seems to
> change.
>
> Thank you all.
>
>
> Mauro Piccini
> -------------
> Muteki
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: turbine-user-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: turbine-user-help@jakarta.apache.org
>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: turbine-user-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: turbine-user-help@jakarta.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: turbine-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: turbine-user-help@jakarta.apache.org
Re: AW: Charset encoding issue
Posted by Mauro Piccini <mp...@tin.it>.
Linux and MacOsX, same problem and same solution (change the mysql jdbc
driver)
Bye
Mauro Piccini
-------------
Muteki
On Friday, September 19, 2003, at 05:55 PM, Jürgen Hoffmann wrote:
> Hi Mauro
>
> What Operating System does your application run on? Linux or Windows
>
> Kind regards
>
> Jürgen Hoffmann
>
> -----Ursprüngliche Nachricht-----
> Von: Mauro Piccini [mailto:piccini@muteki.it]
> Gesendet: Donnerstag, 18. September 2003 19:22
> An: Turbine Users List
> Betreff: Charset encoding issue
>
>
> Hi.
>
> I have some problem related to encoding.
> I'm sending data to a Turbine application with special chars. Data are
> correctly stored in the db but when I ask back for the data and I print
> them ina a Velocity template, I only see strange characters.
>
> In TurbineResource.properties I have:
> services.VelocityService.input.encoding=iso-8859-1
> services.VelocityService.output.encoding=iso-8859-1
> ....
> locale.default.charset=iso-8859-1
>
> and in the template :
> $page.setHttpEquiv("Content-Type","text/html; charset=iso-8859-1")
>
> I'm using turbine 2.3.
>
> I've tried all the combination of this parameters but nothing seems to
> change.
>
> Thank you all.
>
>
> Mauro Piccini
> -------------
> Muteki
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: turbine-user-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: turbine-user-help@jakarta.apache.org
>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: turbine-user-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: turbine-user-help@jakarta.apache.org
>
AW: Charset encoding issue
Posted by Jürgen Hoffmann <jh...@byteaction.de>.
Hi Mauro
What Operating System does your application run on? Linux or Windows
Kind regards
Jürgen Hoffmann
-----Ursprüngliche Nachricht-----
Von: Mauro Piccini [mailto:piccini@muteki.it]
Gesendet: Donnerstag, 18. September 2003 19:22
An: Turbine Users List
Betreff: Charset encoding issue
Hi.
I have some problem related to encoding.
I'm sending data to a Turbine application with special chars. Data are
correctly stored in the db but when I ask back for the data and I print
them ina a Velocity template, I only see strange characters.
In TurbineResource.properties I have:
services.VelocityService.input.encoding=iso-8859-1
services.VelocityService.output.encoding=iso-8859-1
....
locale.default.charset=iso-8859-1
and in the template :
$page.setHttpEquiv("Content-Type","text/html; charset=iso-8859-1")
I'm using turbine 2.3.
I've tried all the combination of this parameters but nothing seems to
change.
Thank you all.
Mauro Piccini
-------------
Muteki
---------------------------------------------------------------------
To unsubscribe, e-mail: turbine-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: turbine-user-help@jakarta.apache.org
AW: Charset encoding issue
Posted by Jürgen Hoffmann <jh...@byteaction.de>.
Hi Mauro
What Operating System does your application run on? Linux or Windows
Kind regards
Jürgen Hoffmann
-----Ursprüngliche Nachricht-----
Von: Mauro Piccini [mailto:piccini@muteki.it]
Gesendet: Donnerstag, 18. September 2003 19:22
An: Turbine Users List
Betreff: Charset encoding issue
Hi.
I have some problem related to encoding.
I'm sending data to a Turbine application with special chars. Data are
correctly stored in the db but when I ask back for the data and I print
them ina a Velocity template, I only see strange characters.
In TurbineResource.properties I have:
services.VelocityService.input.encoding=iso-8859-1
services.VelocityService.output.encoding=iso-8859-1
....
locale.default.charset=iso-8859-1
and in the template :
$page.setHttpEquiv("Content-Type","text/html; charset=iso-8859-1")
I'm using turbine 2.3.
I've tried all the combination of this parameters but nothing seems to
change.
Thank you all.
Mauro Piccini
-------------
Muteki
---------------------------------------------------------------------
To unsubscribe, e-mail: turbine-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: turbine-user-help@jakarta.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: turbine-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: turbine-user-help@jakarta.apache.org
Charset encoding issue
Posted by Mauro Piccini <pi...@muteki.it>.
Hi.
I have some problem related to encoding.
I'm sending data to a Turbine application with special chars. Data are
correctly stored in the db but when I ask back for the data and I print
them ina a Velocity template, I only see strange characters.
In TurbineResource.properties I have:
services.VelocityService.input.encoding=iso-8859-1
services.VelocityService.output.encoding=iso-8859-1
....
locale.default.charset=iso-8859-1
and in the template :
$page.setHttpEquiv("Content-Type","text/html; charset=iso-8859-1")
I'm using turbine 2.3.
I've tried all the combination of this parameters but nothing seems to
change.
Thank you all.
Mauro Piccini
-------------
Muteki
---------------------------------------------------------------------
To unsubscribe, e-mail: turbine-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: turbine-user-help@jakarta.apache.org
Charset encoding issue
Posted by Mauro Piccini <pi...@muteki.it>.
Hi.
I have some problem related to encoding.
I'm sending data to a Turbine application with special chars. Data are
correctly stored in the db but when I ask back for the data and I print
them ina a Velocity template, I only see strange characters.
In TurbineResource.properties I have:
services.VelocityService.input.encoding=iso-8859-1
services.VelocityService.output.encoding=iso-8859-1
....
locale.default.charset=iso-8859-1
and in the template :
$page.setHttpEquiv("Content-Type","text/html; charset=iso-8859-1")
I'm using turbine 2.3.
I've tried all the combination of this parameters but nothing seems to
change.
Thank you all.
Mauro Piccini
-------------
Muteki