Re: Need your help!!!

2003-07-06 Thread Holger Klawitter

> I installed Tomcat 4.1.24 on Solaris 2.6. After Tomcat is started up,
> servlets could be accessed, but all JSPs could not be accessed and below
> Exception is reported. Could you please give me some suggestion about how
> to solve it. Thanks a lot.

You don't have the full jdk installed, do you?

You need the full j2se, the jre is not enough as the jsp 
files need to be compiled into bytecode.

Mit freundlichem Gruß / With kind regards
Holger Klawitter
--
lists  klawitter  de


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Re: Jboss to parse exsisting tomcat server.xml ...

2003-07-06 Thread Venkat
I dont see any file called tomcat41-service.xml under jboss home directory.
should I create one if I dont find that file. I see this file
jboss-service.xml under
JBoss home directory.
--

"Paul Gregoire" <[EMAIL PROTECTED]> wrote in message
news:[EMAIL PROTECTED]
> -- this is my 4th attempt to answer a question please disregard if youve
> seen it already :) --
>
> To make changes to tomcat under jboss you must edit tomcat41-service.xml
not
> server.xml; changes made to the server.xml will not be used by tomcat.
> The Tomcat bundled with JBoss uses the tomcat41-service.xml file, located
in
> your /deploy directory of the selected configuration set. This file should
> be nearly identical to a regular server.xml.
>
> Might i suggest that you purchase the JBoss 3.0 Handbook for further
> details, this book kicks ASS!
>
http://www.amazon.com/exec/obidos/tg/detail/-/1861008120/qid=1045677540/sr=8
-1/ref=sr_8_1/104-9967696-6863144?v=glance&s=books&n=507846
>
> And no i dont get any kickbacks.. :(
>
> -Original Message-
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
> Sent: Tuesday, May 27, 2003 12:55 PM
> To: [EMAIL PROTECTED]
> Subject: Jboss to parse exsisting tomcat server.xml ...
>
>
> Hi,
> Can any one tell me ( or give me ) an example of how to make jboss
> parse my existing tomcat server.xml file ???
> jboss 3.0.X and tomcat 4.1.18. ( windows / linux )
>
>
>
> Thanks & Regards
> Guru :-)
>
>
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]




-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Webapp 501 error when using HTTPS.

2003-07-06 Thread Rai Ou
I am using Apache1.3.27 + webapp1.2(jakarta-tomcat-connectors-4.1.24-src)
 + Tomcat4.1.24, and I am using the servlet filter for redirect to Login
page when
the session is time out.

The system is running well but, after I built a SSL in my apache, I get the
501 error
when the sessin is time out and click the form button (it use the POST
method).
the error message is like this:  501 GET Method not implemented

but, when I click any hyper-link(it use the GET method), the filter can run
well and 
redirect to the Login page.

Any ideas for this problem ?
(Note: my OS is Sparc-Solaris8 and I download the apr-0.9.3 and compiled the
jakarta-tomcat-connectors-4.1.24-src source for geting the web_app.so and
warp.jar).




Need your help!!!

2003-07-06 Thread Cui Xiaojing-a13339
Hello ALL,

I installed Tomcat 4.1.24 on Solaris 2.6. After Tomcat is started up, servlets could 
be accessed, but all JSPs could not be accessed and below Exception is reported. Could 
you please give me some suggestion about how to solve it. Thanks a lot.

Regards,
Xiaojing


HTTP Status 500 - 
  _  

type Exception report

message 

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

exception 
org.apache.jasper.JasperException: Unable to compile class for JSP

An error occurred at line: -1 in the jsp file: null

Generated servlet error:
[javac] Since fork is true, ignoring compiler setting.
[javac] Compiling 1 source file
[javac] Since fork is true, ignoring compiler setting.



at java.lang.Throwable.fillInStackTrace(Native Method)
at java.lang.Throwable.fillInStackTrace(Compiled Code)
at java.lang.Throwable.(Compiled Code)
at java.lang.Exception.(Compiled Code)
at javax.servlet.ServletException.(ServletException.java:107)
at org.apache.jasper.JasperException.(JasperException.java:73)
at org.apache.jasper.compiler.DefaultErrorHandler.javacError(Compiled Code)
at org.apache.jasper.compiler.ErrorDispatcher.javacError(Compiled Code)
at org.apache.jasper.compiler.Compiler.generateClass(Compiled Code)
at org.apache.jasper.compiler.Compiler.compile(Compiler.java:370)
at 
org.apache.jasper.JspCompilationContext.compile(JspCompilationContext.java:473)
at 
org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:190)
at org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:295)
at org.apache.jasper.servlet.JspServlet.service(Compiled Code)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at 
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:247)
at 
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:193)
at 
org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:256)
at 
org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(Compiled
 Code)
