Re: Problems with Dynamic Proxy Client against document/literal service

From: kathy walsh <Kathleen.Walsh_at_Sun.COM>
Date: Fri, 08 Oct 2004 10:33:58 -0400

Yes the dynamic proxy client does have problems, however,
non-wrapper style doc literal is not supported for the dynamic proxy-
Do you have the wsdl for the web service and the wscompile options that you
If so, I will test it out and see exactly what the problem is-
Yes, dynamic proxy clients will improve in the future-

Merten Schumann wrote:

>could it be that in JAX-RPC from Sun J2EE 1.4 RI a Dynamic Proxy Client
>has got problems with web services, when you use (wscompile) the
>document/literal mode?
>I do not mean the null value problem, I do know now that I cannot send
>there null as parameter, which is okay. I mean that my Dynamic Proxy
>Client (which is working fine against the web service, when I use
>non-wsi or rpc/literal mode for wscompile to generate the WSDL) fails
>for some strange reason against document/literal web service.
>I found before (I think Kathy told me that in a forum) that a Dynamic
>Proxy Client at the moment cannot really deal with complex types in a
>WSDL, and that's used in document / literal mode when I look at the WSDL
>... So, what I want is, if this could be the reason for my problem here,
>just a confirmation for this limitation of Dynamic Proxy Client at the
>moment (Kathy wrote that things will be improved) ... :-)
>This is the stack trace from server.log. The string "rums" is my
>parameter I'm trying to hand over to sayHello() method.
>pc.server|_ThreadID=17;|deserialization error: XML reader error:
>unexpected character content: "rums" deserialization error: XML reader
>error: unexpected character content: "rums" at
>( at
> at
> at
>) at
> at
>) at javax.servlet.http.HttpServlet.service(
>at javax.servlet.http.HttpServlet.service(
>I do use the 2004 Q4 Beta.
>Thank you!
> Merten
>To unsubscribe, e-mail:
>For additional commands, e-mail:

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