On Thu, Mar 19, 2009 at 1:35 AM, Willem Jiang willem.ji...@gmail.com wrote:
Ah, another OSGi issue.
Charles, you are exploring a new world with CXF and Camel.
Please feel free to fill a JIRA when you get into trouble.
Maybe we could use the OSGi resolver to look up the wsdl file.
Since we just pass the wsdl location as a String into CXF in
the camel-cxf component, we may need do some work on CXF side.
Yeah in Camel 2.0 there is API on CamelContext to get a ClassResolver
that can be injected with a OSGi aware.
Please use this API to get hold of resolvers as it should then be the
same API used by components. But the impl behind them can be OSGi
specific, JBoss specifc, WebSphere specifc and the default ones, etc.
Willem
cmoulliard wrote:
Hi,
I have created two bundles :
- one for the files generated by wsdl2java of CXF = bundle
reportingincident.service (= bundle A)
- and the other for my camel-context using these files = bundle
reportingincident.camel (= bundle B)
In the bundle A, I have created a directory under META-INF called wsdl where
my reporting_incident.wsdl file is and exported the package (in this case,
the wsdl file) using the syntax :
Export-PackageMETA-INF.wsdl/Export-Package
The bundle B imports the package META-INF.wsdl using the following syntax
Import-PackageMETA-INF.wsdl/Import-Package
Unfortunately, when Camel-cxf endpoint and CXF are created and started
during the load of the camel-context, Cxf claims that it does not find the
file under
c:///apache-servicemix-kernet-1.1.0-SNAPSHOT/bin/reporting_incident.wsdl
According to the documentation of camel-cxf endpoint, the wsdl file defined
for the parameter wsdlUrl is loaded through the classpath.
This is not the case here, why ?
Regards,
-
Charles Moulliard
SOA Architect
My Blog : http://cmoulliard.blogspot.com/ http://cmoulliard.blogspot.com/
--
Claus Ibsen
Apache Camel Committer
Open Source Integration: http://fusesource.com
Blog: http://davsclaus.blogspot.com/