at org.apache.catalina.core.StandardPipeline.invoke(Compiled Code)
at org.apache.catalina.core.ContainerBase.invoke(Compiled Code)
at 
org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191)
at 
org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(Compiled
 Code)
at org.apache.catalina.core.StandardPipeline.invoke(Compiled Code)
at org.apache.catalina.core.ContainerBase.invoke(Compiled Code)
at org.apache.catalina.core.StandardContext.invoke(Compiled Code)
at 
org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:180)
at 
org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(Compiled
 Code)
at 
org.apache.catalina.valves.ErrorDispatcherValve.invoke(ErrorDispatcherValve.java:171)
at 
org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(Compiled
 Code)
at 
org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:172)
at 
org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(Compiled
 Code)
at org.apache.catalina.core.StandardPipeline.invoke(Compiled Code)
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.invokeNext(Compiled
 Code)
at org.apache.catalina.core.StandardPipeline.invoke(Compiled Code)
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(Compiled Code)
at 
org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.processConnection(Http11Protocol.java:392)
at org.apache.tomcat.util.net.TcpWorkerThread.runIt(Compiled Code)
at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(Compiled Code)
at java.lang.Thread.run(Thread.java:479)
  _  
Apache Tomcat/4.1.24



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Re: Problem reloading unpacked web app with Tomcat 5.0.3

2003-07-06 Thread Michael Woinoski
I've refined the problem somewhat. I think I need to supply a Context with
reloadable set to true. So how do I do that with an expanded app? If I copy a
context definition () to webapps, Tomcat seems
to ignore it. I seem to remember reading that the context definition could be
stored in the app's META-INF dir, so I set Tomcat's unpackWARs to true and tried
the Ant deploy task again, but again the context definition was ignored.

thanks,
Mike

Michael Woinoski wrote:
> 
> I need to deploy a web app as an unpacked directory structure (the app needs to
> be able write a file to its WEB-INF). I also need to automate the deployment and
> reloading using Ant. So far, I've tried a few things:
> 
> 1. setting unpackWARs in server.xml to true and copying the war file to the
> webapps dir
> 2. copying the expanded directory structure directly in webapps
> 
> In both cases, the app deployment is successful initially. However, when I make
> changes (update the war file for case 1 or update the app's classes in case 2)
> Tomcat does not update the application (i.e., the class files are not reloaded.)
> 
> The Ant reload task gives errors in both cases. I tried to undeploy and deploy
> the app using the Ant undeploy task but the undeploy also gave errors in both
> cases (IncompatibleClassChangeError). However, I can remove the app with the gui
> app manager.
> 
> autoDeploy and liveDeploy are both set to true for the Host. Is there something
> else I need to do to notify Tomcat to reload the class files after
> modifications? Or is there another way to deploy the expanded app so it will be
> reloaded automatically?
> 
> Thanks,
> Mike
> 
> --
> 
> Mike Woinoski  Pine Needle Consulting
> mailto:[EMAIL PROTECTED]
> 
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]

-- 

Mike Woinoski  Pine Needle Consulting
mailto:[EMAIL PROTECTED]

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Re: JSP source compilation error

2003-07-06 Thread Joe McGranaghan
Thanks for your help Tim.


From: Tim Funk <[EMAIL PROTECTED]>
Reply-To: "Tomcat Users List" <[EMAIL PROTECTED]>
To: Tomcat Users List <[EMAIL PROTECTED]>
Subject: Re: JSP source compilation error
Date: Sun, 06 Jul 2003 12:02:34 -0400
http://jakarta.apache.org/tomcat/faq/misc.html#compile

-Tim

Joe McGranaghan wrote:
Using tomcat 4.1.18 I get the following error when trying to view my JSP 
page:

An error occurred at line: -1 in the jsp file: null

Generated servlet error:
   [javac] Compiling 1 source file
