On Mon, Sep 29, 2008 at 2:15 PM, David Leangen <[EMAIL PROTECTED]> wrote: > >> I guess that largely depends on what mechanism the legacy jar uses. >> If the correct API is used, I don't see why it wouldn't work. >> What is the exception? > > > Caused by: java.lang.ClassNotFoundException: > org.apache.xerces.parsers.DOMParser > > > I'm in the process of creating a wrapper bundle that provides xerces, > but this feels like a total hack, since I'm providing stuff for the > internal implementation of this jar (or of the xml service, take your > pick).
Do you have access to source code of it? It could be that Xerces is instantiated directly, and not in the JDK as expected. In that case, figure out what Xerces version it expects, and stick that into the same bundle as an internal jar. Cheers Niclas _______________________________________________ OSGi Developer Mail List osgi-dev@mail.osgi.org https://mail.osgi.org/mailman/listinfo/osgi-dev
