You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@xmlbeans.apache.org by "Radu Preotiuc-Pietro (JIRA)" <xm...@xml.apache.org> on 2005/05/02 23:23:11 UTC

[jira] Updated: (XMLBEANS-149) MinOccurs=0 ignored

     [ http://issues.apache.org/jira/browse/XMLBEANS-149?page=all ]

Radu Preotiuc-Pietro updated XMLBEANS-149:
------------------------------------------

    Fix Version: TBD

You are right. Because the required group is a choice, basically all the elements that could potentially appear in that place are optional, so the validator doesn't know what to suggest (if you had one required element and 20 optional elements, it would only suggest the one required element) and just offers all possibilities.
Since this is not a critical issue and the fix requires some smart analysis of what the content model is, I suggest we fix it in a future version.

> MinOccurs=0 ignored
> -------------------
>
>          Key: XMLBEANS-149
>          URL: http://issues.apache.org/jira/browse/XMLBEANS-149
>      Project: XMLBeans
>         Type: Bug
>     Versions: Version 2 Beta 1, Version 1.0.4
>     Reporter: Harald Meyer
>      Fix For: TBD

>
> When compiling the BPEL schema the elements of a process that are optionaled, are not created as optional.
> Extract from the BPEL Schema:
>     <complexType name="Process">
>         <complexContent>
>             <extension base="bpws:ExtensibleElements">
>                 <sequence>
>                     <element name="partnerLinks" type="bpws:PartnerLinks"
>                              minOccurs="0"/>
>                     <element name="partners" type="bpws:Partners"
>                              minOccurs="0"/>
>                     <element name="variables"
>                              type="bpws:Variables"
>                              minOccurs="0"/>
>                     <element name="correlationSets" 
>                              type="bpws:CorrelationSets" minOccurs="0"/>
>                     <element name="faultHandlers" type="bpws:FaultHandlers"
>                              minOccurs="0"/>
>                     <element name="compensationHandler"
>                              type="bpws:CompensationHandler" minOccurs="0"/>
>                     <element name="eventHandlers"
>                              type="bpws:EventHandlers" minOccurs="0"/>
>                     <group ref="bpws:activity"/>
>                 </sequence>
>                 <attribute name="name" type="NCName"
>                            use="required"/>
>                 <attribute name="targetNamespace" type="anyURI"
>                            use="required"/>
>                 <attribute name="queryLanguage" type="anyURI"
>                     default="http://www.w3.org/TR/1999/REC-xpath-19991116"/>
>                 <attribute name="expressionLanguage" type="anyURI"
>                     default="http://www.w3.org/TR/1999/REC-xpath-19991116"/>
>                 <attribute name="suppressJoinFailure" type="bpws:Boolean"
>                            default="no"/>
>                 <attribute name="enableInstanceCompensation" 
>                            type="bpws:Boolean" default="no"/>
>                 <attribute name="abstracProcess" type="bpws:Boolean" 
>                            default="no"/>
>             </extension>
>         </complexContent>
>     </complexType>
> An empty process (inside a process document) now yields the following validation error:
> Message: Expected elements 'partnerLinks@http://schemas.xmlsoap.org/ws/2003/03/business-process/ partners@http://schemas.xmlsoap.org/ws/2003/03/business-process/ variables@http://schemas.xmlsoap.org/ws/2003/03/business-process/ correlationSets@http://schemas.xmlsoap.org/ws/2003/03/business-process/ faultHandlers@http://schemas.xmlsoap.org/ws/2003/03/business-process/ compensationHandler@http://schemas.xmlsoap.org/ws/2003/03/business-process/ eventHandlers@http://schemas.xmlsoap.org/ws/2003/03/business-process/ empty@http://schemas.xmlsoap.org/ws/2003/03/business-process/ invoke@http://schemas.xmlsoap.org/ws/2003/03/business-process/ receive@http://schemas.xmlsoap.org/ws/2003/03/business-process/ reply@http://schemas.xmlsoap.org/ws/2003/03/business-process/ assign@http://schemas.xmlsoap.org/ws/2003/03/business-process/ wait@http://schemas.xmlsoap.org/ws/2003/03/business-process/ throw@http://schemas.xmlsoap.org/ws/2003/03/business-process/ terminate@http://schemas.xmlsoap.org/ws/2003/03/business-process/ flow@http://schemas.xmlsoap.org/ws/2003/03/business-process/ switch@http://schemas.xmlsoap.org/ws/2003/03/business-process/ while@http://schemas.xmlsoap.org/ws/2003/03/business-process/ sequence@http://schemas.xmlsoap.org/ws/2003/03/business-process/ pick@http://schemas.xmlsoap.org/ws/2003/03/business-process/ scope@http://schemas.xmlsoap.org/ws/2003/03/business-process/' at the end of the content in element process@http://schemas.xmlsoap.org/ws/2003/03/business-process/
> Location of invalid XML: <xml-fragment/>
> If necessary I can provide the generated source code and a test case.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@xmlbeans.apache.org
For additional commands, e-mail: dev-help@xmlbeans.apache.org