HI, I have an intermittant problem using apache xalan (2.7.1) in my osgi application. It seems that my app is sometimes picking up the endorsed extensions version of xalan under com.sun.org.apache from rt.jar(which doesn't work for me), at other times it picks up the version I've wrapped in an osgi bundle. This happens on standalone builds as well as when run under eclipse.
When it picks up the rt.jar version xalan fails to to generate its template classes and I see a stack trace with com.sun.org.apache... When it picks up the desired version it works properly. I can verify the new xalan version is being used in several ways including debugging and seeing the expected org.apache... in the call stack. On a few occasions I've also seen "incompatible class" errors when running under eclipse. This seems to happen randomly, at least nothing I do to the imports and exports of bundles or packages, setting versions etc. makes any difference (as verified by doing clean builds from different versions of my sourcebase). Is there any way to control the use of java endorsed extensions? I'd thought that this was one of the main points of OSGI but I can't seem to get it working. I had suspected that the JAXP implementation registrations had something to do with this as I didn't do anything with the ServiceRegistry declarations when creating the xalan bundle, but as it does work half the time this doesn't fit. I'm running compiling with Eclipse 3.3 and running both within eclipse run/debug and standalone under Equinox 3.3 built with the eclipse pde compiler. Any light anyone can cast on this would be appreciated I'm at a complete loss now. Thanks -- - MikeG _______________________________________________ OSGi Developer Mail List [email protected] http://www2.osgi.org/mailman/listinfo/osgi-dev
