I think Jason Morris wrote:
In fact, by using Swing's trees from my Jess code, I could attach a user
object to each DefaultMutableTreeNode and manipulate it via
getUserObject()/setUserObject(). In my case, the user object becomes a Jess
fact reference (or anything else I want to stick in
Hi All,
I just wanted to squash my previous query about adding a native, general
purpose, tree storage mechanism to Jess. It's not needed -- Jess's
flexibility lets you build pretty much anything you want.
For example, I successfully tried:
a) Cross-linking facts containing Jess multislots
