Especially obvious since it is clearly stated in Jess in Action.
Need to re-read it!
On Jul 22, 2006, at 4:35 PM, mdean77 wrote:
Very clear, thanks. Seems obvious in retrospect that Jess would
use the JVM classpath (not in Eclipse, but I do understand the
problems there.)
On Jul 22,
I am not trying to be dense, and you have been very helpful. I added the import statement and the rules file works properly in my Eclipse environment.My question is aimed at trying to understand why Jess knows from where to import Java classes on a given computer. That is,I could write Java
I think mdean77 wrote:
I am not trying to be dense, and you have been very helpful...
My question is aimed at trying to understand why Jess knows from
where to import Java classes on a given computer. That is,
I could write Java objects in any number of locations or programs on
a given
Very clear, thanks. Seems obvious in retrospect that Jess would use
the JVM classpath (not in Eclipse, but I do understand the problems
there.)
On Jul 22, 2006, at 3:18 PM, friedman_hill ernest j wrote:
I think mdean77 wrote:
I am not trying to be dense, and you have been very helpful...
I have a Jess file with a simple template for a patient:(deftemplate patient "Patient object - has age and weight" (slot age) (slot weight) (slot miscellaneous))and a simple template for a glucose measurement:(deftemplate currentGlucoseValue "Glucose level at current timepoint"
A template is in many ways like a class in Java and other
languages. Here are a few true and relevant statements about a template:
- It defines a datatype.
- It must be defined before it can be used
- If it is defined multiple times in a program, those definitions must
match exactly.
So the
This then raises the question of where do these classes need to be
for the Jess file to find them?
On Jul 21, 2006, at 8:46 AM, friedman_hill ernest j wrote:
A template is in many ways like a class in Java and other
languages. Here are a few true and relevant statements about a
template:
