I am running into an issue wherein the Pax Web WAR Extender is importing a
different version of javax.servlet than a WAR that it is deploying.  This
causes class cast exceptions on javax.servlet.*.  I tried specifying the
version of javax.servlet in my WAR's manifest as the same version that was
being imported by the WAR Extender, but I discovered that the WAR Extender
picks up different versions of javax.servlet depending on when it is loaded. 
Is there a way to guarantee that my war picks up the same version of
javax.servlet as the PAX Web War Extender?

--
View this message in context: 
http://karaf.922171.n3.nabble.com/How-to-Guarantee-that-a-WAR-Imports-the-Same-Version-of-javax-servlet-As-Pax-Web-tp2900224p2900224.html
Sent from the Karaf - User mailing list archive at Nabble.com.

Reply via email to