top button
Flag Notify
    Connect to us
      Site Registration

Site Registration

Tomcat: How do I call JspC manually?

0 votes
493 views

It looks like org.apache.jasper.JspC has a main() method defined, So how should I call it to generate the desired .class file?

posted Sep 1, 2014 by Kiran

Share this question
Facebook Share Button Twitter Share Button LinkedIn Share Button

1 Answer

0 votes

1) http://tomcat.apache.org/tomcat-8.0-doc/jasper-howto.html#Web_Application_Compilation

2) Generally, bin/tool-wrapper.bat, bin/tool-wrapper.sh is designed as a wrapper for such command-line tools, but JspC depends on org.apache.tools.ant.Task, so you need to have Apache Ant libs on the classpath.

3) protected static final String SWITCH_HELP = "-help";

answer Sep 1, 2014 by Dewang Chaudhary
Similar Questions
+1 vote

How do I start and stop just the tomcat admin application from a command line?

I had someone try to guess the password to my Tomee-Plume server last night. Thankfully I changed the default password and the hacker only tried twice. I want to be able to keep the admin application closed most of the time. On the rare occasion that I need access to the tomcat admin console I would like to start it up only for a brief period of time and then stop it.

Internet searches showed me how to stop other applications using the tomcat admin application. I want to stop just the Tomcat admin application not the whole server.

0 votes

I am just wondering whether somehow I can use web.xml to point to the Tomcat JDBC Realm that I am using. Are those two completely disjoint or I can link them together.

+1 vote

I think we can do it through the web.xml file located in tomcatconfweb.xml and then restart Tomcat.

Is there a difference if I change it in the tomcatconf location versus tomcatwebapps[web app name] web-infweb.xml location?

If I change the web.xml file in the tomcatconfweb.xml location will it override the web app location?

0 votes

Setup:
- Two physical servers each running Tomcat 7.0.42
- Brocade load balancer in front

The load balancer is set to source IP persistence for 5 minutes. This time can be changed of course.

The thing I don't understand is 5 minutes or 5 hours - at then end that time limit the user can be sent to the other server and lose data stored in the session.

So why do sticky sessions matter when session replication turned on in Tomcat? Is a performance issue?

...