Re: DII client accessing .NET web service

From: Doug Kohlert <Doug.Kohlert_at_Sun.COM>
Date: Fri, 29 Oct 2004 09:56:21 -0700

The -f:wsi switch really does not do anything when starting from Java
except that it changes the default from rpc/encoded to
rpc/lit. To get doc/lit you must specify the -f:documentliteral option.

Ryan LeCompte wrote:

> Hello Kathy,
> Thank you for your response on the mailing list. I was actually able
> to solve this problem by setting the Call.SOAPACTION_URI_PROPERTY
> property correctly in my DII client application. However, I have
> another question that you may be able to help me out with. I'm a bit
> confused on when I should use the "-f:wsi" feature for the wscompile
> utility. I have been using the "-f:documentliteral" feature with
> wscompile to generate a WSDL file that will work with .NET, etc. Is it
> true that I only need "-f:wsi" if I want to generate JAX-RPC
> stubs/ties on the server-side that are WSI 1.0 compliant? It appears
> that the WSDL file that is produced when I use BOTH the -f:wsi and
> -f:documentliteral features is exactly the same as if I just use only
> the -f:documentliteral feature. I have been using only the
> -f:documentliteral (and not -f:wsi) for generating all of my
> client/server stubs/ties as well as the seralizers used by the DII
> client, and I haven't had any trouble accessing my JAX-RPC or .NET web
> service implementation that is based on the same WSDL produced by
> using just -f:documentliteral. Also, .NET doesn't complain that the
> generated WSDL isn't WSI 1.0 compliant. Is there something that I'm
> missing here? Am I okay with not using the -f:wsi feature? Note that
> I am also generating my server side web service implementation based
> on the generated WSDL from passing only -f:documentliteral to
> wscompile (as opposed to building the server side implementation from
> the Java endpoint interface).
> Thank you,
> -- Ryan
> ------------------------------------------------------------------------
> From: Ryan LeCompte []
> Sent: Wednesday, October 27, 2004 2:17 PM
> To: ''
> Subject: DII client accessing .NET web service
> Hello,
> I'm attempting to access a .NET web service using document/literal
> via a DII client in JAX-RPC (JWSDP 1.4). I'm using the
> Call.invokeOneWay() method, everything appears to be sent correctly
> (there are no exceptions thrown in any of the DII client code).
> However, the request never seems to get to the .NET side. Are there
> any known issues with DII and .NET? Note that the DII client works
> fine when the web service is implemented with JAX-RPC and running in
> the Tomcat 5.0 web container.
> Thank you,
> -- Ryan

To unsubscribe, e-mail:
For additional commands, e-mail: