Workshop IDE can not create CTRL from WSDL file

Question

Hi everybody,
For the evualtion of the Workshop IDE that comes with WLS 7.0 beta, I'm developing
a web service (via this IDE) which must interoperate with another web service
implemented with the help of another tool. I got the corresponding WSDL of this
"outside" web service (see attachement), and when I want to generate the corresponding
CTRL (via Add Service Control), I get the following error:
Error: Could not find operation 'sayHello' in portType ''
Prescription: The operation you are trying to bind was not found among the declared
operations. Please check your <portType> sections.
I do not have a lot of experience with WSDL files and its specification, but I
compared this file with another WSDL files that work with WORKSHOP IDE, and I
do not see difference between these files and the file that does not work. Moreover
the IDE error says that my service 'sayHello' can not be find inside the 'portType'
tags, but if you have a look at the WSDL file, you will see that is not true ?!?!?
Can somebody help me please?
Have a nice day
Vincent

Answer 1

Vincent,
What is happening is that the type attribute on the binding tag must match
both the targetnamespace and the name of the portType name attribute. Yours
do match in basename only. When parsing the WSDL file what we do is put the
name attributes of the portType, service and binding tags into the
targetNamespace of the WSDL and then we expect the references to these names
to also be resolved to that namespace.
In the case of your WSDL, your targetNamespace is
http://localhost:8000/HelloWorldApp/servlet/rpcrouter and the type attribute
on the binding attribute just references HelloWorldServicePort which means
it will use the default namespace of http://schemas.xmlsoap.org/wsdl which
is, of course, different than the targetNamespace.
To fixup the WSDL I would recommend you just define a new namespace at the
top of the WSDL file that matches the targetNamespace attribute and then use
that prefix in the text value of the attribute used to reference that name.
Yes, we do need to do some better parser/error messages to help identify
this :)
Here is one way that I have done to fixup your WSDL and Workshop does pull
it in and expose the methods correctly:
<?xml version='1.0'?>
<definitions name='HelloWorldService'
xmlns:soap='http://schemas.xmlsoap.org/wsdl/soap/'
xmlns:xsd='http://www.w3.org/2001/XMLSchema'
xmlns='http://schemas.xmlsoap.org/wsdl/'
xmlns:SOAP-ENC='http://schemas.xmlsoap.org/soap/encoding/'
targetNamespace='http://localhost:8000/HelloWorldApp/servlet/rpcrouter'
xmlns:test='http://localhost:8000/HelloWorldApp/servlet/rpcrouter'
xmlns:xsd1='http://localhost:8000/HelloWorldApp/servlet/rpcrouter/schema'>
<types>
<xsd:schema
targetNamespace='http://localhost:8000/HelloWorldApp/servlet/rpcrouter/schem
a'>
<xsd:simpleType name="java.lang.Integer"><xsd:restriction
base="xsd:int"/></xsd:simpleType>
<xsd:simpleType name="java.lang.Short"><xsd:restriction
base="xsd:short"/></xsd:simpleType>
<xsd:simpleType name="java.lang.Long"><xsd:restriction base="xsd:long"
/></xsd:simpleType>
<xsd:simpleType name="java.lang.Double"><xsd:restriction
base="xsd:double"/></xsd:simpleType>
<xsd:simpleType name="java.lang.Float"><xsd:restriction
base="xsd:float"/></xsd:simpleType>
<xsd:simpleType name="java.lang.Boolean"><xsd:restriction
base="xsd:boolean"/></xsd:simpleType>
<xsd:simpleType name="java.lang.Character"><xsd:restriction
base="xsd:string"/></xsd:simpleType>
<xsd:simpleType name="java.lang.String"><xsd:restriction
base="xsd:string"/></xsd:simpleType>
<xsd:simpleType name="java.lang.StringBuffer"><xsd:restriction
base="xsd:string"/></xsd:simpleType>
<xsd:simpleType name="java.lang.Byte"><xsd:restriction
base="xsd:byte"/></xsd:simpleType>
<xsd:simpleType name="char_lb_rb"><xsd:restriction
base="xsd:string"/></xsd:simpleType>
<xsd:simpleType name="char"><xsd:restriction
base="xsd:string"/></xsd:simpleType>
</xsd:schema>
</types>
<message name='sayHelloInput'>
<part name='message' type='xsd:string'/>
</message>
<message name='sayHelloOutput'>
<part name='result' type='xsd:string'/>
</message>
<portType name='HelloWorldServicePort'>
<operation name='sayHello'>
<input message='test:sayHelloInput'/>
<output message='test:sayHelloOutput'/>
</operation>
</portType>
<binding name='HelloWorldServiceBinding'
type='test:HelloWorldServicePort'>
<soap:binding style='rpc'
transport='http://schemas.xmlsoap.org/soap/http'/>
<operation name='sayHello'>
<soap:operation
soapAction='http://localhost:8000/HelloWorldApp/servlet/rpcrouter/sayHello'/
>
<input>
<soap:body use='encoded' namespace='urn:HelloWorldService'
encodingStyle='http://schemas.xmlsoap.org/soap/encoding/'/>
</input>
<output>
<soap:body use='encoded' namespace='urn:HelloWorldService'
encodingStyle='http://schemas.xmlsoap.org/soap/encoding/'/>
</output>
</operation>
</binding>
<service name='HelloWorldService'>
<port name='HelloWorldServicePort'
binding='test:HelloWorldServiceBinding'>
<soap:address
location='http://localhost:8000/HelloWorldApp/servlet/rpcrouter'/>
</port>
</service>
</definitions>
Thanks,
Art
"Vincent Ducret" <[email protected]> wrote in message
news:[email protected]...
>
Thanks for your answer, but I do not understand it, and also yoursuggestion.
>
According to WSDL specification, the 'type' attribute of a 'binding' tagmust
reference (bind to) an exisiting 'portType' tag. And it's the case here,no? I.e.
we have a 'portType' tag called HelloWorldServicePort, which is referencedby
the 'binding' tag named HelloWorldServiceBinding via its 'type' attribute:'HelloWorldServicePort'.
>
Where is the problem ?
Thanks a lot
Thanks for your help