As part of the promotion of the Axis project to a top level project,
we have decided to create separate mailing lists for Axis 1 and Axis2.
For all Axis 1 related questions please subscribe and post to
[email protected]. Thanks!

Andreas

On Thu, Nov 4, 2010 at 11:41, RaphaelJ <[email protected]> wrote:
>
>
> Hi Folks,
>
> I am migrating a SOAP web service to JDK1.5. I have took advantage of native
> java enums in the new code. For some reasons, I'm stuck with Axis 1.2 and it
> does not natively support JDK5 "enums".
>
> I have found a tutorial on how to implement custom a serialization /
> deserialization for java enums:
> http://www.developpez.net/forums/d236564/java/developpement-web-java/web-services/utiliser-type-enum-jdk5-axis/
> http://www.developpez.net/forums/d236564/java/developpement-web-java/web-services/utiliser-type-enum-jdk5-axis/
> (in French).
>
> I have been able to successfully register those custom serialization
> handlers on the server side via the use of "typeMapping" elements in the
> ".wsdd" file.
>
> However, I can't figure out how to register the same classes on the client
> side, as I don' think I can use a ".wssd" file here.
>
> The
> http://ws.apache.org/axis/java/user-guide.html#WhenBeansAreNotEnoughCustomSerialization
> corresponding part in the user-guide  does not help either, since it only
> explains the "wsdd" file configuration on server side. Nothing on the client
> side.
>
> Any help would be appreciated.
>
> Many thanks in advance,
> Raphael
>
> --
> View this message in context: 
> http://old.nabble.com/Custom-serialization-of-JDK5-Enum-in-Axis-1.2-on-client-side-tp30130750p30130750.html
> Sent from the Axis - User mailing list archive at Nabble.com.
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [email protected]
> For additional commands, e-mail: [email protected]
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to