[jboss-jira] [JBoss JIRA] (DROOLS-1033) In kmodule.xml, the <kbase> name should be optional if all that kbase's ksessions are named (or if there is only 1 kbase)

[Geoffrey De Smet (JIRA)]

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

Geoffrey De Smet updated DROOLS-1033:
-------------------------------------
    Priority: Minor  (was: Major)


> In kmodule.xml, the <kbase> name should be optional if all that kbase's ksessions are named (or if there is only 1 kbase)
> -------------------------------------------------------------------------------------------------------------------------
>
>                 Key: DROOLS-1033
>                 URL: https://issues.jboss.org/browse/DROOLS-1033
>             Project: Drools
>          Issue Type: Enhancement
>          Components: core engine
>    Affects Versions: 6.3.0.Final
>            Reporter: Geoffrey De Smet
>            Assignee: Mario Fusco
>            Priority: Minor
>
> Currently this kmodule.xml isn't accepted because the kbase names are missing:
> {code}
> <kmodule ...>
>   <kbase packages="org.cars">
>     <ksession name="carsKsession"/>
>   </kbase>
>   <kbase packages="org.planes">
>     <ksession name="planesKsession"/>
>   </kbase>
> </kmodule>
> {code}
> From OptaPlanner, we find what we need through the ksession name, so the kbase names can be anonymous (or uniquely generated - we don't care).
> Having to specify a unique kbase name, is an annoying hoop to jump through (including maintenance burden) - but more importantly it bloats our Quick Start minimal code examples of "using OptaPlanner with a KieContainer and Kjar".



--
This message was sent by Atlassian JIRA
(v6.4.11#64026)