The ConfigAdmin has no relationship to the javax.transaction.xa package. Do you use some JEE technologies such as JMS / XA transaction manager ? The problem with this package is that the JVM has a trimmed down version of this package, but any JEE technology will need the full package and this require a bit of tweaking in the configuration for the packages exported by the system bundle.
On Fri, Sep 4, 2009 at 06:24, Mark Derricutt <[email protected]> wrote: > Should this be a drop in replacement/update to people running ConfigAdmin > 1.0.8 at all? I'm not entirely sure what the implication of "upcoming 1.3 > spec" entails. Is there a minimum Felix/OSGi setup needed? > When the only change to my sling based app was going from 1.0.8 to 1.2.0 > the > system dies horribly on startup with: > > Caused by: java.lang.ClassNotFoundException: > javax.transaction.xa.XAResource > at > > org.apache.felix.framework.searchpolicy.R4SearchPolicyCore.findClass(R4SearchPolicyCore.java:198) > at > > org.apache.felix.framework.searchpolicy.R4SearchPolicy.findClass(R4SearchPolicy.java:45) > at > > org.apache.felix.framework.searchpolicy.ContentClassLoader.loadClass(ContentClassLoader.java:109) > at java.lang.ClassLoader.loadClass(ClassLoader.java:252) > > > > > -- > Pull me down under... > > Sent from Auckland, Auk, New Zealand > > On Tue, Aug 25, 2009 at 8:22 PM, Felix Meschberger <[email protected] > >wrote: > > > The Apache Felix Configuration Admin Service is an implementation of the > > upcoming OSGi Configuration Admin Service Specification 1.3 > > > -- Cheers, Guillaume Nodet ------------------------ Blog: http://gnodet.blogspot.com/ ------------------------ Open Source SOA http://fusesource.com
