JESS: how to dumping rules ?

Hi I tried to dump the rules loaded at some point in time as follows but it did not work out... I do not know the names beforehand and have to figure out why they are not firing... Jess (rules) For a total of 0 rules in module MAIN. Jess (defrule x (f $? )=) TRUE Jess (rules) MAIN::x For a

Re: JESS: how to dumping rules ?

(rules) just prints, returning nil. (foreach ?v (explode$ (ppdefrule *)) (ppdefrule ?v)) -W On Wed, Sep 2, 2009 at 11:25 AM, jo etaoi...@yahoo.com wrote: Hi I tried to dump the rules loaded at some point in time as follows but it did not work out... I do not know the names beforehand and

Re: JESS: how to dumping rules ?

On Sep 2, 2009, at 5:25 AM, jo wrote: Hi I tried to dump the rules loaded at some point in time as follows but it did not work out... I do not know the names beforehand and have to figure out why they are not firing... That's what (ppdefrule *) does.

Re: JESS: how to dumping rules ?

Looks like (ppdefrule *) is sufficient, Jess (foreach ?v (explode$ (ppdefrule *)) (ppdefrule ?v)) Jess reported an error in routine call while executing (call (engine) findDefrule ?__rule) while executing (bind ?__defrule (call (engine) findDefrule ?__rule)) while

Re: JESS: how to dumping rules ?

On Wed, Sep 2, 2009 at 1:55 PM, Wolfgang Laun wolfgang.l...@gmail.comwrote: (rules) just prints, returning nil. This is correct. (foreach ?v (explode$ (ppdefrule *)) (ppdefrule ?v)) This is nonsense, -W

Re: JESS: how to dumping rules ?

Maybe that is what you want? (bind ?it ((engine) listDefrules)) (while (?it hasNext) (printout t (ppdefrule ((?it next) getName)) crlf crlf) ) Regards, Florian On Wed, Sep 2, 2009 at 11:25 AM, jo etaoi...@yahoo.com mailto:etaoi...@yahoo.com wrote: Hi I tried to dump the rules

RE: JESS: JessML and metaphors

Thanks a lot for your insight. Son -Original Message- From: owner-jess-us...@sandia.gov [mailto:owner-jess-us...@sandia.gov] On Behalf Of Ernest Friedman-Hill Sent: Tuesday, September 01, 2009 9:31 PM To: jess-users Subject: Re: JESS: JessML and metaphors The javax.rules properties

Re: JESS: how to dumping rules ?

Cool, works like a charm... Thanks Joe - Original Message From: Florian Fischer florian.fisc...@sim.hcuge.ch To: jess-users@sandia.gov Sent: Wednesday, September 2, 2009 3:56:32 PM Subject: Re: JESS: how to dumping rules ? Maybe that is what you want? (bind ?it ((engine)

JESS: static members in Jess 7.1

Hi, I'm helping a client that's currently on a very old Jess 7.0 (b2 I believe) upgrade to the 7.1p2 version. The existing jess code imports some 'constructed' pre- Java 1.5 enums of the form public class MyEnum { public final static ENUMVAL1 = new MyEnum(..); } In the 7.0b Jess code we

Re: JESS: matching field item : in rule ?

First, let me say that strictly, this isn't legal. The : character is a special character in Jess and although the parser is letting you get away with asserting that fact, it really shouldn't. It should be an error right there. But given that you've already gotten into this situation, you

Re: JESS: static members in Jess 7.1

Hi Erich, I have some bad news for your client: this syntax {myEnum != MyEnum.ENUMVAL1} NEVER worked. The test they've written is comparing the myEnum slot to the Jess symbol MyEnum.ENUMVAL1, which, although it wouldn't give an error, also never did the right thing. This stopped

JESS: quering working memory

Hello, I'm writting an expert system in jess. It includes the two kinds of templates, the ones that you can define from java (using declare from-class) and the ones that you define directly in the clp archive. The beans are all of the same kind, all of the contains Strings. I've experimenting

Re: JESS: quering working memory

Hi Lucia, Basically the issue is that Jess has two completely different text- like data types: RU.STRING, which are double-quoted Strings that can contain spaces and punctuation, and RU.SYMBOL, which don't have quotes and generally look like Java identifiers. They're not the same, and

Re: JESS: static members in Jess 7.1

Awesome thanks for the quick response On Wed, Sep 2, 2009 at 1:29 PM, Ernest Friedman-Hillejfr...@sandia.gov wrote: Hi Erich, I have some bad news for your client: this syntax  {myEnum  != MyEnum.ENUMVAL1} NEVER worked. The test they've written is comparing the myEnum slot to the Jess

Re: JESS: quering working memory

Thank you very much for your answer!! i'm gonna make the change that you mentioned! On Wed, Sep 2, 2009 at 5:22 PM, Ernest Friedman-Hill ejfr...@sandia.govwrote: Hi Lucia, Basically the issue is that Jess has two completely different text-like data types: RU.STRING, which are double-quoted