You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Rules should be able to be versioned independently of the application code. When a new version of rules is published, the application should load the newly published rules and start running the new rules version in place of the old one.
A couple of things to consider:
in-flight rules should not break during a rules version update
version updates should have various modes of scheduling (it could use quartz or EJB timer, perhaps)
Initially, repositories for rules could be Maven. Maybe later, Git could be supported.
The text was updated successfully, but these errors were encountered:
Starting off, rules can be maintained in Maven as stated above. However, that doesn't really provide a nice mechanism for storing human readable rules, which are addressed in a separate issue. But for this issue, it will do.
Rules should be able to be versioned independently of the application code. When a new version of rules is published, the application should load the newly published rules and start running the new rules version in place of the old one.
A couple of things to consider:
Initially, repositories for rules could be Maven. Maybe later, Git could be supported.
The text was updated successfully, but these errors were encountered: