[ 
https://issues.apache.org/jira/browse/DAFFODIL-1885?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Dave Thompson closed DAFFODIL-1885.
-----------------------------------

Pulled the latest updates from the incubator-daffodil repository and verified 
the updates included the specified commit, 
1328c40f23d23f6e15e300607b27cf22447b0e13.

Verified that the specified changes were implemented. Verified the added tests 
executed successfully. Verified that without the specified fix the added tests 
fail for the specified reason.

> Initiators are not being inherited from parent choices
> ------------------------------------------------------
>
>                 Key: DAFFODIL-1885
>                 URL: https://issues.apache.org/jira/browse/DAFFODIL-1885
>             Project: Daffodil
>          Issue Type: Bug
>          Components: Compatibility, Front End
>    Affects Versions: 2.1.0
>            Reporter: Josh Adams
>            Assignee: Dave Thompson
>            Priority: Major
>             Fix For: 2.1.0
>
>
> This is a bug that is currently effecting the compatibility with the 
> IBM4690-TLOG schema project.
> In the IBM4690-TLOG schemas there is a parent choice with 
> dfdl:initiatedContent="yes" that contains groups of choices.  The child 
> choices define an initiator, but the initiator does not seem to be getting 
> passed down the the elements contained within the choice inside the child 
> choice (3rd level choice), causing the following SDE:
> Schema Definition Error: Enclosing group has initiatedContent='yes', but 
> initiator is not defined.
>  
> Here is a simplified schema as an example:
> {code:java}
> ...
> <xs:choice dfdl:initiatedContent="yes">
>   <xs:group ref="childChoice"/>
> </xs:choice>
> <xs:group name="childChoice">
>   <xs:choice dfdl:initiator="%#11;:">
>     <xs:element name="elementWithInheritedInitiator"/>
>     <xs:choice>
>       <xs:element name="elementWithoutInheritedInitiator"/>
>     </xs:choice>
>   </xs:choice.
> </xs:group>
> ...{code}
>  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to