JESS: calling an integer or a string

2004-05-27 Thread kimos
hi there, first i want to thanks Ernest Friedman-Hill for helping me and everyone in the mailing list. you are a great help. ok here is my quastion: i have an string and i want to call it in the assert while executioncommand r.executeCommand((assert (i-have-moved))); this is what i have

Re: JESS: Retracting large number of facts

2004-05-27 Thread ejfried
I think Mithun Sheshagiri wrote: [Charset iso-8859-1 unsupported, filtering to ASCII...] Hello, Thank you for your prompt response. If you meant that the proper ordering solves the problem in version 6.1p7 then please ignore the remainder of the mail. Proper ordering solves the

RE: JESS: calling an integer or a string

2004-05-27 Thread Jason Morris
Hi Kimos: I'm learning Jess, too! One thing that I do to avoid errors with (Rete) executeCommmand() is to build a command string first. This way I can do a sanity check on its components before using it in executeCommand(). A StringBuffer works nicely... for example: Rete engine = new Rete();

Re: JESS: calling an integer or a string

2004-05-27 Thread Dusan Sormaz
You can not mix java and jess. Assuming that getstring() is a method which returns String in your java class, then proper code would be: r.executeCommand((assert ( + getstring() + ))); Regards, Dusan Sormaz At 11:31 AM 5/27/2004 +0200, you wrote: hi there, first i want to thanks Ernest

JESS: Message: Bad index 53 in call to set() on this vector...

