Yeah, we have that turned on, it's a simple:server not a jaxws; figured
it would work the same though:

        <!-- CXF Endpoint Assembly -->
        <simple:server
                id="member-services-ws"
                address="/service"
                xmlns:service="http://service.member.argushealth.com";
                endpointName="service:MemberService"
                serviceName="service:MemberServices"
                serviceBean="#memberServicesWebservice"
        
serviceClass="com.argushealth.member.service.MemberServicesWebservice">
                <simple:dataBinding>
                        <ref
                                bean="aegisDatabinding" />
                </simple:dataBinding>
                <simple:inInterceptors>
                        <ref
        
bean="com.argushealth.enterprise.security.webservices.authentication.WSS
4JAuthenticator" />
                </simple:inInterceptors>
                <simple:properties>
                        <entry
                                key="schema-validation-enabled"
                                value="true" />
                </simple:properties>
        </simple:server>
-B
 

-----Original Message-----
From: Daniel Kulp [mailto:[email protected]] 
Sent: Tuesday, August 24, 2010 2:58 PM
To: [email protected]
Cc: Stopp, Bryan
Subject: Re: Min Occurs/Nillable False




See the section in the FAQ about schema validation:

http://cxf.apache.org/faq.html#FAQ-HowcanIturnonschemavalidationforjaxws
endpoint%253F

Dan



On Tuesday 24 August 2010 3:42:33 pm Stopp, Bryan wrote:
> How can I get CXF to enforce the minoccurs and nillable settings
during
> invocation?
> 
> I have the following XML Element:
> 
> 
> 
> <xsd:complexType name="MemberIdentifier">
> 
> <xsd:sequence>
> 
> <xsd:element name="birthDate" type="xsd:date" />
> 
> <xsd:element name="firstName" type="xsd:string" />
> 
> <xsd:element name="gender" type="member:Gender" />
> 
> <xsd:element name="groupExternalId" type="xsd:string" />
> 
> <xsd:element name="lastName" type="xsd:string" />
> 
> <xsd:element name="memberPK" type="member:MemberPK" />
> 
> </xsd:sequence>
> 
> </xsd:complexType>
> 
> <xsd:complexType name="MemberPK">
> 
> <xsd:sequence>
> 
> <xsd:element name="clientId" type="xsd:int" />
> 
> <xsd:element name="customerId" type="xsd:int" />
> 
> <xsd:element name="memberId" type="xsd:string" />
> 
> </xsd:sequence>
> 
> </xsd:complexType>
> 
> 
> 
> However, during invoation, any of these fields can be left off the
> request completely, and CXF does not throw any exceptions. Is there a
> way to have CXF enforce the nillable and minoccurs of the WSDL?
> 
> 
> 
> -B
> 
> 
> PRIVILEGED AND CONFIDENTIAL
> This email transmission contains privileged and confidential
information
> intended only for the use of the individual or entity named above.  If
the
> reader of the email is not the intended recipient or the employee or
agent
> responsible for delivering it to the intended recipient, you are
hereby
> notified that any use, dissemination or copying of this email
transmission
> is strictly prohibited by the sender.  If you have received this
> transmission in error, please delete the email and immediately notify
the
> sender via the email return address or
mailto:[email protected]. 
> Thank you.

-- 
Daniel Kulp
[email protected]
http://dankulp.com/blog

PRIVILEGED AND CONFIDENTIAL
This email transmission contains privileged and confidential information 
intended only for the use of the individual or entity named above.  If the 
reader of the email is not the intended recipient or the employee or agent 
responsible for delivering it to the intended recipient, you are hereby 
notified that any use, dissemination or copying of this email transmission is 
strictly prohibited by the sender.  If you have received this transmission in 
error, please delete the email and immediately notify the sender via the email 
return address or mailto:[email protected].  Thank you.




Reply via email to