July 2011 - rules-users - Jboss List Archives

by David Godfrey

Can someone point me in the direction of documentation or examples for using Rule Templates together with data held in a database (or source other than XLS / CSV which seems to be what all the examples show)? Many thanks, David

14 years, 11 months

2
1
0 / 0

Possibly stupid question... but I have to ask

by Eugenia Carcel

Hi, Is it possible to insert and modify a fact in the same rule consequence ? >From what I've read in the docs... it isn't... If I could do that it would be great for me. This is the reason why I post this question. I hope someone will anwer.

14 years, 11 months

5
5
0 / 0

Invitation to connect on LinkedIn

by Miles Wen via LinkedIn

LinkedIn ------------ Miles Wen requested to add you as a connection on LinkedIn: ------------------------------------------ Michael, I'd like to add you to my professional network on LinkedIn. - Miles Accept invitation from Miles Wen http://www.linkedin.com/e/zenusm-gqomkhtr-17/uB6kHWAQdcW8YYCt7_2B2zAQXMPq... View invitation from Miles Wen http://www.linkedin.com/e/zenusm-gqomkhtr-17/uB6kHWAQdcW8YYCt7_2B2zAQXMPq... ------------------------------------------ DID YOU KNOW you can conduct a more credible and powerful reference check using LinkedIn? Enter the company name and years of employment or the prospective employee to find their colleagues that are also in your network. This provides you with a more balanced set of feedback to evaluate that new hire. http://www.linkedin.com/e/zenusm-gqomkhtr-17/rsr/inv-27/ -- (c) 2011, LinkedIn Corporation

14 years, 11 months

1
0
0 / 0

Rule not compiling in IDE after migration to 5.2

by Jamie

This rule used to compile in the IDE under Drools 5.1.1: when $order: OrderFact(numberOfCreditCardDeclines > FraudCCDeclines.find().getCreditCardDeclinesThreshold()) then //do something but it's breaking since I moved to 5.2, although it runs fine when I deploy it to the server. Any idea why? If I make the > comparison static, like this: when $order: OrderFact(numberOfCreditCardDeclines > 5) then //do something It also works fine. What's wrong? -- View this message in context: http://drools.46999.n3.nabble.com/Rule-not-compiling-in-IDE-after-migrati... Sent from the Drools: User forum mailing list archive at Nabble.com.

14 years, 11 months

3
7
0 / 0

Guvnor - AccumulateFunction ClassCastException

by Melton, Michael P CTR SPAWARSYSCEN-ATLANTIC, 01200

14 years, 11 months

3
5
0 / 0

Rules migration from ILog

by Tomas Andersen

Hi. We are thinking about using Drools instead of Ilog for a current project. I have some ilr files containing rules/decision points. Is it possible to convert/migrate these to drl files to be used in Drools? If not does anyone know if there is a way to import ilog rules into drools. We have excel scenario files and/or ilr files as a base. Regards, Tomas

14 years, 11 months

2
1
0 / 0

FW: FW: Capitalized element names

by Tom.E.Murphy＠wellsfargo.com

Thanks, Wolfgang. Is it possible the error is in the internal treatment of caps in the code that converts MICompanyMarketClassification in ("2", "3") to MICompanyMarketClassification == "2" || MICompanyMarketClassification == "3" Why I think this: The only place the capitalization seems harmful is when it occurs with an in (...) clause. If I use forced lower- casing of the first letter of a capitalized property in other types of expressions, 5.2 fails. If I use forced lower-casing of the first letter of a capitalized property in an in(...) expression, 5.2 succeeds. If I use natural casing of a capitalized property in other types of expressions, 5.2 succeeds. If I use natural casing of a capitalized property in property in an in(...) expression, 5.2 fails. Tom Murphy Systems Architect Wells Fargo HCFG - CORE Deal Decisioning Platform 800 S. Jordan Creek Parkway | West Des Moines, IA 50266 MAC: X2301-01B Office: 515 324 4853 | Mobile: 515 423 4334 tom.e.murphy(a)wellsfargo.com<mailto:tom.e.murphy@wellsfargo.com> This transmission may contain information that is confidential and/or proprietary. If you are not the individual or entity to which it is addressed, note that any review, disclosure, copying, retransmission, or other use is strictly prohibited. If you received this transmission in error, please notify the sender immediately and delete the material from your system. From: rules-users-bounces(a)lists.jboss.org [mailto:rules-users-bounces@lists.jboss.org] On Behalf Of Wolfgang Laun Sent: Wednesday, July 27, 2011 12:46 AM To: Rules Users List Subject: Re: [rules-users] FW: Capitalized element names Edson, please also not JBRULES-3147: Regression: all uppercase field reference results in compile error. Some forms used to work in 5.1.1 that don't in 5.2. I've added the gist of this thread to JIRA-3147. -W 2011/7/27 Edson Tirelli <ed.tirelli(a)gmail.com<mailto:ed.tirelli@gmail.com>> > > If one works and the other doesn't, then we have a problem. It must work if you make the first letter lowercase, as that is part of the javabeans spec. > Feel free to open a JIRA and we will take a look at it. > Edson > > 2011/7/26 <Tom.E.Murphy(a)wellsfargo.com<mailto:Tom.E.Murphy@wellsfargo.com>> >> >> Thanks Edson, however here is more info on the issue as I've been playing with it: >> >> 1. I have other elements in other objects referenced within the same rule group that start with capital letters and they have no problem. Example: >> >> , FHAMaxBaseMortgageWithToleranceAmt < ($totalLoanAmt+$aggregateSubordinateFinancingAmt) >> >> Compiles just fine in the same session. >> >> 2. If I lower the first M to m to make it mICompanyMarketClassification, it compiles in 5.2 but does NOT compile in 5.0.1 >> >> 3. If I leave it as the capitalized MICompanyMarketClassification, it compiles in 5.0.1 but not 5.2 >> >> Thoughts? >> >> Tom Murphy >> >> Systems Architect >> Wells Fargo HCFG - CORE Deal Decisioning Platform >> >> >> >> 800 S. Jordan Creek Parkway | West Des Moines, IA 50266 >> MAC: X2301-01B >> Office: 515 324 4853 | Mobile: 515 423 4334 >> >> tom.e.murphy(a)wellsfargo.com<mailto:tom.e.murphy@wellsfargo.com> >> >> This transmission may contain information that is confidential and/or proprietary. If you are not the individual or entity to which it is addressed, note that any review, disclosure, copying, retransmission, or other use is strictly prohibited. If you received this transmission in error, please notify the sender immediately and delete the material from your system. >> >> >> >> >> >> From: rules-users-bounces(a)lists.jboss.org<mailto:rules-users-bounces@lists.jboss.org> [mailto:rules-users-bounces@lists.jboss.org<mailto:rules-users-bounces@lists.jboss.org>] On Behalf Of Edson Tirelli >> Sent: Tuesday, July 26, 2011 7:45 PM >> To: Rules Users List >> Subject: Re: [rules-users] Capitalized element names >> >> >> >> >> >> Hi Tom, >> >> >> >> I've seen this before and AFAIK, the javaBeans spec always transforms the first letter to lowercase when converting a get method into a property name. We can try to address this in future releases, maybe falling back to uppercase if the lower case property name lookup fails, but I don't think there is a solution to keep it as is. In 5.2. you can use the full method name instead, but not sure if that isn't event worse: >> >> >> >> MortageInsurance{ getMICompanyMarketClassification() in ("2", "3") } >> >> >> >> Edson >> >> >> >> 2011/7/26 <Tom.E.Murphy(a)wellsfargo.com<mailto:Tom.E.Murphy@wellsfargo.com>> >> >> In the following rule, the element MICompanyMarketClassification is capitalized due to the MI portion being an acronym for Mortgage Insurance. >> >> This comes from our enterprise data model and is not something I can change. >> >> >> >> rule "R1234" >> >> dialect "java" >> >> when >> >> MortageInsurance{ MICompanyMarketClassification in ("2", "3") } >> >> then >> >> system.out.printLn("something"); >> >> end >> >> >> >> The rule refuses to compile, giving a message "Unable to Analyse Expression MICompanyMarketClassification == "2" || MICompanyMarketClassification == "3": >> >> [Error: no such identifier: MICompanyMarketClassification] >> >> [Near : {... MICompanyMarketClassification ....}]" >> >> >> >> I assume this is caused by the capitalized first letter? >> >> Anything I can do to fix the issue or work around it? >> >> >> >> Drools 5.2 community edition >> >> Tom Murphy >> >> Systems Architect >> Wells Fargo HCFG - CORE Deal Decisioning Platform >> >> >> >> 800 S. Jordan Creek Parkway | West Des Moines, IA 50266 >> MAC: X2301-01B >> Office: 515 324 4853 | Mobile: 515 423 4334 >> >> tom.e.murphy(a)wellsfargo.com<mailto:tom.e.murphy@wellsfargo.com> >> >> This transmission may contain information that is confidential and/or proprietary. If you are not the individual or entity to which it is addressed, note that any review, disclosure, copying, retransmission, or other use is strictly prohibited. If you received this transmission in error, please notify the sender immediately and delete the material from your system. >> >> >> >> >> >> >> >> >> >> _______________________________________________ >> rules-users mailing list >> rules-users(a)lists.jboss.org<mailto:rules-users@lists.jboss.org> >> https://lists.jboss.org/mailman/listinfo/rules-users >> >> >> -- >> Edson Tirelli >> JBoss Drools Core Development >> JBoss by Red Hat @ www.jboss.com<http://www.jboss.com> >> >> _______________________________________________ >> rules-users mailing list >> rules-users(a)lists.jboss.org<mailto:rules-users@lists.jboss.org> >> https://lists.jboss.org/mailman/listinfo/rules-users >> > > > > -- > Edson Tirelli > JBoss Drools Core Development > JBoss by Red Hat @ www.jboss.com<http://www.jboss.com> > > _______________________________________________ > rules-users mailing list > rules-users(a)lists.jboss.org<mailto:rules-users@lists.jboss.org> > https://lists.jboss.org/mailman/listinfo/rules-users >