2004-05-27 Thread sorokinru
Hello, jess-users! Message: Bad index 53 in call to set() on this vector: (MAIN::object (is-a Questions: 1. What usually means this message? 2. Specifically, what means a number 53? Thanx for the answers. Sincerely, Ru Ruslan P. Sorokin [EMAIL PROTECTED]OOGIS RL

JESS: Combining Jess and Java Beans

2004-05-27 Thread jabhi
Dear Ernest Friedman-Hill, Please tell me the detailed combination process of jess and java beans with help of examples. It will be great if you could refer me to some of lucid and useful stuff on the net with complete explanation of jess and java beans interaction. Thanking you, J.Abhishek

Re: JESS: Message: Bad index 53 in call to set() on this vector...

2004-05-27 Thread ejfried
I think [EMAIL PROTECTED] wrote: [Charset koi8-r unsupported, filtering to ASCII...] Hello, jess-users! Message: Bad index 53 in call to set() on this vector: (MAIN::object (is-a Questions: 1. What usually means this message? It means that Jess, for one reason or another, is trying

Re: JESS: Combining Jess and Java Beans

2004-05-27 Thread ejfried
I think [EMAIL PROTECTED] wrote: Please tell me the detailed combination process of jess and java beans with help of examples. It will be great if you could refer me to some of lucid and useful stuff on the net with complete explanation of jess and java beans interaction. See

JESS: Oh I feel like a gumby...

2004-05-27 Thread Simon Harris
Ok. So my next question is. Given I have say half-a-dozen different options describing some facts is it better to... (deftemplate foo (slot aBoolean) (slot anotherBoolean) ... etc.) or (deftemplate foo (multislot options)) or (deftemplate foo) (deftemplate

Re: JESS: Message: Bad index 53 in call to set() on this vector...

2004-05-27 Thread sorokinru
Hello, Ernest! Thank you for the answers. Please, specify an answer about a bug in an older version of Jess. I am using this version: 6.1 from 4/9/2003. Is it OK? Thanx once more. - Original Message - From: [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Thursday, May 27, 2004 4:53 PM

Re: JESS: Message: Bad index 53 in call to set() on this vector...

2004-05-27 Thread ejfried
I think [EMAIL PROTECTED] wrote: Hello, Ernest! Thank you for the answers. Please, specify an answer about a bug in an older version of Jess. I am using this version: 6.1 from 4/9/2003. Is it OK? Thanx once more. There have been seven patch levels released since them; 6.1p7 was released

Re: JESS: Oh I feel like a gumby...

2004-05-27 Thread ejfried
I think Simon Harris wrote: Ok. So my next question is. Given I have say half-a-dozen different options describing some facts is it better to... (deftemplate foo (slot aBoolean) (slot anotherBoolean) ... etc.) This is probably the best *if* the options change only rarely. or

Re: JESS: Oh I feel like a gumby...

2004-05-27 Thread Simon Harris
I think I'll stick with option one then. Regards, Simon On Thu, 27 May 2004 06:40:13 -0700 (PDT), [EMAIL PROTECTED] wrote: I think Simon Harris wrote: Ok. So my next question is. Given I have say half-a-dozen different options describing some facts is it better to... (deftemplate foo (slot

JESS: Getting a handle to the fact that matched given pattern

2004-05-27 Thread Amit Chopra
Hi all, I am trying to find the fact that matches a given pattern in rule. I tried something, but it wouldn't work. I want to do something like this (this does not work in Jess, its pseudocode). foo is a shadow fact of a java object that has a method, lets say, 'assign'. (defrule foo-res (foo

JESS: not understanding this error

2004-05-27 Thread Brenda K Hamilton
This is from my rules file, an example that produces the error: (import org.w3c.dom.*) (bind ?*nd* (fetch OBJ)) (defrule if-element (test (= (call ?*nd* nodetype) org.w3c.node.Node.ELEMENT_NODE)) = (printout t (call ?*nd* tagname) crlf) ) This is the error: Exception in thread main Jess

RE: JESS: not understanding this error

2004-05-27 Thread Jason Morris
Brenda, My guess is that you are using the = function when you should be using eq to compare object references. The = is for numerical values, hence the error. Hope this helps. -Jason - Jason Morris Morris Technical Solutions [EMAIL PROTECTED]

Re: JESS: Getting a handle to the fact that matched given pattern

2004-05-27 Thread ejfried
I think Amit Chopra wrote: [Charset iso-8859-1 unsupported, filtering to ASCII...] (defrule foo-res (foo (name ?x)) = (call 'fact that matched' assign)) I want to know how to find 'fact that matched' to be able to call assign on it. OK, two things. First, to get a reference to the

RE: JESS: Getting a handle to the fact that matched given pattern

2004-05-27 Thread Jason Morris
Amit, I just did something like this yesterday First I wrote a defquery as you suggested: (defquery find-foo-by-name (declare (variables ?name)) (foo (name ?name))) This returns an iterator of all foos with the given name Now, I added a function to wrap the query: (deffunction

RE: JESS: Getting a handle to the fact that matched given pattern

2004-05-27 Thread Jason Morris
Oops... I may have misunderstood your question. Sorry... completely mixed up my code. Disregard that last suggestion. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Amit Chopra Sent: Thursday, May 27, 2004 10:58 AM To: [EMAIL PROTECTED] Subject:

Re: JESS: Getting a handle to the fact that matched given pattern

2004-05-27 Thread Amit Chopra
Ernest and Jason, Thanks for replying, that should be adequate. amit. [EMAIL PROTECTED] wrote: I think Amit Chopra wrote: [Charset iso-8859-1 unsupported, filtering to ASCII...] (defrule foo-res (foo (name ?x)) = (call 'fact that matched' assign)) I want to know how to find 'fact that

RE: JESS: not understanding this error

2004-05-27 Thread Brenda K Hamilton
The call to nodetype should return an integer and ELEMENT_NODE is a short. I thought the '=' would be correct. On Thu, 2004-05-27 at 15:28, Jason Morris wrote: Brenda, My guess is that you are using the = function when you should be using eq to compare object references. The = is for

Re: JESS: not understanding this error

2004-05-27 Thread ejfried
I think Brenda K Hamilton wrote: The call to nodetype should return an integer and ELEMENT_NODE is a short. I thought the '=' would be correct. Ah. In Jess, org.w3c.node.Node.ELEMENT_NODE is just a symbol (an ATOM, as the error message says.) You want the ELEMENT_NODE member of the

JESS: Global variables and bags

2004-05-27 Thread fb
Hi, I would need a little help. I try to create a bag and bind it to a global variable. This works well. After a reset (set-reset-globals is set to true) the global variable still point to the bag and the bag content still exists. Here the code: (defglobal ?*QueryList* = (bag create

Re: JESS: Global variables and bags

2004-05-27 Thread ejfried
I think [EMAIL PROTECTED] wrote: Any suggestions? bag create returns an existing bag if there's already one by that name; reset doesn't clear the list of bags. Therefore, although the defglobal is indeed reset, it's reset to set to the same object! Note that all bag does is manage a Hashtable

Re: JESS: Global variables and bags

2004-05-27 Thread fb
Great! Works Thanks Felix On 27 May 2004 at 15:16, [EMAIL PROTECTED] wrote: I think [EMAIL PROTECTED] wrote: Any suggestions? bag create returns an existing bag if there's already one by that name; reset doesn't clear the list of bags. Therefore, although the defglobal is indeed

[no subject]

2004-05-27 Thread Simon Harris
I have some rules which assert facts based on the the non-existence of certain other facts. Those other facts may however come into exsistence based on other rules. Once again, I'm faced with a number of choices. Do/can I somehow use logical? I don't believe it's possible to use logical

JESS: Re: your mail

2004-05-27 Thread ejfried
I think Simon Harris wrote: Do/can I somehow use logical? I don't believe it's possible to use logical with not. You can, actually. (logical (not (foo))) acts as you'd expect. Or, is there another solution I've not thought of? I'm afraid I didn't understand the question, so perhaps

Re: JESS: Re: your mail

2004-05-27 Thread Simon Harris
Ahh. Quite right you are. I'm a fool! When JESS complained about Logical CEs can't follow non-logical what it really means is Logical CEs can't follow non-logical :-). I'll remember to read the messages more carefully next time. So I guess the question becomes: is it more effecient to use

Re: JESS: Re: your mail

2004-05-27 Thread ejfried
I think Simon Harris wrote: Ahh. Quite right you are. I'm a fool! When JESS complained about Logical CEs can't follow non-logical what it really means is Logical CEs can't follow non-logical :-). I'll remember to read the messages more carefully next time. Comprehensible error messages