Op 17-07-12 20:54, Garf schreef:
last month, Ralph wrote: /All the examples in the drools-planner-examples
seem to have a fixed list of problem facts (rooms, teachers, timeslots)
which only should be combined optimally./
Just to address this one unanswered point.
The Cloud Balancing example
Instead of the guvnor jboss-as-7.0 war, use the guvnor tomcat-6.0 war,
that one includes the weld jars.
Op 18-07-12 06:17, Ravikiran schreef:
Hi,
I am deploying drools-guvnor.war (version 5.3.0) into Websphere AS 7. The
war file was working perfectly fine in JBoss AS 7. But i am getting below
Hi Esteban,
I can't pass de source code of my rules because it's too much.
I've about 1600 rules. Too much to be passed.
Can you give me any suggestions?
King regards
Paco
--
View this message in context:
http://drools.46999.n3.nabble.com/Error-on-Build-Package-Click-tp4018712p4018749.html
Hi Geoffrey,
I couldn't find any weld related jar files available in
guvnor-5.3.0.Final-tomcat-6.0.war. Also i have tried wild card search like
weld*, but i couldn't find it.
Could you please check whether the below line from the error message might
give you some idea,
Service method 'public
hello..i am using the following changeset :
change-set xmlns=http://drools.org/drools-5.0/change-set;
xmlns:xs=http://www.w3.org/2001/XMLSchema-instance;
xs:schemaLocation=http://drools.org/drools-5.0/change-set.xsd
Hi Geoffrey Other Gurus
To throw more light on the above error message, please find below the
getCurrentUser() method snippet that i have taken from the source of
SecurityServiceServlet.java. Please tell me in what cases the
securityService comes as null for causing this exception.
public
Just realized:
We only use CDI, weld, seam 3 and arquillian since Guvnor 5.4.0
In Guvnor 5.3.0 we still use seam 2 (which does not use the CDI spec jars).
So how can you be running into errors that speak about weld-servlet?
Op 18-07-12 14:19, Ravikiran schreef:
Hi Geoffrey Other Gurus
To
Hi,
I am new to drools, currently i have deployed drools-guvnor5.3 on jboss AS
5.1GA.
I want to use guvnor asset editor in my custom application. I have followed
the link
http://ilesteban.wordpress.com/2010/11/23/guvnor-embed-assets-editor-in-your-application/.
I am using assetEditor.html, but
Thanks. I downloaded 5.2 and there are no compilation errors. I also need
to check to see if one decision table issue (that I had worked around) was
solved. However, in 5.2 I get
Hi Joffrey,
I have downloaded the distribution shows Drools-guvnor 5.3.0, but when i see
the Guvnor version from web UI (Adminstration--About) it shows the version
as SNAPSOT 5.4.0. Now i too suspect that my Guvnor is of version 5.4.0 only,
that's why all those errors were coming.
I feel that
Try removing the
'gwt.codesvr=localhost:8080http://localhost:8080/drools-guvnor/org.drools.guvnor.Guvnor/standaloneEditorServlet?gwt.codesvr=localhost:8080'
from the url. That parameter is only valid when GWT is running in dev mode.
Best Regards,
Esteban
I was able to reproduce this error locally by updating my version of java to
1.6_31(thought I had but I didn't) The stack trace doesn't give me any
information really to go off of. I have around 150 rules of which a dozen
will retract the object OrderSideContext. Is there a way to get a better
Is there a recommended way to remove events from working memory that don't
match and can't activate any rules?
For example, let's say I have two rules which should both fire when a person
with name Bob is encountered. If a person with name Jim comes in he
stays in working memory forever even
If a fact is to be matched right after insertion the solution is
simple: add a rule with low salience matching and retracting the fact.
If you expect/hope that it matches later and you have a time limit,
@expires is the answer.
The interesting case is when you don't have the time limit and still
Thanks for the super fast reply W!
The problem with retracting with a low salience is that my rule set is
fairly dynamic. Rules come and go. And we have lots of event types and
lots of fields within them to match on.
Some rules may match an event immediately. Ex:
when
$p : Person( name ==
If your rules are dynamic, would you still want to retract a fact not
matching any of your current rules,
knowing that a new rule might appear later, which would be activated by that
fact?
This said, the problem here is garbage-collecting facts which have been
insert, but are in a zombie
status,
I wrote a method to compile these rules using the KnowledgeBaseBeanFactory,
but the unit tests using it did not fail (i.e. did not repro the bug). Here
is my method:
public static KnowledgeBase createKnowledgeBaseUsingBeanFactory(String path)
throws Exception {
ListDroolsResourceAdapter
Davide Sottara wrote
If your rules are dynamic, would you still want to retract a fact not
matching any of your current rules,
knowing that a new rule might appear later, which would be activated by
that fact?
That's a good question. Smaller memory footprint by retracting. But we
lose
18 matches
Mail list logo
