We are having a problem utilizing org.apache.cxf.jaxws.JaxWsProxyFactoryBean
within an OSGi container.

I have successfully deployed a CXF endpoint that uses JAX-WS/JAXB and I can
call this via a JUnit and through a web application that I have both
deployed in Jetty and WebLogic.

But when we try to do the same invocation via a OSGi container (Felix in
this case, via Day for WCM), we get the following issue described by one of
the developers.  He is explaining that as CXF has a problem finding some of
the schemas it expects on the classpath and his concern is the leading "/"
in some of the relative paths.

Description
--------------------------------------------

All the cxf singletons are loaded correctly in the bundle  (notice path 
META-INF/cxf/cxf-extension-http-jetty.xml]

It starts to get into errors when it tries to build the service from Class

Dec 5, 2010 5:17:10 PM
org.apache.cxf.service.factory.ReflectionServiceFactoryBean
buildServiceFromClass

Look at the paths , there is a /  in front of the xsd . It cannot resolve
this enven though it is in the bundle jar

org.apache.jackrabbit.classloader.DirectoryClassPathEntry
getResource: problem accessing the resource [/schemas/wsdl/wsrm.xsd

ERROR LOG

INFO: Loading XML bean definitions from class path resource
[META-INF/cxf/cxf-extension-http-jetty.xml]
Dec 5, 2010 5:17:09 PM
org.springframework.beans.factory.xml.XmlBeanDefinitionReader
loadBeanDefinitions
INFO: Loading XML bean definitions from class path resource
[META-INF/cxf/cxf-extension-http.xml]
Dec 5, 2010 5:17:09 PM
org.springframework.beans.factory.xml.XmlBeanDefinitionReader
loadBeanDefinitions
INFO: Loading XML bean definitions from class path resource
[META-INF/cxf/cxf-extension-soap.xml]
Dec 5, 2010 5:17:09 PM
org.springframework.beans.factory.xml.XmlBeanDefinitionReader
loadBeanDefinitions
INFO: Loading XML bean definitions from class path resource
[META-INF/cxf/cxf-extension-jaxws.xml]
Dec 5, 2010 5:17:09 PM
org.springframework.beans.factory.xml.XmlBeanDefinitionReader
loadBeanDefinitions
INFO: Loading XML bean definitions from class path resource
[META-INF/cxf/cxf-extension-http.xml]


Dec 5, 2010 5:17:10 PM
org.apache.cxf.service.factory.ReflectionServiceFactoryBean
buildServiceFromClass
INFO: Creating Service
{http://cas.service.hnfs.healthnet.com/}CodeLookupUtilityServiceService from
class 
     com.foo.service.cas.CodeLookupUtilityService
178215 [141.177.38.99 [1291598227289] GET
/content/hnfs/home/tn/t3app/services/svceservice.html HTTP/1.1] WARN
org.apache.jackrabbit.classloader.DirectoryClassPathEntry - 
    getResource: problem accessing the resource
[/schemas/wsdl/ws-addr-wsdl.xsd, /var/classes/] 
    below javax.jcr.RepositoryException: invalid
path:/var/classes//schemas/wsdl/ws-addr-wsdl.xsd

178218 [141.177.38.99 [1291598227289] GET
/content/hnfs/home/tn/t3app/services/svceservice.html HTTP/1.1] 
    WARN org.apache.jackrabbit.classloader.DirectoryClassPathEntry -
getResource: problem accessing the resource [/schemas/wsdl/ws-addr.xsd,
/var/classes/] below javax.jcr.RepositoryException: invalid
path:/var/classes//schemas/wsdl/ws-addr.xsd

178225 [141.177.38.99 [1291598227289] GET
/content/hnfs/home/tn/t3app/services/svceservice.html HTTP/1.1] 
               WARN
org.apache.jackrabbit.classloader.DirectoryClassPathEntry - 
               getResource: problem accessing the resource
[/schemas/wsdl/wsrm.xsd, /var/classes/] below javax.jcr.RepositoryException: 
               invalid path:/var/classes//schemas/wsdl/wsrm.xsd

javax.xml.ws.WebServiceException: Could not find wsdl:binding operation info
for web method getLookupCodes.
        at
org.apache.cxf.jaxws.JaxWsClientProxy.invoke(JaxWsClientProxy.java:113)
        at $Proxy34.getLookupCodes(Unknown Source)
        at
com.healthnet.ws.osgi.subsystem.internal.WebServiceProxyImpl.getSponsorId(WebServiceProxyImpl.java:72)

-- 
View this message in context: 
http://cxf.547215.n5.nabble.com/OSGi-bug-javax-xml-ws-WebServiceException-Could-not-find-wsdl-binding-operation-tp3293584p3293584.html
Sent from the cxf-user mailing list archive at Nabble.com.

Reply via email to