I think Florian Fischer wrote: > > But my objects have much more attributes than I need in the rules. I > would like to limit which attribute is visible to JESS. I can do that > to some extent by defining getters of the form getSomething(int dummy) > where the parameter is never used but prevents the attribute "something" > to appear in JESS. But that is not very clean. Is there a way to tell > JESS which attributes to read and which to ignore for a given Java class?
The standard JavaBeans way to do this is by providing a BeanInfo class; the BeanInfo class gets to define which properties exist for a particular Bean class. Jess will use a BeanInfo if you provide one, since Jess uses java.beans.Introspector to find the properties for a Bean class. --------------------------------------------------------- Ernest Friedman-Hill Advanced Software Research Phone: (925) 294-2154 Sandia National Labs FAX: (925) 294-2234 PO Box 969, MS 9012 [EMAIL PROTECTED] Livermore, CA 94550 http://herzberg.ca.sandia.gov -------------------------------------------------------------------- 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] --------------------------------------------------------------------
