[jboss-jira] [JBoss JIRA] Commented: (JBRULES-1797) Migrate Ruleflow from 4.0 to 5.0 during compilation
[
https://jira.jboss.org/jira/browse/JBRULES-1797?page=com.atlassian.jira.p...
]
Kris Verlaenen commented on JBRULES-1797:
-----------------------------------------
Looking very good, thx !
I only did two minor changes to the xsl:
- While the type of the process was Workflow in Drools4, RuleFlows should now have type
"RuleFlow" so I hardcoded that type
- The XSL also set an id on the constraint, while that is not allowed by the XSD (and not
necessary anyway) so removed the id for constraints
I was able to execute all the Drools4.0.7 examples using the parser (when turning on the
system property) so committing now to trunk.
Kris
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