Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Replace jakarta references with something more up-to-date

...

However, do not add questions without answers to this page. If you have a question about how to do something in Tomcat which has not been addressed yet, ask the tomcat-user list. Once you've figured out how to fix your problem, come back and update the Wiki to allow the rest of us to benefit from what you've learned!

...

In particular, here are a number of locations for Tomcat Connectors:

The following excellent article was written by Mladen Turk. He is a Developer and Consultant for JBoss Inc in Europe, where he is responsible for native integration. He is a long time commiter for Jakarta Tomcat Connectors, Apache Httpd and Apache Portable Runtime projects.

...

You cannot share sessions directly across web apps, as that would be a violation of the Servlet Specification. There are workarounds, including using a singleton class loaded from the common classloader repository to hold shared information, or putting some of this shared information in a database or another data store. Some of these approaches have been discussed on the tomcat-user mailing list, whose archives you should search for more information.

Sharing sessions across containers for clustering or replication purposes is a different matter altogether.

...

I

...

First, add this to the top of your properties:

No Format

<property environment="env" />

Next find this line in the "war" target:

No Format

<classes dir="${build.dir}" includes="**/*.properties" />

Change it so it reads like this:

No Format

<classes dir="${src.dir}" includes="**/*.properties" />

Now it will work!

I'm encountering classloader problems when using JNI under Tomcat

...

  • Download the source bundle or grab the source XML file from CVS Subversion repository. The docs are in the jakarta-tomcat-catalina CVS module, in the webapps/docs subdirectory. They are in XML format and get processed into the HTML documentation as part of the Tomcat release.

...

  • Open a Bugzilla enhancement item with the explanation of your enhancements, and attach a svn diff or diff -u format of your patch. We will evaluate and commit your patch as needed. Note that the Tomcat web site is updated with every release, so that documentation changes will not be visible as soon as you submit your Bugzilla itemuntil next Tomcat release.
  • If you're interested in previewing your changes, you will need to follow the directions for building Tomcat yourself. The docs will be generated in the webapps/tomcat-docs directory just like with any normal Tomcat distributions.If you'd like to get documentation up and visible to the world before the next Tomcat release, use this wiki
  • Documentation for current (unreleased) versions of Tomcat 6 and Tomcat 7 is published by ASF Buildbot. See links on the buildbot page on Apache Tomcat web site.

...