Hi guys,
Ole from the soapui team here.. I checked this and it's a bug in soapUI
which will be fixed in next snapshot.. the workaround is to provide the
encodingStyle attribute for the body in the binding for the Subscribe
operation:
<wsdl:operation name="Subscribe">
<wsdl-soap:operation
soapAction="http://ws.apache.org/muse/test/wsrf/Subscribe"; />
<wsdl:input>
<wsdl-soap:body use="encoded" />
</wsdl:input>
should be
<wsdl:operation name="Subscribe">
<wsdl-soap:operation
soapAction="http://ws.apache.org/muse/test/wsrf/Subscribe"; />
<wsdl:input>
<wsdl-soap:body use="encoded"
encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"/>
</wsdl:input>
this should be fixed in all input/output/faults that specify use="encoded"
without specifying the encodingStyle..
(most of them are ok)
the generated request for the Subscribe operation is then:
<soapenv:Envelope xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
xmlns:xsd="http://www.w3.org/2001/XMLSchema";
xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/";
xmlns:b="http://docs.oasis-open.org/wsn/b-2";>
<soapenv:Header/>
<soapenv:Body>
<b:Subscribe>
<ConsumerReference xsi:type="add:EndpointReferenceType"
xmlns:add="http://www.w3.org/2005/08/addressing";>
<Address xsi:type="add:AttributedURIType">?</Address>
<!--Optional:-->
<ReferenceParameters xsi:type="add:ReferenceParametersType">
<!--You may enter ANY elements at this point-->
</ReferenceParameters>
<!--Optional:-->
<Metadata xsi:type="add:MetadataType">
<!--You may enter ANY elements at this point-->
</Metadata>
<!--You may enter ANY elements at this point-->
</ConsumerReference>
<!--Optional:-->
<Filter xsi:type="b:FilterType">
<!--You may enter ANY elements at this point-->
</Filter>
<!--Optional:-->
<InitialTerminationTime
xsi:type="b:AbsoluteOrRelativeTimeType">?</InitialTerminationTime>
<!--Optional:-->
<SubscriptionPolicy>
<!--You may enter ANY elements at this point-->
</SubscriptionPolicy>
<!--You may enter ANY elements at this point-->
</b:Subscribe>
</soapenv:Body>
</soapenv:Envelope>
regards!
/Ole
Ramesh Gurunathan wrote:
>
> SOAPUI basically lists all the port type operations. I can choose the
> operation I want to invoke. It will compose a SOAP message and places
> '?' for all the mandatory/optional elements to allow user to enter
> values. For the 'Subscribe' operation, it didn't show any SOAP message
> at all. The input panel was empty. So I thought there must be
> something wrong in the way WSDL defines the web service. When I tried
> with XML Spy, it was even worse. It just crashed.
>
> I looked at the WSDL (WsResource.wsdl), it had several levels of
> imports. Import within import. It may be technically correct, but
> tools are not robust enough yet?
>
> On 12/8/06, Daniel Jemiolo <[EMAIL PROTECTED]> wrote:
>> The WSDL has the standard WSN WSDL content, so I doubt its invalid WSDL
>> content... how does soapUI make the request? Do you have a chance to
>> enter values for the parameters in the request? Subscribe() has a number
>> of parameters, so I'd be interested to know what values you provided and
>> whether soapUI seems to be ignoring them or not.
>>
>> Dan
>>
>>
>>
>> "Ramesh Gurunathan" <[EMAIL PROTECTED]> wrote on 12/08/2006
>> 05:04:37 AM:
>>
>> > Hi,
>> >
>> > My application clients are non-java applications and so they can't use
>> > muse API for notification subscription requests. They truly rely on
>> > SOAP for communication with the notification server. WSDL is the only
>> > contract between the (notification) server and the clients.
>> >
>> > So I decided to generate a sample SOAP message for Topic subscription.
>> > This will give a heads-up to the application client developers.
>> >
>> > I tried to load the WsResource.wsdl file of wsn-producer sample in the
>> > XML Spy editor, it crashed. I thought it could be due to a bug in XML
>> > Spy, then I decided to load it in SOAP UI (1.6 final) tool, it
>> > successfully loaded the wsdl and all it's import files, but when
>> > generating a SOAP request for 'Subscribe' operation, it only produced
>> > an empty soap request.
>> >
>> > Any ideas what could be wrong? Is there anything wrong in the WSDL?
>> >
>> > Appreciate your advice.
>> >
>> > Ramesh
>> >
>> > ---------------------------------------------------------------------
>> > To unsubscribe, e-mail: [EMAIL PROTECTED]
>> > For additional commands, e-mail: [EMAIL PROTECTED]
>> >
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: [EMAIL PROTECTED]
>> For additional commands, e-mail: [EMAIL PROTECTED]
>>
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
>
--
View this message in context:
http://www.nabble.com/Unable-to-load-wsn-producer%5CWsResource.wsdl-tf2779718.html#a7760593
Sent from the Muse User mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
