Re: Marking mandatory parameters with JAX-WS (was Marking optional parameters with JAX-WS)

2007-08-20 Thread Corey Puffalt
To: Corey Puffalt Cc: cxf-user@incubator.apache.org Subject: Re: Marking mandatory parameters with JAX-WS (was Marking optional parameters with JAX-WS) Honestly, I don't think there's an easy way. I just grepped through the JAX-WS spec and the JSR181 spec and neither spec mentions anything

RE: Marking mandatory parameters with JAX-WS (was Marking optional parameters with JAX-WS)

2007-08-20 Thread Benson Margulies
: [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] ] Sent: Friday, August 17, 2007 4:59 PM To: Corey Puffalt Cc: cxf-user@incubator.apache.org Subject: Re: Marking mandatory parameters with JAX-WS (was Marking optional parameters with JAX-WS) Honestly, I don't think there's an easy way. I just grepped

Re: Marking mandatory parameters with JAX-WS (was Marking optional parameters with JAX-WS)

2007-08-17 Thread Corey Puffalt
Daniel, Thanks for your reply. I should have been more explicit. I am using the default DOCUMENT style. Furthermore, I got my question completely backwards. :P The real question (given that all non-primitive parameters are marked minOccurs=0 as you mention below, how do I mark these parameters

Re: Marking mandatory parameters with JAX-WS (was Marking optional parameters with JAX-WS)

2007-08-17 Thread Daniel Kulp
Honestly, I don't think there's an easy way. I just grepped through the JAX-WS spec and the JSR181 spec and neither spec mentions anything about it. When we move to JAX-WS 2.1, we might be able to add support for @XmlElement(required=true). Right now, we don't support any of the JAXB