Hi Guillaume, The extensions.xml file is in the META-INF directory which is needed by the WSDL processor to determine what factory class is needed to parse WSDL extensors. I agree with you that exporting this directory is not a great thing as any other bundle that also has an extensors.xml will not be able to export that package without conflicts. We also ran into this problem with the META-INF/cxf directory for a bundle we created and had to put the cxf extensor info for this bundle in another directory. Regards, Seumas
-----Original Message----- From: Guillaume Nodet [mailto:[EMAIL PROTECTED] Sent: Tuesday, June 10, 2008 10:13 AM To: dev@cxf.apache.org Subject: Re: cxf-bundle.jar needs META-INF in the Export-Package list to make extensions.xml available in OSGi What's inside the META-INF folder that need to be exported ? Exporting the META-INF directory is a bad idea because if you have any other bundle that also exports the same package, your client bundle may fail, depending on which bundle is wired to it. Everything that need to be exported should be in a CXF specific package. Even export META-INF.cxf was not a very good idea, and ideally, the xml files should be moved to another folder like org.apache.cxf.xxx instead. On Tue, Jun 10, 2008 at 1:49 AM, Ramnarine, Michael <[EMAIL PROTECTED]> wrote: > A small change to cxf-bundle.jar is needed, to make extensions.xml > available, when this is used in OSGi. > > Would someone add META-INF to the Export-Package list, in > distribution/bundle/pom.xml? The syntax is probably the same as > META-INF.cxf, so '=META-INF'. > > We haven't moved to CXF 2.1 yet, so we need this on 2.0.x-fixes > initially. > > -Mike > -- Cheers, Guillaume Nodet ------------------------ Blog: http://gnodet.blogspot.com/
