Hi Achim
Again thanks for your response. I have managed to reproduce this problem with
very little code. The key lines in my manifest are:
Bundle-ClassPath: ., WEB-INF/classes,
WEB-INF/lib/mysql-connector-java-3.1.14-bin.jar, WEB-INF/lib/poppet-1.8.jar,
WEB-INF/lib/sound-1.6.jar, WEB-INF/lib/xercesImpl-2.8.1.jar
Import-Package: javax.naming, javax.servlet, javax.servlet.http,
javax.servlet.jsp, javax.swing, javax.xml.parsers, org.ops4j.pax.web.service,
org.osgi.framework, org.osgi.service.http, org.w3c.dom, uk.ac.stir.cs.poppet
I created a tiny JSP that fails in the same way as the bigger one:
<%@ page import = "org.w3c.dom.*" %>
<%
out.println("<p>done</p>");
%>
The failure is due to the import of "org.w3c.dom". This is part of
"xercesImpl-2.8.1.jar". This all works fine when I deploy under Tomcat.
I have a slight suspicion that Knopflerfish may not be providing access to
classes in "rt.jar", but if so then I don't know why.
Perhaps "org.w3c.dom" is using some internal class I don't know about but that
needs to be imported? There are sometimes internal implementation classes.
Perhaps some other bundle (in Pax Web) is using an incompatible version of
Xerces? All mine are using the same version.
Thanks, Ken
--
The Sunday Times Scottish University of the Year 2009/2010
The University of Stirling is a charity registered in Scotland,
number SC 011159.
_______________________________________________
general mailing list
[email protected]
http://lists.ops4j.org/mailman/listinfo/general
