[
https://jira.jboss.org/jira/browse/JBRULES-1797?page=com.atlassian.jira.p...
]
Nimesh Muley updated JBRULES-1797:
----------------------------------
Attachment: RuleFlowFrom4To5.xsl
XSL is attached herewith. It has one issue that it does not add xmlns element.
A system property can be added and read in ProcessBuilder.addProcessFromFile to check
whether translation activity needs to be carried out. If yes, and if the ruleflow belongs
to version 4.0 then XSL needs to be applied to produce the 5.0 format and then processed
as per 5.0 format.
The system property should be added so that people who have started work on 5.0 do not
have to bear the brunt of checking of ruleflow version.
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: 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