F:\Program 
Files\jakarta-tomcat-4.1.18\jakarta-tomcat-4.1.18\work\Standalone\localhost\lul\BrowseTop_jsp.java:168: 
handlePageException(java.lang.Exception) in javax.servlet.jsp.PageContext 
cannot be applied to (java.lang.Throwable)
 if (pageContext != null) pageContext.handlePageException(t);
 ^
1 error

at 
org.apache.jasper.compiler.DefaultErrorHandler.javacError(DefaultErrorHandler.java:130)

at 
org.apache.jasper.compiler.ErrorDispatcher.javacError(ErrorDispatcher.java:293)

at 
org.apache.jasper.compiler.Compiler.generateClass(Compiler.java:340)
at org.apache.jasper.compiler.Compiler.compile(Compiler.java:352)
at 
org.apache.jasper.JspCompilationContext.compile(JspCompilationContext.java:474)

at 
org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:184)

at 
org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:295)
at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:241)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:865)
at 
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:247)

at 
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:193)

at 
org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:260)

at 
org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:643)

at 
org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:480)
at 
org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995)
at 
org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191)

at 
org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:643)

at 
org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:480)
at 
org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995)
at 
org.apache.catalina.core.StandardContext.invoke(StandardContext.java:2415)
at 
org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:180)

at 
org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:643)

at 
org.apache.catalina.valves.ErrorDispatcherValve.invoke(ErrorDispatcherValve.java:170)

at 
org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:641)

at 
org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:172)

at 
org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:641)

at 
org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:480)
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.invokeNext(StandardPipeline.java:643)

at 
org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:480)
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:432)
at 
org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.processConnection(Http11Protocol.java:386)

at 
org.apache.tomcat.util.net.TcpWorkerThread.runIt(PoolTcpEndpoint.java:534)
at 
org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:530)

at java.lang.Thread.run(Thread.java:536)

Is there a way to fix the generated code problem without having to 
manually edit every
source file with the error? There must be a way.

_
MSN 8 helps eliminate e-mail viruses. Get 2 months FREE*.  
http://join.msn.com/?page=features/virus

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
_
Add pho

Re: JSP source compilation error

2003-07-06 Thread Tim Funk
http://jakarta.apache.org/tomcat/faq/misc.html#compile

-Tim

Joe McGranaghan wrote:
Using tomcat 4.1.18 I get the following error when trying to view my JSP 
page:

An error occurred at line: -1 in the jsp file: null

Generated servlet error:
   [javac] Compiling 1 source file
F:\Program 
Files\jakarta-tomcat-4.1.18\jakarta-tomcat-4.1.18\work\Standalone\localhost\lul\BrowseTop_jsp.java:168: 
handlePageException(java.lang.Exception) in 
javax.servlet.jsp.PageContext cannot be applied to (java.lang.Throwable)
 if (pageContext != null) pageContext.handlePageException(t);
 ^
1 error

at 
org.apache.jasper.compiler.DefaultErrorHandler.javacError(DefaultErrorHandler.java:130) 

at 
org.apache.jasper.compiler.ErrorDispatcher.javacError(ErrorDispatcher.java:293) 

at org.apache.jasper.compiler.Compiler.generateClass(Compiler.java:340)
at org.apache.jasper.compiler.Compiler.compile(Compiler.java:352)
at 
org.apache.jasper.JspCompilationContext.compile(JspCompilationContext.java:474) 

at 
org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:184) 

at 
org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:295)
at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:241)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:865)
at 
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:247) 

at 
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:193) 

at 
org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:260) 

at 
org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:643) 

at 
org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:480)
at 
org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995)
at 
org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191) 

at 
org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:643) 

at 
org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:480)
at 
org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995)
at 
org.apache.catalina.core.StandardContext.invoke(StandardContext.java:2415)
at 
org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:180) 

at 
org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:643) 

at 
org.apache.catalina.valves.ErrorDispatcherValve.invoke(ErrorDispatcherValve.java:170) 

at 
org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:641) 

at 
org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:172) 

at 
org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:641) 

at 
org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:480)
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.invokeNext(StandardPipeline.java:643) 

at 
org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:480)
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:432)
at 
org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.processConnection(Http11Protocol.java:386) 

