3 Replies Latest reply on Oct 10, 2011 9:05 PM by ffang

    classpath from different bundle...

    fphilip

      Hi, any idea how i do to load wsdl from another bundle that i call?

       

      <cxfbc:consumer

                  wsdl="classpath:META-INF/.....wsdl

        • 1. Re: classpath from different bundle...
          michal.warecki

          In bundle that exports wsdl you have to export META-INF directory (i. e. using felix plugin you have to add '=META-INF' in 'Export-Package'). In bundle that wants to import that wsdl you have to import META-INF (i.e. META-INF in 'Import-Package')

           

          Micha&#322;

          • 2. Re: classpath from different bundle...
            fphilip

            These guidelines are in place, and the web console tells me that the relationship is resolved .. But is not resolved

             

             

            This is the error, but, the now, after 30 time.. works ;P

             

            Caused by: java.io.FileNotFoundException: OSGi resource[:META-INF/ovs-connect-documents/ovs-connect-documents-1.0.wsdl|bnd.id=284|bnd.sym=ovs-connect-documents-servicemix-cxfbc] cannot be resolved to URL because it does not exist

             

            Edited by: fphilip on Oct 10, 2011 8:22 PM

            • 3. Re: classpath from different bundle...
              ffang

              Hi,

               

              I think the problem is that a lot of bundles have common META-INF package so your customer bundle actually don't know which one it should import.

               

              So you can put your wsdl from another bundle in a special package like META-INF/mywsdl/, then export and import it from your customer bundle.

               

              Freeman