[jboss-jira] [JBoss JIRA] (DROOLS-117) The "from" CE does not manage @events correctly

[Davide Sottara (JIRA)]

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

Davide Sottara moved JBRULES-3637 to DROOLS-117:
------------------------------------------------

              Project: Drools  (was: JBRULES)
                  Key: DROOLS-117  (was: JBRULES-3637)
             Workflow: GIT Pull Request workflow   (was: jira)
    Affects Version/s:     (was: 5.4.0.Final)
          Component/s:     (was: drools-core (fusion))
        Fix Version/s:     (was: 6.0.0.Alpha1)

    
> The "from" CE does not manage @events correctly
> -----------------------------------------------
>
>                 Key: DROOLS-117
>                 URL: https://issues.jboss.org/browse/DROOLS-117
>             Project: Drools
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>            Reporter: Davide Sottara
>            Assignee: Edson Tirelli
>            Priority: Critical
>
> If an event type (i.e. an instance of a class marked with @role(event)) is returned by a "from" node, it is not wrapped by an EventFactHandle as expected, so e.g. any attempt to use temporal operators will fail. 
> See the test case below for an example
> The problem is in FromNode.java around line 200, where the new handles are created without passing an ObjectTypeConfiguration, leading to the default creation of a DefaultFactHandle.
> I wonder if it's possible to simply retrieve the ObjectTypeConf:
> workingMemory.getObjectTypeConfigurationRegistry().getObjectTypeConf( context.getEntryPoint(), object )
> and pass it to the handle factory method. 
> I tested it and it works for the test case below, but there may be other
> side-effects I'm not seeing.
> ---------------------------------------------------------------------------
> May be related (but not the same as) #JBRULES-2423

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira