Re: JESS: JESS & EJB

[rhalsey007]

Title: RE: JESS: JESS & EJB

To Bryan and James,   Yeah, I have been curious about having the (JESS) engine maintaining its state over a number of execution cycles.   One application that I have is only processing one new fact each time, but I have a number of facts (JavaBeans) that implement the "interface" into an application. These I want to remain in memory for matches against the newly asserted fact during a cycle. The RETE class in JESS implements the Serializable interface, so I guess I will have to come up with a "Bean Managed Persistence" approach to serialize the state of the engine if I put JESS inside a Stateful Bean. Something in my memory of this mailing list tells me that Earnest explained this once before. I am VERY new to J2EE, so I have to ask questions like I did today.   Thanks,   Rich Halsey ----- Original Message ----- From: Bryan Talbot To: '[EMAIL PROTECTED]' Sent: Thursday, February 28, 2002 4:38 PM Subject: RE: JESS: JESS & EJB -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 My application uses a fairly static set of rules to process an XML document describing a business transaction.  Each document is processed individually and the rule engine is reset before each processing cycle.  So, I don't have a need for long term access to the same rule engine state that you seem to have. I'm not sure what my solution to solve that problem would be since I haven't looked at it much; I've been lucky and able to avoid using state full session beans. - -Bryan >-----Original Message----- >From: James Patterson [mailto:[EMAIL PROTECTED]] >Sent: Thursday, February 28, 2002 2:08 PM >To: [EMAIL PROTECTED] >Subject: Re: JESS: JESS & EJB > > >I'm curious what type of applications you guys are using the >engine for.  We are investigating the JMX route because of the >"normal" EJB rules.  For example, how do manage state?  The >engine use we are working toward is going to be a >run-all-the-time service.  Just because the engine maybe quite >for a given time, I can't have the container running around >trying to kill it off.  Now, I admit to being a bit >under-acquainted with J2EE as a whole, but how else does one >use/model the engine? I suppose if your rule base were small >enough and a persistent state was not required for long >periods of time, things might be more straight forward?  Comments? > >James > > -----BEGIN PGP SIGNATURE----- Version: PGP Personal Privacy 6.5.2 iQA/AwUBPH6xeUzuKKcxAa+OEQLbbQCgnEKW7mLeTB/Yr/LEh3XCr6h5Qg8AoJoT x+iMyz/V2Fh4AGQPqmz8tdF5 =gEx6 -----END PGP SIGNATURE-----