I don't think that it might help to migrate to rpc-encoded/rpc-literal.I
have no clue about the service parameters
and data types that you are using.If your service uses "value type
objects" (such as Complex Java Beans /Arrays/Enums),DII may not work.
Also,if you are using a "Call" Object and configuring things manually in
your code,pls make sure that the TypeMapping
and TypeMappingRegistry are all fine(they have proper mappings).Its
quite a lot of work to do ,if you want to use DII.
-Ravi
William Lee wrote:
>Thanks for your prompt response.
>
>Do you think it might help if I migrate my service to
>rpc-literal/rpc-encoded would make using DII with JAX-RPC SI easier?
>
>William
>
>--- response to
>Date: Thu, 12 Feb 2004 11:52:13 +0530
>From: Ravikiran <Venkata-Naga.Ravikiran_at_sun.com>
>Content-type: text/plain; charset=ISO-8859-1; format=flowed
>Subject: IllegalArgumentException in LiteralObjectSerializerBase
>
>
>
>DII with doc-literal might have some issues.The specific exception is
>thrown as the DynamicSerializer was not able to find out a type mapping
>for some parameter that it is going to serialize.Try using static stubs
>to avoid these issues.
>
>-Ravi
>
>
>--- William Lee @ London e-Science Centre, Imperial College London --
>A: Room 348, Department of Computing, Imperial College London, Huxley
>Building, South Kensington campus, London SW6 2BZ, UK
>E: wwhl_at_doc.ic.ac.uk | william_at_imageunion.com
>W: www.lesc.ic.ac.uk | www.imageunion.com
>P: +44(0)20 7594 8251
>F: +44(0)20 7581 8024
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>---------------------------------------------------------------------
>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