https://issues.apache.org/bugzilla/show_bug.cgi?id=49897
Jeremias Maerki <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- Summary|Linkage error on |Linkage error on |org.w3c.dom.event |org.w3c.dom.event | |(OSGi-related) --- Comment #2 from Jeremias Maerki <[email protected]> 2010-10-01 03:12:59 EDT --- I've run into similar issues, BTW. I'm also working in an OSGi environment. I suggest that we work towards removing any W3C DOM sources from Batik and instead cooperate with the Xerces team who maintains xml-apis and xml-apis-ext. I've done these things to my local Batik working copy but right now I don't remember which steps I took exactly. I'll need to find time to replicate that and propose a concrete changes to Batik. A little background concerning OSGi: Every OSGi bundle (JAR plus manifest metadata) declares exactly which Java packages it imports and which it exports. The OSGi framework then does the wiring of the packages based on version information in a network of class loaders rather than the hierarchical class loader used by normal Java applications. Therefore, problems arise as soon as two JARs provide classes in the same Java package, ex. org.w3c.dom.events. -- Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug. --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
