Hi Willem,
The only thing that I managed to do before Mario fixed the issue for me in
5.4.1.Final was to include a modified version of MvelConstraint in my own code
(of course earlier in the classpath so that it replaced the one from drools)
and changing the value of static member
Hi,
Thanks for the replies. I'm actually working with a big number of large rule
sets (ranging from 100 rules to up to 3000), which are generated based on
another proprietary language. These are not used system wide, but on a user per
user basis and loaded dynamically
In itself, the system
: Jean-Paul Shemali jshem...@hotmail.com
À: rules-users@lists.jboss.org
Envoyé: Lundi 10 Septembre 2012 10:06:43
Objet: Re: [rules-users] Guvnor Declarative Model
Simply by not writing them in drools, but in another (proprietary) language,
which in turn gets translated to drools at runtime
Simply by not writing them in drools, but in another (proprietary) language,
which in turn gets translated to drools at runtime.
Of course there's nothing really simple about the translation and how the
actual facts get generated
Date: Sat, 8 Sep 2012 23:53:47 +0200
From:
Thanks for quick answers guys!
I just realized the original thread never made it trough to the list (the user
didn't register probably) the original poster had the same issue on Guvnor,
hence the title.
Edson I've opened https://issues.jboss.org/browse/JBRULES-3621 for this
Unfortunately, I
Hi again mario,
Yes in my case it would be nice for generated classes to be garbage collected
when no longer referenced : for long-lived virtual machines where rules are
changed a lot, you really hit the max perm gen quickly enough.
I guess what you are describing is a production environment
Hi again all,
Am i the only one noting these issues on the version?
If this is not the right place to discuss this, could someone point me in the
right direction (do I enter an issue in JIRA with potential patches, ...)?
Thanks in advance
Date: Mon, 25 Jun 2012 00:01:16 -0700
From:
