On 10/26/07, Ernest Friedman-Hill <[EMAIL PROTECTED]> wrote:
>
> To use reflection on a class (which the JessDE will do now, because
> it uses ReflectionClassResearcher), you have to load the class. That
> means that if, say, you're editing a file that includes "(defclass
> Foo Foo)", that your cla
To use reflection on a class (which the JessDE will do now, because
it uses ReflectionClassResearcher), you have to load the class. That
means that if, say, you're editing a file that includes "(defclass
Foo Foo)", that your class Foo will be loaded into Eclipse. Normally,
this isn't a big
Can you rely on Jess ClassResearcher and whatever is used under Eclipse
to always produce the same result?
Granted (and I do assume) that you can: What is the benefit of using
some JDE library function as compared to the ClassResearcher? It can't
be a performance issue, because obtaining the templ
Interesting idea! I hadn't thought about ClassResearcher as a user
hook; It was introduced as a way to let Jess use reflection most of
the time, but use Eclipse's JDE libraries inside the JessDE so that
the JessDE doesn't actually load your classes. Therefore this must be
used cautiously be
Deriving a deftemplate from a Java class with, e.g.,
(deftemplate Account (declare (from-class Account)))
invariably adds a slot "class", due to getClass() inherited from
java.lang.Object.
If you want to get rid of this, see the Jess userfunction I've added to the
Jess Wiki:
http://herzberg.ca.
