[jboss-jira] [JBoss JIRA] Updated: (JBRULES-1797) Migrate Ruleflow from 4.0 to 5.0 during compilation

[Nimesh Muley (JIRA)]

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

Nimesh Muley updated JBRULES-1797:
----------------------------------

    Attachment: JBRULES-1797.patch.zip


The Zip contains 2 files.
JBRULES-1797.patch - This contains the patch to be applied on drools-compiler. This patch helps to automatically translate a rule flow from 4.0 to 5.0 if system property "drools.ruleflow.port" is set to "true".

JBRULES-1797.patch.changes.txt - This contains broadly what are the changes done in each of the files in the patch.

This patch is taken based on revision 23534 on TRUNK.

Hopefully I have not missed uploading any files in the patch.

If the patch is not as per desired format then let me know.


> Migrate Ruleflow from 4.0 to 5.0 during compilation
> ---------------------------------------------------
>
>                 Key: JBRULES-1797
>                 URL: https://jira.jboss.org/jira/browse/JBRULES-1797
>             Project: JBoss Drools
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>          Components: drools-compiler (flow)
>    Affects Versions:  5.0.0.M2
>            Reporter: Nimesh Muley
>            Assignee: Mark Proctor
>            Priority: Critical
>             Fix For: 5.0.0.M3
>
>         Attachments: JBRULES-1797.patch.zip, RuleFlowFrom4To5.xsl
>
>
> The format of rule flow has changed from 4.0 to 5.0. Due to this, ruleflows are not backward compatible. If the ruleflow is of version 4.0 and automatic migration flag is switched on in 5.0 then the rule flow should be migrated to 5.0 before executing it. Thus having backward support for ruleflows in 5.0 release.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira