Hi, I'm running a webapp which use jaf (java activation framework) for javamail. In the past it was possible to deploy different versions of our webapp in different contexts of one tomcat instance. Jaf always was a jar within our context. Since java 6 jaf is included in java 6 and we removed it from our webapp. But since it is part of java 6 it is also loaded by the system classloader (I think). When we now load multiple contexts with different versions of our webapp. The contexts share some jaf internal map's about mimetype mappings. This conflicts, because newer version of our webapp have more mimetype mappings than the older ones, but the older ones do find the mappings now.
Do other people see this? And do you have a workaround? Googling gave me 1 person with the same problem, but not with Tomcat, so he had a workaround which didn't apply for my situation. Is there anything else I can do than run multiple instances of Tomcat? Does it give problems to put the jar of jaf back in my webapp? I don't like it to have double classes in the classpath. Ronald. <offtopic>PS: How can I stop Sun from adding so much (JAF, JAXB, etc.) in the JVM? This makes my application a lot less flexible for deployment.</offtopic>
