Greetings, New here. Been eval'ing Blaze, ILOG, and now we're onto JESS. Saving the best for last. I read the discussion a few months back between Greg Ball and Rainer Schmitz and ejfried. The notion of using an ExpertSystemAdapter class makes sense. What we are wondering now is how do we store facts. We will need to create a UI in JSP for business users to modify facts. These will be based on Java classes; business users will change the properties. We would like these classes to be listened to by JESS. Can we use database and Entity beans to store facts? We understand that the Entity bean would need some sort of PropertyChangeSupport, but we don't want to change our underlying database to include this class in the underlying table. Can an Entity bean serve as a dynamic "Fact Object' and notify the JESS listeners, or must we use some other architecture? Any thoughts? Thanks, mark http://www.mail-archive.com/[email protected]/msg02072.html -- Mark Lilly Consonus Inc. 6650 Redwood Lane, Suite 160 Portland, OR 97224 work: 503.670.4800 ext. 221 fax: 503.670.1795 [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, send the words 'unsubscribe jess-users [EMAIL PROTECTED]' in the BODY of a message to [EMAIL PROTECTED], NOT to the list (use your own address!) List problems? Notify [EMAIL PROTECTED] ---------------------------------------------------------------------
