OK Jim,
so I'd say on server side you can use this @DataBinding annotation and
forget about the servlet parameters stuff. If the user wants more
control on the databinding, he's free to provide his own jbossws-cxf.xml
file instead of leveraging the generated one.
For using the annotation we need to move to Apache CXF 2.2.4, which btw
is already scheduled, see. JBWS-2780. I'm doing that (the update)
tomorrow if the artifacts are available on central.
If you're blocked, in the mean time you can take a look at other issues
you already have for 3.2.1 release.
Cheers
Alessio
Daniel Kulp wrote:
Kind of already done. :-)
On trunk and 2.2.4, we have a @DataBinding annotation that takes the Class of
the databinding. Doesn't really allow configuration though due to
limitations for annotations. :-( It does allow a "ref" attribute that
can point to a bean name in the spring config instead though.
The other thing is the wsdl2java tool now outputs that annotations -db
xmlbeans and -db sdo. Thus, the generated code works correctly now without
config.
Dan
On Tue October 13 2009 4:31:21 am Alessio Soldano wrote:
> Hi there,
> we're currently looking at ways for programmatically configuring the
> databinding (Aegis for instance) different from the default JAXB one
> (thus without setting it in the cxf.xml config file).
> Jim already took a look at this and we are thinking about contributing
> something for allowing the databinding to be specified using annotations
> (unless there's already something equivalent for doing this).
> What do you think about this?
> I'd see different approaches here, either using the already existing
> @Feature or adding new annotation.
> Cheers
> Alessio
>
>
--
Alessio Soldano
Web Service Lead, JBoss