Re: TLS-Enabled Connector Prevents Startup

Has the certificate the SSL/TLS connection uses expired? This will cause the TLS connection to fail to come up. Then, if you have a security constraint defined in your web.xml file that requires TLS for your initial pages, the redirect from your normal port to the TLS port will fail (since the

RE: jspc

Hi Paul, To specify a path for your compilation results use the -d option like so: jspc.sh -compile -d /jakarta-tomcat-5.0.25/webapps myapp/WEB-INF/classes ...the rest of you compile options... It will build any subdirs required using the directory you specify, along with the package name you

Re: jspc

Paul, I just use the -compile option and have jspc do the compilation from .java to .class for me. It seems to work fairly well. Once all the fully compiled (ie .class) files are placed in you applications WEB-INF/classes directory you just need to place the generated web.xml file in WEB-INF.

Re: tomcat 4.1.x jsp pre-compilation

Hi Woodchuck, I just fought the exact same thing for two weeks and this is what I discovered: If you want to precompile all the JSPs with a package name other than org.apache.jsp you have to use the -p option and give it a new package name. This doesn't really work, as you may have already

Servlet ... threw load() exception - ActionServlet.parseModuleConfigFile

I have a webapp that runs in Tomcat 4.1.18 fine, but when I load them into Tomcat 5.0.25 I get an HTTP Status 503 - Servlet action is currently unavailable error. I get the following error on Tomcat startup in my Tomcat log: 2004-06-08 13:57:08

struts or parser change from Tomcat 4.x to 5.x?

I know all the files are the same. Did anything change between Tomcat 4.x anf 5.x with regards to struts? Any help or pointers would be appreciated. Thanks, Jason Jason Palmatier [EMAIL PROTECTED] wrote: I have a webapp that runs in Tomcat 4.1.18 fine, but when I load them into Tomcat

Solved: struts or parser change from Tomcat 4.x to 5.x?

? Jason --- Jason Palmatier [EMAIL PROTECTED] wrote: I have an application that runs fine in Tomcat 4.1.18 but gives me a Status 503 - Servlet action is currently unavailable error when I try to run it with Tomcat 5.0.25. The full error from the Tomcat log is below. I checked

JspC compile error output - where's it go?

Does anyone know how to get jspc to display compile errors it encounters when compiling a jsp to a .java file? I haven't been able to get it to work with 4.1.18 or 5.0.19. I've looked through the source code for JspC and it seems like it should be throwing JasperExceptions if it encounters an

Re: JspC compile error output - where's it go?

. This seems quite odd since the above messages seem to indcate that everything went fine. Is this a bug in the JspC compiler for 5.0.19? Jason --- Jason Palmatier [EMAIL PROTECTED] wrote: Does anyone know how to get jspc to display compile errors it encounters when compiling a jsp to a .java

Tomcat compile vs. jspc/jasper compile (was: 0 length .java files generated by jspc?)

First off, the 0 length Java files are due to a bug in the Tomcat jspc compiler documented in this post: http://junlu.com/msg/41035.html Secondly I discovered that if I keep the JSP around and then simply access it through a browser Tomcat compiles the JSP correctly and I end up with a valid

RE: Tomcat compile vs. jspc/jasper compile (was: 0 length .java files generated by jspc?)

Hi Yoav, Thanks for the reply. I'm stuck using 4.1.18 so the bug still applies to me :). However I did take my webapp code and copy it into a 5.0.19 install I had laying around. I then ran the compile under 5.0.19 and saw that no 0 length java file was created (this version must have the bug

404 Error when accessing pre-compiled JSPs

Hello everyone, I am attempting to deploy pre-compiled jsps in Tomcat 4.1.18 (I can't upgrade, I'm stuck with 4.1.18). I've searched the archive extensively and found that I am doing all the things suggested, but I still cannot seem to find any of my web pages. I'm wondering if any of my steps

Re: 404 Error when accessing pre-compiled JSPs

compile fine, but there are a number that end up as zero length .java files after compiling them with jspc. Is there any reason why jspc might create empty .java files for what look to be relatively simple, but correct, .jsp files? --- Jason Palmatier [EMAIL PROTECTED] wrote: Hello everyone, I am

0 length .java files generated by jspc?

Hi, We have some JSP files that get autogenerated by a development tool we are using and they display fine when run normally in Tomcat. However, when we try to precompile them using jspc we always end up with a few 0 length .java files. These are generally JSPs that define sections of a

Re: JSP Compiling - painted in a corner?

Hello Illya, Thank you VERY much for your reply. The fact that Tomcat 5.x includes the directory structure in package statements and 4.x does not makes everything I've been doing much clearer. I need to go back and start from the beginning using Tomcat 5.x and Ant and see if I can get it

Re: JSP Compiling - painted in a corner?

included in their package statement. Then do the compile from .java to .class files. Is having the subdirectories in the package statement the crucial step I need to solve this? Jason --- Illya Kysil [EMAIL PROTECTED] wrote: Jason Palmatier wrote: I'm trying to precompile JSPs and have run

Re: JSP Compiling - painted in a corner?

/servlet-name url-pattern/entry_process.jsp/url-pattern /servlet-mapping servlet-mapping servlet-nameorg.apache.jsp.gso_jsp/servlet-name url-pattern/gso.jsp/url-pattern /servlet-mapping Jason --- QM [EMAIL PROTECTED] wrote: On Tue, May 25, 2004 at 09:12:58AM -0700, Jason Palmatier wrote

Re: JSP Compiling - painted in a corner?

no mapping in web.xml since it compiles into the tomcat work directory, where Jasper loads the classes from Filip - Original Message - From: Jason Palmatier [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Monday, May 24, 2004 12:51 PM Subject: JSP Compiling - painted in a corner

Re: JSP Compiling - painted in a corner?

Okay, I've copied my files to my PC and attempted to run the Ant build using the build.xml given on the Tomcat 5.0 site. It runs for about 2 seconds and spits out this error: C:\apache-ant-1.6.1\bin\build.xml:21: java.lang.VerifyError: (class: org/apache/ xerces/jaxp/DocumentBuilderImpl, method:

JSP Compiling - painted in a corner?

Hello, I'm trying to precompile JSPs and have run into some trouble with the mappings. First off I CANNOT use the Ant build method as specified in http://jakarta.apache.org/tomcat/tomcat-5.0-doc/printer/jasper-howto.html#Web%20Application%20Compilation; due to a lack of certain UNIX commands on

Re: Tomcat with SSL

It looks like you are using WebSphere and may be getting tangled up in IBM's version of Sun's JSSE. I ran into a similar problem on an IBM iSeries server and posted my eventual soultion here:

Changing java.security file values via command line?

Hello Everyone, I have successfully modified a java.security file to allow an SSL connection for a Tomcat server but now want to have those changes applied only for my Tomcat startup (i.e. not change the JVM's java.security file). I found some documentation that said you could provide your own

RE: Getting basic Logging up and running

Thank you very much Yoav! I actually ended up just adding the following lines to startup.sh instead of creating the configuration file commons-logging.properties : export -s CATALINA_OPTS=-Dorg.apache.commons.logging.Log=org.apache.commons.logging.impl.SimpleLog

RE: Getting basic Logging up and running

Informatics -Original Message- From: Jason Palmatier [mailto:[EMAIL PROTECTED] Sent: Wednesday, April 07, 2004 5:27 PM To: [EMAIL PROTECTED] Subject: Getting basic Logging up and running Hi, I've been trying to get basic logging up and running so I can diagnose an SSL

Getting basic Logging up and running

Hi, I've been trying to get basic logging up and running so I can diagnose an SSL connection problem. I've searched the archive and google for a full day and picked up bits and pieces, which I cobbled together, but still can't seem to get any more output then the initial startup (i.e. output