WS service from WSDL

[cholou]

I tried to create a WS from a WSDL File and I got this error message at the dialog window:

"There is no service in specified WSDL File"

I don't know WHY it appears, because some days ago it run, but I've changed something in the WSDL (the file also was wrong, but was another mistake) and now Netbeans doesn't recognize it :S

this is the file:

[alex.brooker]

Simply by trying to validate the wsdl in NB 6.5 the transport has an error:

http://schemas.xmlsoap.org/org/http

should be http://schemas.xmlsoap.org/soap/http

so the line looks like this:

<soap:binding style="document" transport="http://schemas.xmlsoap.org/soap/http"/>

You have more errors in the wsdl as an Axis2 service from WSDL generation fails and errors are shown in the log. I will try and fix and then post back,

regards,

Alex[/quote]

[alex.brooker]

Hi,

some of the operations are rejected because they are 'notifications' that are one-way from the service back to the client, like on old c: int getId(){return 42;} You can have one-way from client to service or request response between the client and service.

According to the wsdl spec at http://www.w3.org/TR/wsdl we have the following quote: "Although the base WSDL structure supports bindings for these four transmission primitives, WSDL only defines bindings for the One-way and Request-response primitives. It is expected that specifications that define the protocols for Solicit-response or Notification would also include WSDL binding extensions that allow use of these primitives."

So notification is an extension, and hence not suprising that the tool doesn't support it. So you need to edit your operations in the following way: (I am not aware of an extension, another poster may be able to add this)

Finish creating your schema types in the wsdl:types section and then reference every operation to use them.

For example:
<wsdl:types>
<xsd:schema xmlns:ns="urn:prueba1" attributeFormDefault="qualified" elementFormDefault="qualified" targetNamespace="urn:prueba1">
<xsd:element name="id">
<xsd:complexType>
<xsd:sequence>
<xsd:element minOccurs="0" name="id" nillable="true" type="xsd:token"/>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
</xsd:schema>
</wsdl:types>

<wsdl:message name="doGetidResponse">
<wsdl:part name="parameters" element="typens:id"/>
</wsdl:message>
<wsdl:message name="doGetidRequest">
<wsdl:part name="parameters" element="typens:id"/>
</wsdl:message>

<wsdl:portType name="FutbolPort">
<wsdl:operation name="doGetid">
<wsdl:input message="typens:doGetidRequest" wsaw:Action="urn:doGetidRequest"/>
<wsdl:output message="typens:doGetidResponse" wsaw:Action="urn:doGetidResponse"/>
</wsdl:operation>
</wsdl:portType>

I suggest that you try and get the thing working with one single operation first, then add in your other operations a few at a time until they all work. Here is the stripped down wsdl I used from your example and this works for a "Service from WSDL" NB 6.5 for a Web Service using the metro stack:

<?xml version="1.0" encoding="UTF-8"?>
<wsdl:definitions xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/"
xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/"
xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/"
xmlns="http://schemas.xmlsoap.org/wsdl/"
xmlns:wsaw="http://www.w3.org/2006/05/addressing/wsdl"
xmlns:typens="urn:prueba1"
name="prueba1"
targetNamespace="urn:prueba1">
<wsdl:types>
<xsd:schema xmlns:ns="urn:prueba1" attributeFormDefault="qualified" elementFormDefault="qualified" targetNamespace="urn:prueba1">
<xsd:element name="id">
<xsd:complexType>
<xsd:sequence>
<xsd:element minOccurs="0" name="id" nillable="true" type="xsd:token"/>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
</xsd:schema>
</wsdl:types>

<wsdl:message name="doGetidResponse">
<wsdl:part name="parameters" element="typens:id"/>
</wsdl:message>
<wsdl:message name="doGetidRequest">
<wsdl:part name="parameters" element="typens:id"/>
</wsdl:message>

<wsdl:portType name="FutbolPort">
<wsdl:operation name="doGetid">
<wsdl:input message="typens:doGetidRequest" wsaw:Action="urn:doGetidRequest"/>
<wsdl:output message="typens:doGetidResponse" wsaw:Action="urn:doGetidResponse"/>
</wsdl:operation>
</wsdl:portType>

<wsdl:binding name="FutbolBinding" type="typens:FutbolPort">
<soap:binding style="document" transport="http://schemas.xmlsoap.org/soap/http"/>
<wsdl:operation name="doGetid">
<soap:operation soapAction="urn:doGetid" style="document"/>
<wsdl:input>
<soap:body use="literal"/>
</wsdl:input>
<wsdl:output>
<soap:body use="literal"/>
</wsdl:output>
</wsdl:operation>
</wsdl:binding>

<wsdl:service name="FutbolService">
<wsdl:port name="FutbolPort" binding="typens:FutbolBinding">
<soap:address location="http://localhost:8080/WebApplication3/NewWebServiceService"/>
</wsdl:port>
</wsdl:service>

</wsdl:definitions>

hope that helps

good luck,

Alex

[cholou]

thank you very much!!!
it's very helpful!
I must do it automatically because I'm developing a Java aplication that implements wsdl and the WSDL:TYPES are generated automatically too from Relaxer, then I can't change anything from the XSD.
thanks a lot!!

[cholou]

i got it!
thank you very much, the mistake was at the Binding, the style was "document" and that's not valid, i've changed it to "rpc". thank you very much again