Skip to main content
Announcements
New: No-code data prep in Qlik Cloud Analytics™ TAKE A TOUR
cancel
Showing results for 
Search instead for 
Did you mean: 
Anonymous
Not applicable

wsdl-first web service: not invokable and malformed wsdl

Hello,
I am trying to deploy an OSGi-fied version of the CXF wsdl-first CustomerService example into TSF. I Build both, client and server, from wsdl, implemented some testing logic in the stubs and added the following Manifest and beans.xml to the server bundle:

Manifest-Version: 1.0
Ant-Version: Apache Ant 1.8.1
Created-By: 1.6.0_20-b02 (Sun Microsystems Inc.)
Main-Class: com.example.customerservice.CustomerService_CustomerServic
ePort_Server
Bundle-ManifestVersion: 2
Bundle-Name: CustomerServiceServer
Bundle-SymbolicName: CustomerServiceServer
Bundle-Version: 0.9.9.alpha
Require-Bundle: org.apache.cxf.bundle,org.springframework.bean

 



xmlns="http://www.springframework.org/schema/beans"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:jaxws="http://cxf.apache.org/jaxws"
xsi:schemaLocation="http://www.springframework.org/schema/beans
http://ww


To see the whole post, download it here
Labels (3)
3 Replies
dkulp
Contributor
Contributor

I'm really not sure what would cause that.
I just converted the service part of the wsdl_first sample into an OSGi bundle and stuck the result at:
http://dankulp.com/talend/wsdl_first_osgi.tar.gz
If I install/start that bundle and then use "mvn -Pclient" in the normal wsdl_first directory to run the standard client, it seems to work fine. Can you take a look at that and maybe provide a clue as to what may be different between what I did and what you did?
Thanks!
Dan
Anonymous
Not applicable
Author

Dear Dan,
thanks for your help.
I needed to specify some packages to import, at least:
Import-Package: javax.annotation,javax.jws,javax.xml.bind,javax.xml.bind.ann
otation,javax.xml.bind.annotation.adapters,javax.xml.namespace,javax.
xml.ws,org.apache.cxf.endpoint,org.apache.cxf.interceptor,org.apache.
cxf.jaxws,org.apache.cxf.tools.common,org.springframework.context.sup
port;version="3.0"

I only looked at the pom.xml (not the generated manifest.mf) of the jaxws-jms-spec example and got the impression, that it was sufficient to declare org.apache.cxf.bundle and org.springframework.bean as requiered bundles. Since I wrote my manifest per hand, the needed imports were not added by some tool like the maven-bundle-plugin.
Best Regards,
Markus
dkulp
Contributor
Contributor

Thanks for the follow up. As a maven user, I keep forgetting people actually try and maintain MANIFEST entries by hand. 🙂
Dan