cxf-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Matt Inger (JIRA)" <>
Subject [jira] Commented: (DOSGI-55) JAX-WS Frontend generating WSDL with no operations or types
Date Tue, 09 Feb 2010 21:50:28 GMT


Matt Inger commented on DOSGI-55:

I've tried to use the 1.2-SNAPSHOT on dmServer 2.0.0.RELEASE, hoping maybe the issue would
be fixed in the 1.2-SNAPSHOT singlebundle distribution, but when I do that, I can't even get
the endpoint to come up at all.  The bundles all start up fine, but the endpoint itself never
gets exposed out.  I keep just getting 404 errors, with no clues in the servicibility log
as to why.

> JAX-WS Frontend generating WSDL with no operations or types
> -----------------------------------------------------------
>                 Key: DOSGI-55
>                 URL:
>             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="" />
>       <entry key="" value="jaxws" />
>       <entry key="" value="jaxb" />
>       <entry key="" 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=""
xmlns:ns1="" xmlns:soap=""
xmlns:tns="" xmlns:wsdl=""
>   <wsdl:portType name="WidgetWebService">
>   </wsdl:portType>
>   <wsdl:binding name="WidgetWebServiceServiceSoapBinding" type="tns:WidgetWebService">
>     <soap:binding style="document" transport=""
>   </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.

View raw message