Re: Got "unexpected null value for literal data" exception in WSI compliant web service

From: Doug Kohlert <Doug.Kohlert_at_Sun.COM>
Date: Fri, 27 Aug 2004 13:12:19 -0700

Did you use the wsi option on the server and client or just server?

Merten Schumann wrote:

>I've created a simple JAX-RPC web service with Sun J2EE 1.4 RI and
>deployed the .war (including the JAX-RPC .jars from Sun J2EE 1.4) in
>Tomcat 5.0.27. I tried to create two variants: WSI compliant and not
>compliant (feature="wsi" to wscompile).
>There's a method
> String execute(String msg, String user, String password) throws
>in the service' interface. In a JAX-RPC client I invoke the method with
> execute("foo", null, null)
>This works fine in non-WSI compliant version, but with features="wsi"
>version I do get
>SEVERE: unexpected null value for literal data
>unexpected null value for literal data
>The method works if I call execute("foo", "", "").
>I do not use method overloading in the service interface, there's not
>another execute method.
>My question is, in WSI compliant way, is it not possible to hand over
>null values to web service methods???
>Thanx a lot!
> Merten
>To unsubscribe, e-mail:
>For additional commands, e-mail:

Doug Kohlert	
Sun MicroSystems, Inc.
To unsubscribe, e-mail:
For additional commands, e-mail: