Actually ....
Switching to Aegis is massively simple.
I wrapped a +100 method legacy api pretty darn quickly with Aegis and
a few simple binding modifications (to get away from optional stuff)
/je
On Oct 13, 2010, at 7:17 PM, ericacm wrote:
>
> First off, congratulations to Dan and everyone in getting 2.3.0 out!
>
> Since it's out the first thing I wanted to test was one of my pet issues,
> required @WebParams.
>
> The JAX-WS 2.2 spec (section 3.6.2.1) says:
>
>> If a SEI’s method parameter or return type is annotated with @XmlElement,
>> that annotation is used for the wrapper bean properties. This can be used
>> to map corresponding XML schema element declaration’s attributes like
>> minOccurs, maxOccurs, and nillable etc.
>
> So I went and added @XmlElement(required=true) to a parameter to test. It
> turns out that you can't even add @XmlElement to a method parameter because
> it has @Target(value={FIELD,METHOD}). The compiler won't allow it.
>
> Has anyone else run into this issue? Will I have to bite the bullet and use
> one of the workarounds that have been mentioned?
> - Create a wrapper bean and use the @XmlElement there
> - Switch to Aegis
> - Use WSDL first
>
> Lots of work either way, not looking forward to it.
>
> Thanks,
> --
> View this message in context:
> http://cxf.547215.n5.nabble.com/Revisiting-required-WebParams-tp3211381p3211381.html
> Sent from the cxf-user mailing list archive at Nabble.com.
Johan Edstrom
j...@opennms.org
They that can give up essential liberty to purchase a little temporary safety,
deserve neither liberty nor safety.
Benjamin Franklin, Historical Review of Pennsylvania, 1759
