see comment inline.
The
eric
Tony Opatha wrote:
By DEFAULT does not .NET/WSE based SOAP client send Doc/Lit request
in bare format rather than wrapped format.
.Net based client send requests that match the WSDL used when you generate the Web reference; there is no default for the client stub. The default is meaningfull when you want to deploy a service with .Net. With VS .Net 2003, by default, you get doc/lit/wrapped with the addNumbers cory is using.
Wrapped format is being discouraged and probably nopt very well documented
by Microsoft.
Why are you saying that wrapped is discouraged? I was under the impression that axis has also defined a wrapped style in WSDD.
Shouldn't .NET developers and AXIS applications that interface with .NET NOT use wrapped format since it is not compliant with WS-I??
Regarding WS-I, the part which is discouraged is the use of SOAPAction to dispatch messages. 'SOAPAction is purely a hint to processors' (see http://www.ws-i.org/Profiles/Basic/2003-06/BasicProfile-1.0-BdAD.html#refinement34343864).
*/Eric Rajkovic <[EMAIL PROTECTED]>/* wrote:
Cory,
With .Net, there are two flavors of document/literal requests you can generate. Once you have genereted the web reference, you can look at the generated code (Web Reference\com.travelnow.test\Reference.cs) to figure out which style is in use.
Look at the value for the ParameterStyle attribute (last parameter of System.Web.Services.Protocols.SoapDocumentMethodAttribute()).
It could be either System.Web.Services.Protocols.SoapParameterStyle.Bare or System.Web.Services.Protocols.SoapParameterStyle.Wrapped
In addition to your two examples, you have the following option for wire format. ******* DOC/LITERAL/Wrapped *******
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"; xmlns:xsd="http://www.w3.org/2001/XMLSchema";>
5 2
Without to see the WSDL generated in you case, it's hard to tell if your service is expected to get a wrapper with the operation name, is relying on the SOAPAction header attribute to perform the message dispatching or can dispatch messages based on the QName of the first element inside the .
hth, eric
Cory Wilkerson wrote:
> Sorry, premature send...that should read "com.travelnow.test" down there and not "com.corywilkerson...". Still an issue here -- just a typo when composing the email. > > ---------------- > > > Using 1.1 final, I've implemented a VERY rudimentary doc/literal service ! for the sake of testing doc/literal services. The following fails with a .NET client -- but, if I remove the style/use attributes -- the service executes without issue. This serivce does *not* throw a subclass of exception (which was an issue with an earlier doc/literal approach of mine) -- can anyone explain why this service isn't being invoked? > > --------------------------- > service implementation > --------------------------- > package com.corywilkerson.test; > > public class SomeService { > public int addNumbers(int x, int y) { > return x + y; > } > } > > ------------------------- > server-config.wsdd entry > ------------------------- > > > > ! > > > > ------------------------- > .NET client SOAPMessage via currentMessage/getSOAPPartAsString > ------------------------- > > ******* > DOC/LITERAL > ******* > > xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"; > xmlns:xsd="http://www.w3.org/2001/XMLSchema";> > > 5 > 2 > > > > ******* > ENCODED > ******* > > > xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/"; > xmlns:tns="http://dev.travelnow.com/services/TestService"; > xmlns:types="http://dev.travelnow.com/services/TestService/encodedT! ypes" > xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"; > xmlns:xsd="http://www.w3.org/2001/XMLSchema";> > > > > 5 > 2 > > > >
------------------------------------------------------------------------
Do you Yahoo!?
SBC Yahoo! DSL <http://pa.yahoo.com/*http://rd.yahoo.com/evt=1207/*http://promo.yahoo.com/sbc/> - Now only $29.95 per month!