14 years, 11 months

2
1
0 / 0

Re: [rules-users] How to add application data through StatefulKnowledgeSession

by DroolersEye

please refere the drools expert document (section 5.5.2. global ) available in the following link http://docs.jboss.org/drools/release/5.2.0.Final/drools-expert-docs/html_... ----- with kind regards, -- View this message in context: http://drools.46999.n3.nabble.com/How-to-add-application-data-through-Sta... Sent from the Drools: User forum mailing list archive at Nabble.com.

14 years, 11 months

1
0
0 / 0

Declare new fact type - where do i put it?

by Eugenia Carcel

I want to declare a new fact type, but I don't know where to put it. In a java file? It's not java syntax... In a drl file? I've already went through the docs but this piece of info is missing... Thanks again,

14 years, 11 months

2
1
0 / 0

Unable to build constraint as '_default' is invalid

by Eugenia Carcel

Hi, I get the following error when I try to build and deploy: Unable to build constraint as '_default' is invalid : [Rule name='myRuleName'] It yields this error because of this pattern in my drl file: MyType(_default == DefaultType.YES) In my java class MyType I have something like this: public class MyType { .... @XmlAttribute(name = "default") protected DefaultType _default; .... } where DefaultType is an enum. Here is the hole enum class: @XmlType(name = "defaultType") @XmlEnum public enum DefaultType { @XmlEnumValue("yes") YES("yes"); private final String value; DefaultType(String v) { value = v; } public String value() { return value; } public static DefaultType fromValue(String v) { for (DefaultType c: DefaultType.values()) { if (c.value.equals(v)) { return c; } } throw new IllegalArgumentException(v); } } Can you help me? I don't see where the problem is... Any suggestions are much appreciated.

14 years, 11 months

3
2
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

rules-users July 2011