This is a spec compliance issue. The DEFAULTS for this are
minOccurs=0. The nillable probably shouldn't be there.
In anycase, it IS controllable to some extent, but it's not exactly
easy. Basically, you would have to create a bean to represent the
request, annotate it poperly, and then add an @RequestWrapper
annotation to point at the bean. For the most part, if you don't
like the defaults, you need to do the bean thing to override the
defaults.
Dan
On Jun 25, 2008, at 4:19 PM, Landslide wrote:
Here is what I got from Axis2 forum. I just wonder if CXF has
already have a
better solution for this issue.
Thanks for any help.
==================================
At the moment what you can do is , generate a wsdl using Java2wsdl ,
then modified that to have minOccurs="1" and then put that into META-
INF
directory of your service archive , then Axis2 will shows up the wsdl
correctly. However the long term solution would be to create a JIRA so
that we will try to come up with some kind of way to specify those.
Thanks
Deepal
Hi,
/i am using the following definition in my service.xml/
<operation name="createInitial">
<messageReceiver
class="org.apache.axis2.rpc.receivers.RPCMessageReceiver" />
</operation>
/pointing to:/
public Status createInitial(String wsml) throws AxisFault;
/in the WSDL i noticed:/
<xs:element name="createInitial">
<xs:complexType>
<xs:sequence>
<xs:element minOccurs="0" name="wsml" nillable="true"
type="xs:string"/>
</xs:sequence>
</xs:complexType>
</xs:element>
*so - how can i set minOccurs ="1" from my class or from the
service.xml
??
It should not be nillable also.*
Regards, Tobias
--
View this message in context:
http://www.nabble.com/How-to-define-the-value-of-minOccurs-or-maxOccurs-using-CXF-SOAP-server-engine-tp18120975p18120975.html
Sent from the cxf-user mailing list archive at Nabble.com.
---
Daniel Kulp
[EMAIL PROTECTED]
http://www.dankulp.com/blog
