ok ----- Original Message ----- From: "Michael Neale (JIRA)" <jira <at> codehaus.org> To: <dev <at> drools.codehaus.org> Sent: Friday, December 30, 2005 3:35 AM Subject: [drools-dev] [jira] Created: (DROOLS-469) Create new ReteDumper so people do not access Dumper in reteoo directly
ok ----- Original Message ----- From: "Michael Neale (JIRA)" <jira <at> codehaus.org> To: <dev <at> drools.codehaus.org> Sent: Friday, December 30, 2005 3:37 AM Subject: [drools-dev] [jira] Resolved: (DROOLS-469) Create new ReteDumper so people do not access Dumper in reteoo directly
Michael,
I have to find a solution for the following recommendation. However, I
am not able to find adequate documentation.
"Instead of storing the object under application scope on startup,
clients would have to do a JNDI lookup per request to get the object. If
we can figure out how to do the former, it would probably be simpler
than using custom code. "
Keith A. Marshall, B.Sc. | Java Contractor, eCommerce | Ext: 1089
-----Original Message-----
From: Michael Neale (JIRA) [mailto:jira <at> codehaus.org]
Sent: Thursday, December 29, 2005 10:37 PM
To: dev <at> drools.codehaus.org
Subject: [drools-dev] [jira] Resolved: (DROOLS-469) Create new
ReteDumper so people do not access Dumper in reteoo directly
[ http://jira.codehaus.org/browse/DROOLS-469?page=all ]
Michael Neale resolved DROOLS-469:
----------------------------------
Resolution: Fixed
> Create new ReteDumper so people do not access Dumper in reteoo
> directly
> ----------------------------------------------------------------------
> -
(Continue reading)
HI Keith. I assume you need to change rules on the fly. Are you doing a workingmemory per request pattern? (ie a request comes in, you create a new working memory from the rule base, process the rules and then continue?) On 1/4/06, Keith Marshall <kmarsha1 <at> insight.com> wrote: > > Michael, > > I have to find a solution for the following recommendation. However, I > am not able to find adequate documentation. > > > > "Instead of storing the object under application scope on startup, > clients would have to do a JNDI lookup per request to get the object. If > we can figure out how to do the former, it would probably be simpler > than using custom code. " > > > Keith A. Marshall, B.Sc. | Java Contractor, eCommerce | Ext: 1089 > > -----Original Message----- > From: Michael Neale (JIRA) [mailto:jira <at> codehaus.org] > Sent: Thursday, December 29, 2005 10:37 PM > To: dev <at> drools.codehaus.org > Subject: [drools-dev] [jira] Resolved: (DROOLS-469) Create new > ReteDumper so people do not access Dumper in reteoo directly >(Continue reading)
Your assumption is correct. No I am not doing a working mem per request.
We are using STRUTS what we have done is create a listener class that
initiates the working memory on application startup. At that time the
ruleBase, per say is put into application scope. When we require
processing with rules the rulebase is removed from the context and then
the appropriate object is asserted. See code below:
ServletContext ctx = request.getSession().getServletContext();
WorkingMemory mem =
(WorkingMemory)ctx.getAttribute(Constants.RULES_ENGINE);
...
...
//Assert the User object to the Rule Engine to process
//the ApprovalProcessEntry rules. A single assertion
here will
//provide the User object with the values required for
all tests
//to follow for access to this module
mem.assertObject(user);
//Execute the Agenda on the object asserted
mem.fireAllRules();
//start page-view if
if (user.getCanUseApprovalProcess() ) {
...
(Continue reading)
We are trying to get Drools into the Magic Quadrant report, however we
cannot do this unless we show that Drools the JBoss Rules engine has
atleast a 3 million "impact" on the market. Because open source is
different we can include end users as a calculated financial impact, to
do this we need to gather some answers to questions from our users. No
information will be made public, its purely for us to present to
gartner, and we can sign an NDA if necessary. If you can help please
answer these, as briefly or as detailed as you can manage, and reply to
me directly.
1. What specific problem(s) were you trying to solve?
2. Describe the project itself; what was needed?
3. Is this project internal or external and how many estimated users?
4. What products & vendors did you consider?
5. Why JBoss Rules? How much did open source play in your decision?
6. Describe the implementation/size (hardware, OS, databases, # of
servers or CPUs, # of developers, etc...)
7. How long did it take you to implement your JBoss Rules solution?
How did that compare to previous projects?
8. What benefits do you realize? (ROI, cost savings, performance
improvements, developer productivity, etc...)
9. Are you now in deployment? How has JBoss performed so far? What
were the main delivered benefits from Drools?
10. What is your experience with JBoss support thus far? What support
products do you use (Professional Support, Consulting, Training)?
11. Knowing what you know now, would you choose JBoss again for
upcoming projects?
Many Thanks
(Continue reading)
condition ending with ; is not considered as wrong when parsing ruleset but generates error when asserting
an object
--------------------------------------------------------------------------------------------------------------------
Key: DROOLS-470
URL: http://jira.codehaus.org/browse/DROOLS-470
Project: drools
Type: Bug
Components: semantics.java
Versions: 2.5
Reporter: Kris Verlaenen
Priority: Minor
When creating a java condition ending with a semi-colon, loading of the ruleset is successful.
e.g. when creating a rule containing
<java:condition>
true;
</java:condition>
then
ruleBase = RuleBaseLoader.loadFromInputStream(this.getClass().getResourceAsStream(
"/myrule.java.drl" ))
does not generate any errors.
Although, when asserting an object in the working memory that leads to the evaluation of that condition,
first some output is written to the system out, followed by an exception:
drools/org/MyRuleSet_1136384249796/java/Allow_ProviderA_access_0.java(26)
Syntax error on token ";", delete this token
drools/org/MyRuleSet_1136384249796/java/Allow_ProviderA_access_0.java(26)
(Continue reading)Keith A. Marshall, B.Sc. | Java Contractor, eCommerce | Ext: 1089 -----Original Message----- From: Mark Proctor [mailto:mproctor <at> codehaus.org] Sent: Tuesday, January 03, 2006 4:33 PM To: Drools User List; dev <at> drools.codehaus.org Subject: [drools-dev] questionnaire to help get Drools into Gartner Magic Quandrant We are trying to get Drools into the Magic Quadrant report, however we cannot do this unless we show that Drools the JBoss Rules engine has atleast a 3 million "impact" on the market. Because open source is different we can include end users as a calculated financial impact, to do this we need to gather some answers to questions from our users. No information will be made public, its purely for us to present to gartner, and we can sign an NDA if necessary. If you can help please answer these, as briefly or as detailed as you can manage, and reply to me directly. 1. What specific problem(s) were you trying to solve? The extraction of Customer/Entity specific logic from the application code to a centrally managed repository. 2. Describe the project itself; what was needed? On-line retailer and reseller management of purchasing rules.(Continue reading)
How do we get more specific development assistance with Drools? Is it covered under our JBoss Support contract? Keith A. Marshall, B.Sc. | Java Contractor, eCommerce | Ext: 1089 -----Original Message----- From: Keith Marshall Sent: Tuesday, January 03, 2006 2:48 PM To: dev <at> drools.codehaus.org Subject: RE: [drools-dev] JNDI Importance: High Your assumption is correct. No I am not doing a working mem per request. We are using STRUTS what we have done is create a listener class that initiates the working memory on application startup. At that time the ruleBase, per say is put into application scope. When we require processing with rules the rulebase is removed from the context and then the appropriate object is asserted. See code below: ServletContext ctx = request.getSession().getServletContext(); WorkingMemory mem = (WorkingMemory)ctx.getAttribute(Constants.RULES_ENGINE); ... ... //Assert the User object to the Rule Engine to process //the ApprovalProcessEntry rules. A single assertion here will //provide the User object with the values required for(Continue reading)
Best advice you can get is to come onto IRC, where you can talk to the drools developers - http://irc.codehaus.org JBoss offer the full range of support services, although those are limited on the 2.x release - only 3.x will be fully supported. Mark Keith Marshall wrote: > How do we get more specific development assistance with Drools? Is it > covered under our JBoss Support contract? > > > Keith A. Marshall, B.Sc. | Java Contractor, eCommerce | Ext: 1089 > > -----Original Message----- > From: Keith Marshall > Sent: Tuesday, January 03, 2006 2:48 PM > To: dev <at> drools.codehaus.org > Subject: RE: [drools-dev] JNDI > Importance: High > > Your assumption is correct. No I am not doing a working mem per request. > We are using STRUTS what we have done is create a listener class that > initiates the working memory on application startup. At that time the > ruleBase, per say is put into application scope. When we require > processing with rules the rulebase is removed from the context and then > the appropriate object is asserted. See code below: > > > ServletContext ctx = request.getSession().getServletContext();(Continue reading)
RSS Feed43 | |
|---|---|
94 | |
80 | |
85 | |
36 | |
19 | |
37 | |
52 | |
49 | |
13 | |
50 | |
44 | |
32 | |
16 | |
87 | |
123 | |
61 | |
36 | |
66 | |
35 | |
104 | |
73 | |
90 | |
102 | |
120 | |
135 | |
117 | |
93 | |
85 | |
144 | |
92 | |
153 | |
138 | |
122 | |
25 | |
47 | |
87 | |
68 | |
58 | |
40 | |
45 | |
30 | |
46 | |
79 | |
40 | |
38 | |
20 | |
27 | |
26 | |
23 | |
40 | |
62 | |
57 | |
38 | |
47 | |
76 | |
31 | |
49 | |
40 | |
26 | |
27 | |
30 | |
23 | |
14 | |
43 | |
13 | |
44 | |
56 | |
17 | |
54 | |
78 | |
36 | |
92 | |
54 | |
83 | |
106 | |
53 | |
75 | |
66 | |
20 | |
23 | |
130 | |
150 | |
22 | |
42 | |
95 | |
121 | |
46 | |
17 | |
26 | |
17 | |
54 | |
38 | |
29 | |
84 | |
30 | |
63 | |
52 | |
86 | |
50 | |
16 | |
15 | |
25 | |
42 | |
4 |