at 
org.apache.tomcat.util.net.TcpWorkerThread.runIt(PoolTcpEndpoint.java:534)
at 
org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:530) 

at java.lang.Thread.run(Thread.java:536)

Is there a way to fix the generated code problem without having to 
manually edit every
source file with the error? There must be a way.

_
MSN 8 helps eliminate e-mail viruses. Get 2 months FREE*.  
http://join.msn.com/?page=features/virus

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


Re: NoSuchMethodException

2003-07-06 Thread Tim Funk
It sounds like a classpath / classloader issue. It sounds like there is jar 
floating around where it shouldn't be. (Probably - servlet.jar, the servlet 
api,  as part of the system classpath)

-Tim

Joe McGranaghan wrote:
Maybe I'm missing something, but to clarify:

It's not JSPs that are sending that error, it's servlets.
As far as I know a server doesn't create any generated code dependencies.
Thanks for your response.


From: "Andre D Bonner" <[EMAIL PROTECTED]>
Reply-To: "Tomcat Users List" <[EMAIL PROTECTED]>
To: "Tomcat Users List" <[EMAIL PROTECTED]>
Subject: Re: NoSuchMethodException
Date: Sat, 5 Jul 2003 17:37:27 -0400
Is the internal Server TOMCAT??

or the Oracle Servlet container?

If its the Oracle one, I suggest you look through the generated
code/dependancies
and remove all of the oracle specific stuff
- Original Message -
From: "Joe McGranaghan" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Saturday, July 05, 2003 5:35 PM
Subject: NoSuchMethodException
> I'm developing a web app in JDeveloper. Works fine while using its
embedded
> server, however, as soon as I deploy it to tomcat, my servlets throw 
this:
>
> Root cause:
>
>
>
> java.lang.NoSuchMethodError:
>
javax.servlet.http.HttpSessionBindingEvent.(Ljavax/servlet/http/HttpSession; 

Ljava/lang/String;Ljava/lang/Object;)V
> at
>
org.apache.catalina.session.StandardSession.setAttribute(StandardSession.jav 

a:1259)
> at
>
org.apache.catalina.session.StandardSessionFacade.setAttribute(StandardSessi 

onFacade.java:191)
> at
>
org.apache.catalina.session.StandardSessionFacade.setAttribute(StandardSessi 

onFacade.java:191)
> at lul.servlets.SearchAttribSetter.doGet(SearchAttribSetter.java:53)
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:740)
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:865)
> at
>
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(Application 

FilterChain.java:247)
> at
>
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterCh 

ain.java:193)
> at
>
org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.ja 

va:260)
> at
>
org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invok 

eNext(StandardPipeline.java:643)
> at
>
org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:480) 

> at 
org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995)
> at
>
org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.ja 

va:191)
> at
>
org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invok 

eNext(StandardPipeline.java:643)
> at
>
org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:480) 

> at 
org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995)
> at
> 
org.apache.catalina.core.StandardContext.invoke(StandardContext.java:2415) 

> at
>
org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:180 

)
> at
>
org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invok 

eNext(StandardPipeline.java:643)
> at
>
org.apache.catalina.valves.ErrorDispatcherValve.invoke(ErrorDispatcherValve. 

java:170)
> at
>
org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invok 

eNext(StandardPipeline.java:641)
> at
>
org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:172 

)
> at
>
org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invok 

eNext(StandardPipeline.java:641)
> at
>
org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:480) 

> 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.invok 

eNext(StandardPipeline.java:643)
> at
>
org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:480) 

> 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:432) 

> at
>
org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.processConne 

ction(Http11Protocol.java:386)
> at
> 
org.apache.tomcat.util.net.TcpWorkerThread.runIt(PoolTcpEndpoint.java:534) 

> at
>
org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.jav 

a:530)
> at java.lang.Thread.run(Thread.java:536)
>
>
> Help would be greatly appreciated
>
> _
> Protect your PC - get McAfee.com VirusScan Online
> http://clinic.mcafee.com/clinic/ibuy/campaign.asp?cid=3963
>
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>

Re: How to set default encoding to JSPs ?

2003-07-06 Thread Tim Funk
AFAIK - No.

But you could write a filter to do this for you. (Google on "servlet filter" 
or search the archives more more information on filters)

-Tim

