axis-java-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From jayachandra <>
Subject Re: [Axis2] databinding setting [Re: [Axis2]Databinding Notes
Date Wed, 27 Jul 2005 06:07:24 GMT
Sounds reasonable to me for now.
Even in Axis 1.x if user wishes to ser and deser a particular part of
SOAP message as per a different data binding standard, he must have
the intelligentia to code the ser and deser factory for that data
binding mechanism. Castor serializer and deserializer factories are
some that got place inside axis code like that, if my understanding is

Ajith! btw, if the user writes his own extension... should he
necessarily add that one into axis2 code and recompile the whole thing
and use the resulting jar, or can he 'plug' that one through some
config XML file or command line option during code generation? The
later feature if present, would be very nice.

Thank you

On 7/27/05, Ajith Ranabahu <> wrote:
> Hi Alek,
> The idea in having pluggable data binding is not making it pluggable after
> code generation. Our view of 'pluggability' is at the code generation level.
> i.e. if the user needs his own data binding he has to engage that extension
> at the code generation stage to have the required code generated. Once the
> code is generated (say with XMLBeans) it stays the same and cannot be
> changed.
> If the user needs to have different data binding components at different
> parts of the SOAP Message he will have to have a highly customized codegen
> extension to do that.
> On 7/26/05, Aleksander Slominski <> wrote: 
> > if databinding selection happens during code generation how user can
> > plugin their own databinding? 
> > 
> > and in particular what about case when user wants to apply different
> > databinding for different parts of SOAP/XML message?
> > 
> > thanks,
> > 
> > alek
> > 
> > 
> -- 
> Ajith Ranabahu 

-- Jaya

View raw message