You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cxf.apache.org by "Matt Inger (JIRA)" <ji...@apache.org> on 2010/02/18 00:03:27 UTC
[jira] Issue Comment Edited: (DOSGI-55) JAX-WS Frontend generating
WSDL with no operations or types
[ https://issues.apache.org/jira/browse/DOSGI-55?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12835026#action_12835026 ]
Matt Inger edited comment on DOSGI-55 at 2/17/10 11:03 PM:
-----------------------------------------------------------
Removing the geronimo-ws jar seems to eventually have helped, as I can now use jax-ws annotations and generate a proper wsdl , Though I do see a wierdness in the examination of the exports of the org.eclipse.osgi bundle. I will say that I don't want this defect closed because I had to do a lot of wrangling, including modifying and compiling cxf-2.2.4 and dosgi on my own in order to get this to work. I think that dosgi either needs to be updated to work with the latest spring and spring-dm versions, and work with dmServer as well.
javax.jws 0.0.0
javax.jws 2.0.0
imported by com.fiberlink.service.widget.widget-web-service-impl 1.0.0.SNAPSHOT [104]
imported by com.fiberlink.service.widget.widget-web-service-api 1.0.0.SNAPSHOT [103]
imported by com.springsource.server.admin.web 2.0.0.RELEASE [66]
imported by com.springsource.server.splash 2.0.0.RELEASE [68]
imported by org.springframework.web 3.0.0.RELEASE [44]
imported by org.apache.cxf.bundle-minimal 2.2.5 [94]
imported by com.springsource.server.repository.hosted-2.0.0.RELEASE-com.springsource.server.repository.hosted.web 2.0.0.RELEASE [58]
javax.jws.soap 0.0.0
javax.jws.soap 2.0.0
imported by com.fiberlink.service.widget.widget-web-service-impl 1.0.0.SNAPSHOT [104]
imported by com.fiberlink.service.widget.widget-web-service-api 1.0.0.SNAPSHOT [103]
imported by com.springsource.server.admin.web 2.0.0.RELEASE [66]
imported by com.springsource.server.splash 2.0.0.RELEASE [68]
imported by org.apache.cxf.bundle-minimal 2.2.5 [94]
imported by com.springsource.server.repository.hosted-2.0.0.RELEASE-com.springsource.server.repository.hosted.web 2.0.0.RELEASE [58]
The changes I had to make in addition to removing the geronimo-ws bundle from the container:
cxf-2.2.5:
{code}
Index: distribution/bundle/minimal/pom.xml
===================================================================
--- distribution/bundle/minimal/pom.xml (revision 910806)
+++ distribution/bundle/minimal/pom.xml (working copy)
@@ -173,6 +173,7 @@
antlr*;resolution:=optional,
com.ibm*;resolution:=optional,
com.sun*;resolution:=optional,
+ com.sun.xml.bind.v2;resolution:=optional,
javax.jms*;resolution:=optional,
javax.ws.rs*;resolution:=optional,
com.ctc.wstx.msv*;resolution:=optional,
Index: parent/pom.xml
===================================================================
--- parent/pom.xml (revision 910806)
+++ parent/pom.xml (working copy)
@@ -57,7 +57,10 @@
<msv.version>2009.1</msv.version>
<rhino.version>1.7R1</rhino.version>
<saaj.version>1.3</saaj.version>
+<!--
<spring.version>2.5.5</spring.version>
+-->
+ <spring.version>3.0.0.RELEASE</spring.version>
<spring.mock>spring-test</spring.mock>
<stax.impl.groupId>org.codehaus.woodstox</stax.impl.groupId>
<stax.impl.artifactId>wstx-asl</stax.impl.artifactId>
{code}
dosgi_trunk:
{code}
Index: parent/pom.xml
===================================================================
--- parent/pom.xml (revision 910791)
+++ parent/pom.xml (working copy)
@@ -20,8 +20,12 @@
<properties>
<cxf.version>2.2.5</cxf.version>
<felix.version>1.8.0</felix.version>
+<!--
<spring.version>2.5.6</spring.version>
<spring.osgi.version>1.2.0</spring.osgi.version>
+-->
+ <spring.version>3.0.0.RELEASE</spring.version>
+ <spring.osgi.version>1.2.1</spring.osgi.version>
<zookeeper.version>3.2.1</zookeeper.version>
<remote.service.admin.interfaces.version>1.0.0</remote.service.admin.interfaces.version>
{code}
was (Author: mattinger):
Removing the geronimo-ws jar does not seem to help at all. It still seems to thing there's a 2.0.0 package installed, but when i try the "package examine javax.jws 2.0.0" command,
it says there's no package with that version, evern though that shows up with the "package list" command.
> JAX-WS Frontend generating WSDL with no operations or types
> -----------------------------------------------------------
>
> Key: DOSGI-55
> URL: https://issues.apache.org/jira/browse/DOSGI-55
> Project: CXF Distributed OSGi
> Issue Type: Bug
> Affects Versions: 1.1
> Reporter: Matt Inger
>
> I've setup a web service interface and implementation with the proper annotations (@WebService, @WebMethod, @WebParam) and so forth, and deployed the dosgi singlebundle distribution into spring dmServer 2.0. When setup for the simple frontend with jaxb bindings, I get a somewhat ok result, though the generated wsdl exceptions a message payload like this:
> {code}<ns1:addWidget><widgetData>...<widgetData></ns1:addWidget>{code}
> Obviously this is not optimal, so i decided to switch to JAX-WS, and added the appropriate package imports in my manifest:
> {code}
> @WebService
> public interface WidgetService {
> @WebMethod
> void addWidget(@WebParam(name="widgetData") WidgetData widgetData);
> }
> {code}
> {code}
> <osgi.import.package>
> javax.jws,
> javax.jws.soap,
> javax.xml.bind.annotation,
> javax.xml.bind.annotation.adapters,
> ...
> </osgi.import.package>
> {code}
> and then set the front end to use jaxws:
> {code}
> <osgi:service ref="WidgetWebService" interface="com.fiberlink.service.widget.web.api.WidgetWebService">
> <osgi:service-properties>
> <entry key="service.exported.interfaces" value="com.fiberlink.service.widget.web.api.WidgetWebService" />
> <entry key="service.exported.configs" value="org.apache.cxf.ws" />
> <entry key="org.apache.cxf.ws.frontend" value="jaxws" />
> <entry key="org.apache.cxf.ws.databinding" value="jaxb" />
> <entry key="org.apache.cxf.ws.address" value="http://localhost:9090/widget" />
> </osgi:service-properties>
> </osgi:service>
> {code}
> I would have expected a proper WSDL to be generated which wanted a payload like this:
> {code}<ns1:addWidget><widgetData>...<widgetData></ns1:addWidget>{code}
> However, what I got from the WSDL was this. Posts I have googled on indicated there might be something wrong with singlebundle distribution, but the links to the solution are expired, and i've had no luck getting the multibundle distribution working. Everytime I try to deploy a webservice using the multi-bundle distro, it never ends up deploying anything on the requested port #. Same with the 1.2 SNAPSHOT version as well. Seems I'm running into roadblocks everywhere.
> {code}
> <wsdl:definitions name="WidgetWebServiceService" targetNamespace="http://api.web.widget.service.fiberlink.com/" xmlns:ns1="http://schemas.xmlsoap.org/soap/http" xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/" xmlns:tns="http://api.web.widget.service.fiberlink.com/" xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/" xmlns:xsd="http://www.w3.org/2001/XMLSchema">
> <wsdl:portType name="WidgetWebService">
> </wsdl:portType>
> <wsdl:binding name="WidgetWebServiceServiceSoapBinding" type="tns:WidgetWebService">
> <soap:binding style="document" transport="http://schemas.xmlsoap.org/soap/http" />
> </wsdl:binding>
> <wsdl:service name="WidgetWebServiceService">
> <wsdl:port binding="tns:WidgetWebServiceServiceSoapBinding" name="WidgetWebServicePort">
> <soap:address location="http://localhost:9090/widget" />
> </wsdl:port>
> </wsdl:service>
> </wsdl:definitions>
> {code}
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.