Ido Kobelkowsky Diaz wrote:
Is there any way to set the default encoding to request, response and page
from one of the configuration files (server.xml web.xml ?)



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


JSP source compilation error

2003-07-06 Thread Joe McGranaghan
Using tomcat 4.1.18 I get the following error when trying to view my JSP 
page:

An error occurred at line: -1 in the jsp file: null

Generated servlet error:
   [javac] Compiling 1 source file
F:\Program 
Files\jakarta-tomcat-4.1.18\jakarta-tomcat-4.1.18\work\Standalone\localhost\lul\BrowseTop_jsp.java:168: 
handlePageException(java.lang.Exception) in javax.servlet.jsp.PageContext 
cannot be applied to (java.lang.Throwable)
 if (pageContext != null) pageContext.handlePageException(t);
 ^
1 error

	at 
org.apache.jasper.compiler.DefaultErrorHandler.javacError(DefaultErrorHandler.java:130)
	at 
org.apache.jasper.compiler.ErrorDispatcher.javacError(ErrorDispatcher.java:293)
	at org.apache.jasper.compiler.Compiler.generateClass(Compiler.java:340)
	at org.apache.jasper.compiler.Compiler.compile(Compiler.java:352)
	at 
org.apache.jasper.JspCompilationContext.compile(JspCompilationContext.java:474)
	at 
org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:184)
	at org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:295)
	at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:241)
	at javax.servlet.http.HttpServlet.service(HttpServlet.java:865)
	at 
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:247)
	at 
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:193)
	at 
org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:260)
	at 
org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:643)
	at 
org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:480)
	at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995)
	at 
org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191)
	at 
org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:643)
	at 
org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:480)
	at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995)
	at 
org.apache.catalina.core.StandardContext.invoke(StandardContext.java:2415)
	at 
org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:180)
	at 
org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:643)
	at 
org.apache.catalina.valves.ErrorDispatcherValve.invoke(ErrorDispatcherValve.java:170)
	at 
org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:641)
	at 
org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:172)
	at 
org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:641)
	at 
org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:480)
	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.invokeNext(StandardPipeline.java:643)
	at 
org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:480)
	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:432)
	at 
org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.processConnection(Http11Protocol.java:386)
	at 
org.apache.tomcat.util.net.TcpWorkerThread.runIt(PoolTcpEndpoint.java:534)
	at 
org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:530)
	at java.lang.Thread.run(Thread.java:536)

Is there a way to fix the generated code problem without having to manually 
edit every
source file with the error? There must be a way.

_
MSN 8 helps eliminate e-mail viruses. Get 2 months FREE*.  
http://join.msn.com/?page=features/virus

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


Re: NoSuchMethodException

2003-07-06 Thread Joe McGranaghan
Maybe I'm missing something, but to clarify:

It's not JSPs that are sending that error, it's servlets.
As far as I know a server doesn't create any generated code dependencies.
Thanks for your response.


From: "Andre D Bonner" <[EMAIL PROTECTED]>
Reply-To: "Tomcat Users List" <[EMAIL PROTECTED]>
To: "Tomcat Users List" <[EMAIL PROTECTED]>
Subject: Re: NoSuchMethodException
Date: Sat, 5 Jul 2003 17:37:27 -0400
Is the internal Server TOMCAT??

or the Oracle Servlet container?

