On 04/01/2011 01:41, dc tech wrote:
I wonder if any, or perhaps many, of you are using Drools community
version in production systems? Or are you using the jBoss BRMS - the
commercially supported version?
If you are using the community version, what is your sense of
stability of the releases?
The commercial project code base is supported for 5
years and bugs are
patched without forcing you to include new features or apis. It's tested
against a wider range of projects and application servers and releases
are generally based on a given corporate schedule.
The project is released when it's ready and bug fixes are not
backported, so you always need to be running bleeding edge to get latest
bug fixes. So while you get the bug fixes, you also get all the new
features which haven't had much testing yet and can introduce some level
of instability. This puts a lot more onus, and thus cost, onto the end
user to test more thoroughly in their environments.
Mark
On 1/3/11, smogstate<smogstate(a)yahoo.com> wrote:
> I have same issue. Can anyone help?
> --
> View this message in context:
>
http://drools-java-rules-engine.46999.n3.nabble.com/Drools-Flow-within-St...
> Sent from the Drools - User mailing list archive at
Nabble.com.
> _______________________________________________
> rules-users mailing list
> rules-users(a)lists.jboss.org
>
https://lists.jboss.org/mailman/listinfo/rules-users
>