title: Bundle gains unexplained requirement to different bundle when try to read XML
body: <p>This is an odd situation for me.  We have a large project using OSGI and I'm modifying one of the bundles.  Most of the changes work fine, except that when I try to update one part of the code to read some XML the bundle refuses to load.  I get an error message stating that my bundle is missing a constraint for jogl version 0.0.0.  My Bundle does not directly use JOGL, although a bundle it's dependent on does use JOG.  We have a jogl_1.1.1 bundle installed which is sufficient to load all the other JOGL dependent bundles; </p>
  
  <p>By commenting out parts of the code and testing I've discovered that I can import all of the appropriate classes, but the moment I try to use DocumentBuilderFactory to parse the XML I get the complaint about missing a JOGL bundle.  This occurs even if I add the DocumentBuilderFactory into a method that is never called; and occurs despite my ensuring the XML-APIS jar is in the class path.</p>
  
  <p>I'm at a complete lost for how XML parsing could be connected to JOGL.  Is a bundle version of 0.0.0 even valid?  I don't know where to go from here, so any suggestion as to the cause of this behavior or what I could try to address it is appreciated.</p>
  
  <p>Thanks</p>