Page History

   }}}
----

''' How do I share sessions across webapps?'''

You cannot share sessions directly across webapps, 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 contains for clustering or replication is
a different matter altogether.

----

''' Why doesn't the netbeans example build for me? '''

I have found 2 issues with the build.xml provided here:
http://jakarta.apache.org/struts/faqs/netbeans.html

First, add this to the top of your properties:
<property environment="env" />

Next find this line in the "war" target:
<classes dir="${build.dir}" includes="**/*.properties" />

Change it so it reads like this:
<classes dir="${src.dir}" includes="**/*.properties" />

Now it will work!

----

'''I'm encountering classloader problems when using JNI under Tomcat'''

The important thing to know about using JNI under Tomcat is that one cannot place the native libraries OR their JNI interfaces under the WEB-INF/lib or WEB-INF/classes directories of a web application and expect to be able to reload the webapp without restarting the server. The class that calls System.loadLibrary(String) must be loaded by a classloader that is not affected by reloading the web application itself.

Thus, if you have JNI code that follows the convention of including a static initilaizerinitializer like this:

{{{  class FooWrapper { 
    static { 
        System.loadLibrary("foo"); 
    } 

    native void doFoo(); 
  }