cxf-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From nair_anoop <nair_an...@hotmail.com>
Subject Re: CXF / JAXB "Java first approach" - remove minOccurs="0"
Date Tue, 27 Jan 2009 19:15:18 GMT

It appears that this post describes the same:

http://www.nabble.com/minOccurs-nillable-on-a-parameter-td13147352.html#a13147352

Any insights on specifics of using the @RequestWrapper appraoch to
accomplish this?

Thanks.



nair_anoop wrote:
> 
> Hello -
> 
>      I am using the "Java first" approach (JAX-WS annotations on the SEI
> and SIB) to "automatically" generate the WSDL at run-time using CXF 2.1.3.
> 
>      Everything seems to be working mostly OK; my question is very similar
> (may be even identical!) to the one here
> -http://www.nabble.com/set-Default-minOccurs-and-nillable-Parameters-td15291545.html#a15291545
> 
>      Using the default JAXB binding, is there a way to remove the
> minOccurs=0 attribute from the resultant CXF-generated WSDL. I need this
> to better handle .Net / Java interop.
> 
>     This page (http://cwiki.apache.org/CXF20DOC/aegis-databinding.html)
> seems to describe this using the Aegis data binding, but I am using the
> default JAXB binding.
> 
> Thanks in advance.
> 

-- 
View this message in context: http://www.nabble.com/CXF---JAXB-%22Java-first-approach%22---remove-minOccurs%3D%220%22-tp21692084p21692319.html
Sent from the cxf-user mailing list archive at Nabble.com.


Mime
View raw message