Message4099

So, you are using 2 different versions of jython.jar in 2 different web
applications?

That should not create any problems, because the two different web
applications should each have a separate class loader; each class loader
should see a different jython.jar, and load the classes from it
completely independently.

If this is not happening, then you need to read the documentation for
your servlet container, in order to understand how class-loading within
that container works. For example, you may have a copy of jython.jar
being loaded by a classloader further up the class-loading hierarchy,
which is over-riding any jython.jar further down the hierarchy, such as
in the WEB-INF/lib of an individual application. In this case, you would
have to delete the jython.jar from further up the hierarchy, and also
make sure that your application configuration ensures that jars are
loaded from the local WEB-INF/lib *before* class-loading is delegated up
the hierarchy.

It is not possible to guess the actual cause of your problems without
knowing A: the container being used and B: how you have configured it.

Here is the relevant documentation for Apache Tomcat
http://tomcat.apache.org/tomcat-5.5-doc/class-loader-howto.html

And here is the documentation for Sun Java System Application Server
Platform
http://docs.sun.com/app/docs/doc/819-3659/beadf?a=view