On Mon, Nov 16, 2009 at 14:18, Sujoy <[email protected]> wrote: > Hi Alex, > > Thanks for the information but installing " org.apache.axis2.osgi" via Felix > console didn't not make any difference. There also some internal > dependencies are there which are hard to resolve. > > I was just searching over the net and found one link, > > https://svn.apache.org/repos/asf/webservices/axis2/scratch/java/saminda/osgi > _test > > It's a simple example where osgification of AXIS2 has been done > successfully. There also it's clearly stated there are around twenty two jar > are there as a part of an external dependencies with axis2 osgi bundle. > > I did follow the same steps for sling but failed at the final steps by > showing the following error message. > > 16.11.2009 18:31:46.991 *ERROR* [Configuration Updater] > org.apache.felix.configadmin Service > [org.apache.felix.cm.ConfigurationAdmin,17] > [org.osgi.service.cm.ManagedService]: Unexpected problem updating > configuration (javax.xml.stream.FactoryConfigurationError: Requested factory > com.ctc.wstx.stax.WstxInputFactory cannot be located. Classloader > =sun.misc.launcher$appclassloa...@e39a3e) > javax.xml.stream.FactoryConfigurationError: Requested factory > com.ctc.wstx.stax.WstxInputFactory cannot be located. Classloader > =sun.misc.launcher$appclassloa...@e39a3e > at > javax.xml.stream.FactoryLocator.loadFactory(FactoryLocator.java:120) > at javax.xml.stream.FactoryLocator.locate(FactoryLocator.java:109) > at javax.xml.stream.FactoryLocator.locate(FactoryLocator.java:54) > > If I am not wrong then this error is coming due to OSGI class loading > mechanism. If you can put some light on this will be helpful :-)
I think you should try and include all the bundles necessary, as the project you mention has done already. For OSGi, bundles are required, which are normal jar files with additional information about what packages to import and export. Apart from dynamic resolution of packages at runtime (finding which bundle currently provides a package), OSGi allows bundles to have private packages that are invisible to other bundles. For non-bundleized jars this means some up-front manual work. Regards, Alex -- Alexander Klimetschek [email protected]
