[jboss-jira] [JBoss JIRA] Commented: (JBRULES-3143) Knowledge Agent does not handle multiple packages in Builder output from single resource

[Davide Sottara (JIRA)]

    [ https://issues.jboss.org/browse/JBRULES-3143?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12614635#comment-12614635 ] 

Davide Sottara commented on JBRULES-3143:
-----------------------------------------

I have had the same problem recently, when building a complex KB from many knowledge resources.
I'm already working on a (simplified, actually) version of the KA which solves this problem. I will commit for review soon.

> Knowledge Agent does not handle multiple packages in Builder output from single resource
> ----------------------------------------------------------------------------------------
>
>                 Key: JBRULES-3143
>                 URL: https://issues.jboss.org/browse/JBRULES-3143
>             Project: Drools
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: drools-core  (expert)
>    Affects Versions: 5.2.0.Final
>            Reporter: Wolfgang Laun
>            Assignee: Mark Proctor
>            Priority: Blocker
>             Fix For: 5.2.1.Final
>
>
> Note: see also https://issues.jboss.org/browse/JBRULES-2940
> KnowledgeAgent with a ChecngeSet containing a single DRL:
>    package x
>    import y.Type
>    declare Type
>       @role(event)
>    end
>    //...rules etc.
> If this is passed to the builder, it'll return two KnowledgePackageImpl objects, one with name 'x' and another one with name 'y'. But the KA only takes the first package from the Collection of packages returned by the builder.
> =!=> KA must process all packages from the builder.
> =!=> Incremental kBase building requires diff-ing between old/new packages. This, then, must take into account that contribution to one package can come from several resource builds.
> =!=> The idea that the kBuilder should return packages with different names from a single DRL build is probably wrong. If a Drools package foo contains an import bar.Type, then this is still an asset in package foo and needs to be handled as a type reference in foo. Any annotation additions must be carried by that asset foo. (The *Java* package of the imported bar.Type remains of course bar.)

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira