[teiid-issues] [JBoss JIRA] (TEIID-3244) XML Choice is not being evaluated as expected

[Steven Hawkins (JIRA)]

     [ https://issues.jboss.org/browse/TEIID-3244?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Steven Hawkins moved JBEDSP-1238 to TEIID-3244:
-----------------------------------------------

          Project: Teiid  (was: JBoss Enterprise Data Services Platform)
              Key: TEIID-3244  (was: JBEDSP-1238)
      Component/s: Query Engine
                       (was: Server)
    Fix Version/s: Open To Community
                       (was: Future Versions)


> XML Choice is not being evaluated as expected
> ---------------------------------------------
>
>                 Key: TEIID-3244
>                 URL: https://issues.jboss.org/browse/TEIID-3244
>             Project: Teiid
>          Issue Type: Bug
>          Components: Query Engine
>            Reporter: Debbie Steigner
>            Assignee: Steven Hawkins
>            Priority: Minor
>             Fix For: Open To Community
>
>
> We have an XML View model, built on a schema that includes choice nodes. We've used the choice editor to define a default choice; however, no data comes back for any of these choices, despite the fact that data does exist.
> It appears that MMX is not executing the queries under the default choice nodes.
> As a second test, we tried setting criteria that would always be true. Still, the choice nodes were not executed.
> Finally, we tried setting criteria that would never be true, and told the choice editor to throw an exception if the criteria was not met. No exception was thrown. This seems to indicate that MMX simply isn't evaluating this part of the document.
> Finally, I have an theory about what could be the source of the problem, based on what I did differently during the rebuild. If you click on the "Subject" mapping class, notice that "choice" gets highlighted. In my rebuild, when I click on "Subject", the "category" gets highlighted, but the choice above it does not. The behavior is problematic in the first case, but works as expected in the second case.



--
This message was sent by Atlassian JIRA
(v6.3.8#6338)