If its the Oracle one, I suggest you look through the generated
code/dependancies
and remove all of the oracle specific stuff
- Original Message -
From: "Joe McGranaghan" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Saturday, July 05, 2003 5:35 PM
Subject: NoSuchMethodException
> I'm developing a web app in JDeveloper. Works fine while using its
embedded
> server, however, as soon as I deploy it to tomcat, my servlets throw 
this:
>
> Root cause:
>
>
>
> java.lang.NoSuchMethodError:
>
javax.servlet.http.HttpSessionBindingEvent.(Ljavax/servlet/http/HttpSession;
Ljava/lang/String;Ljava/lang/Object;)V
> at
>
org.apache.catalina.session.StandardSession.setAttribute(StandardSession.jav
a:1259)
> at
>
org.apache.catalina.session.StandardSessionFacade.setAttribute(StandardSessi
onFacade.java:191)
> at
>
org.apache.catalina.session.StandardSessionFacade.setAttribute(StandardSessi
onFacade.java:191)
> at lul.servlets.SearchAttribSetter.doGet(SearchAttribSetter.java:53)
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:740)
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:865)
> at
>
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(Application
FilterChain.java:247)
> at
>
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterCh
ain.java:193)
> at
>
org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.ja
va:260)
> at
>
org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invok
eNext(StandardPipeline.java:643)
> at
>
org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:480)
> at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995)
> at
>
org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.ja
va:191)
> at
>
org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invok
eNext(StandardPipeline.java:643)
> at
>
org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:480)
> at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995)
> at
> 
org.apache.catalina.core.StandardContext.invoke(StandardContext.java:2415)
> at
>
org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:180
)
> at
>
org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invok
eNext(StandardPipeline.java:643)
> at
>
org.apache.catalina.valves.ErrorDispatcherValve.invoke(ErrorDispatcherValve.
java:170)
> at
>
org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invok
eNext(StandardPipeline.java:641)
> at
>
org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:172
)
> at
>
org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invok
eNext(StandardPipeline.java:641)
> at
>
org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:480)
> 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.invok
eNext(StandardPipeline.java:643)
> at
>
org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:480)
> 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:432)
> at
>
org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.processConne
ction(Http11Protocol.java:386)
> at
> 
org.apache.tomcat.util.net.TcpWorkerThread.runIt(PoolTcpEndpoint.java:534)
> at
>
org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.jav
a:530)
> at java.lang.Thread.run(Thread.java:536)
>
>
> Help would be greatly appreciated
>
> _
> Protect your PC - get McAfee.com VirusScan Online
> http://clinic.mcafee.com/clinic/ibuy/campaign.asp?cid=3963
>
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
_
Add photos to your e-mail with MSN 8. Get 2 months FREE*.  
http://join.msn.com/?page=features/featuredemail

-

How to set default encoding to JSPs ?

2003-07-06 Thread Ido Kobelkowsky Diaz
Is there any way to set the default encoding to request, response and page
from one of the configuration files (server.xml web.xml ?)






-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Re: Confusing Tomcat/Apache/Linux problem

2003-07-06 Thread Martin Whelan
I'd get rid of Apache and run Tomcat as a standalone until you find the 
solution. It sounds like the context may not be set correctly. It's at 
least a good sign that the 404 is coming from Tomcat, it shows that the mod 
jk stuff is actually working.
Martin

At 15:04 05/07/2003 -0700, you wrote:

I'm helping somebody with a Tomcat installation that is being quite 
stubborn about working. He currently has Apache 1.3.20 acting as a proxy 
for Tomcat 4.1.24 on a Linux server. I've set up a trivial web app for 
Tomcat that consists of just a single html page. When I try to load the 
page I get a "404 - resource not available" page from Tomcat. I can tell 
from the logs that Tomcat is finding and loading my web app (its find the 
app specific web.xml), and matching the context path for the request. But 
then it can't find the html file, despite having found the web app 
previously. So it can find the file mytest/WEB-INF/web.xml when the server 
starts, but not mytest/index.html when a request comes in. The only things 
I can come up with are that filesystem permissions aren't set right 
(although I did chmod +rx for all the files in the web app), or that he 
shouldn't be using Tomcat 4.x with Apache 1.x. Anyone else have any ideas?



Mitch Ratisher
Silicon Valley Resident
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Martin Whelan
Déise Design - www.deisedesign.com
Tel : 058 23647
Mobile : 086 975



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


Re: Effect of J2SE upgrade on Tomcat

2003-07-06 Thread Bill Barker
AFAIK, there is no reason that you *have* to upgrade your TC version.  A
possible exception would be if you are using the stand-alone SSL Connector,
but I'm guessing that it would still work.

Of course, TC 3.2.x is no longer officially supported, so you can't expect
that any bugs that you report against it (e.g. you actually find problems
with the upgraded JVM) will be fixed.  The currently supported version for
the Servlet-2.2 Spec is TC 3.3.1(a).

"Govinda Rao, Ragavendiran" <[EMAIL PROTECTED]> wrote in message
news:[EMAIL PROTECTED]
> Hi,
>
> We intend to migrate our Java application to J2SE 1.4.2 from 1.3.1. I
would
> like to know whether I need to upgrade Tomcat 3.2.4 also at the same time.
> Any pointers would be very much appreciated
>
> Thanks,
> Raga




-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]