[jboss-jira] [JBoss JIRA] (DROOLS-2263) [GSS] (6.4.z) Unexpected results in GDST when using enumerations with commas

[Toni Rikkola (JIRA)]

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

Toni Rikkola moved RHBRMS-3064 to DROOLS-2263:
----------------------------------------------

              Project: Drools  (was: JBoss BRMS Platform)
                  Key: DROOLS-2263  (was: RHBRMS-3064)
             Workflow: GIT Pull Request workflow   (was: CDW with docs v1)
       Docs QE Status: NEW
          Component/s: Guided Decision Table Editor
                           (was: Business Central)
    Affects Version/s:     (was: 6.4.1.GA)
            QE Status: NEW


> [GSS] (6.4.z) Unexpected results in GDST when using enumerations with commas
> ----------------------------------------------------------------------------
>
>                 Key: DROOLS-2263
>                 URL: https://issues.jboss.org/browse/DROOLS-2263
>             Project: Drools
>          Issue Type: Bug
>          Components: Guided Decision Table Editor
>            Reporter: Toni Rikkola
>            Assignee: Toni Rikkola
>
> When using enumerations where the values itself contain a comma, the rules generated by a GDST are unexpected, as the "contains in" operator splits those values in the enumerations. Example enumeration:
> {noformat}
>    fact: person
>    field: city
>    context: ['paris','london','new york,boston']
> {noformat}
> Note: see the 'new york, boston' sample.
> The code generated will be:
> {noformat}
> rule "Row 1 personGDT"
>     dialect "mvel"
>     when
>         p : person( city in ( "new york", "boston" ) )
>     then
> end
> {noformat}
> Basically "paris" and "new york,boston" will be treated by the DSL parser as 3 strings in the DRL generation and will produce someting simiular to
>    p : person( city in ( "paris", "new york", "boston" ) )
> But what the customer expects is the following
>    p : person( city in ( "paris", "new york,boston" ) )



--
This message was sent by Atlassian JIRA
(v7.5.0#75005)