users@jax-rpc.java.net

RE: -f:wsi

From: Kevin Jones <kevinj_at_develop.com>
Date: Fri, 6 Aug 2004 10:11:15 +0100

OK,

so the binding is rpc-literal, but I can achieve that with -f:rpcliteral
(BTW, you really should be using doc/literal which you turn in with the
-f:documentliteral feature if you want the best shot at interoperability)

wscompile -help says

"wsi enable WSI-Basic Profile features (for
                           document/literal and rpc/literal)"


What basic profile features does it enable?


Kevin Jones
http://kevinj.develop.com
 

> -----Original Message-----
> From: Merten Schumann [mailto:Merten.Schumann_at_asg.com]
> Sent: 06 August 2004 09:09
> To: users_at_jax-rpc.dev.java.net
> Subject: RE: -f:wsi
>
> I'm trying to assemble a web service with both, WSI compliant
> and non compliant WSDL interface, so I have generated both WSDL files:
>
> non-WSI:
> <?xml version="1.0" encoding="UTF-8"?>
> <definitions name="WuergService" targetNamespace="urn:Foo"
> xmlns:tns="urn:Foo" xmlns="http://schemas.xmlsoap.org/wsdl/"
> xmlns:xsd="http://www.w3.org/2001/XMLSchema"
> xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/">
> <types/>
> <message name="Wuerg_sayHello">
> <part name="String_1" type="xsd:string"/></message>
> <message name="Wuerg_sayHelloResponse">
> <part name="result" type="xsd:string"/></message>
> <portType name="Wuerg">
> <operation name="sayHello" parameterOrder="String_1">
> <input message="tns:Wuerg_sayHello"/>
> <output
> message="tns:Wuerg_sayHelloResponse"/></operation></portType>
> <binding name="WuergBinding" type="tns:Wuerg">
> <soap:binding transport="http://schemas.xmlsoap.org/soap/http"
> style="rpc"/>
> <operation name="sayHello">
> <soap:operation soapAction=""/>
> <input>
> <soap:body
> encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"
> use="encoded"
> namespace="urn:Foo"/></input>
> <output>
> <soap:body
> encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"
> use="encoded"
> namespace="urn:Foo"/></output></operation></binding>
> <service name="WuergService">
> <port name="WuergPort" binding="tns:WuergBinding">
> <soap:address
> location="REPLACE_WITH_ACTUAL_URL"/></port></service></definitions>
>
>
> WSI:
> <?xml version="1.0" encoding="UTF-8"?>
> <definitions name="WuergService" targetNamespace="urn:Foo"
> xmlns:tns="urn:Foo" xmlns="http://schemas.xmlsoap.org/wsdl/"
> xmlns:xsd="http://www.w3.org/2001/XMLSchema"
> xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/">
> <types/>
> <message name="Wuerg_sayHello">
> <part name="String_1" type="xsd:string"/></message>
> <message name="Wuerg_sayHelloResponse">
> <part name="result" type="xsd:string"/></message>
> <portType name="Wuerg">
> <operation name="sayHello" parameterOrder="String_1">
> <input message="tns:Wuerg_sayHello"/>
> <output
> message="tns:Wuerg_sayHelloResponse"/></operation></portType>
> <binding name="WuergBinding" type="tns:Wuerg">
> <soap:binding transport="http://schemas.xmlsoap.org/soap/http"
> style="rpc"/>
> <operation name="sayHello">
> <soap:operation soapAction=""/>
> <input>
> <soap:body use="literal" namespace="urn:Foo"/></input>
> <output>
> <soap:body use="literal"
> namespace="urn:Foo"/></output></operation></binding>
> <service name="WuergService">
> <port name="WuergPort" binding="tns:WuergBinding">
> <soap:address
> location="REPLACE_WITH_ACTUAL_URL"/></port></service></definitions>
>
> Have a look for the <binding> element for the difference ...
> It's really important, for example, old MS SOAP Toolkit 3.0
> cannot work with the WSI compliant WSDL, I guess .NET stuff can.
>
> cu
> Merten
>
> > -----Original Message-----
> > From: Kevin Jones [mailto:kevinj_at_develop.com]
> > Sent: Friday, August 06, 2004 10:04 AM
> > To: users_at_jax-rpc.dev.java.net
> > Subject: -f:wsi
> >
> > What exactly does the -wsi feature do? I know about the WSI and the
> > Base Profile etc, I'm just wondering exactly what this flag
> brings to
> > the party?
> >
> > Thanks,
> >
> > Kevin Jones
> > http://kevinj.develop.com
> >
> >
> >
> ---------------------------------------------------------------------
> > To unsubscribe, e-mail: users-unsubscribe_at_jax-rpc.dev.java.net
> > For additional commands, e-mail: users-help_at_jax-rpc.dev.java.net
> >
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe_at_jax-rpc.dev.java.net
> For additional commands, e-mail: users-help_at_jax-rpc.dev.java.net
>
>


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe_at_jax-rpc.dev.java.net
For additional commands, e-mail: users-help_at_jax-rpc.dev.java.net