Description David Savage 2010-07-15 04:13:43 EDT

Build Identifier: 

The problem here is that this causes uses constraint violations when deploying this bundle along side other bundles that import javax.xml.* packages. In felix the framework exports these packages as version=0.0.0.1_006_JavaSE.

I think there are a number of aspects to fixing this however. 

Firstly do the javax.xml packages need to be exported at all? In apache cxf that also uses the javax.xml.* packages their solution is to import the packages with no version, i.e. Import-Package: javax.xml.namespace,org.apache.foo;version=1.0.0. Then rely on the framework to provide these packages vs embedding them in the bundle. This may or may not be appropriate for your usecase.

If they do need to be exported then the javax.xml packages probably shouldn't be inheriting the Tomcat bundle version. But if not then what version should they have? Given this is under discussion by OSGi Alliance not sure what the best answer is.

In my local build I've fixed this problem by rebuilding the tomcat bundle with the following change to org.eclipse.gemini.web.tomcat/template.mf

diff --git a/org.eclipse.gemini.web.tomcat/template.mf b/org.eclipse.gemini.web.tomcat/template.mf
index 6d62570..3109d45 100644
--- a/org.eclipse.gemini.web.tomcat/template.mf
+++ b/org.eclipse.gemini.web.tomcat/template.mf
@@ -28,4 +28,4 @@ Import-Template: org.eclipse.gemini.web.*;version="1.0",
  org.w3c.dom.*;version="0"
 Import-Package: org.apache.catalina.deploy;version="6.0.20.S2-r5956"
 Bundle-Activator: org.eclipse.gemini.web.tomcat.internal.Activator
-Excluded-Exports: *.internal.*
+Excluded-Exports: *.internal.*,javax.*

This seems to work in my testing but I'm not sure if this has unintended consequences outside of the tests I've done (install a simple gwt app as a wab)

Reproducible: Sometimes

Steps to Reproduce:
Happens if gemini bundles are installed along side other bundles that use javax.xml.* packages