Hi Jason, not seeing your code I can only guess that your (update) call uses the shadow fact as an argument and not the underlying bean object.
@Ernest: Perhaps it's possible to either redirect this call to the OBJECT slot, or at least check in the its-not-a-definstance-error branch whether it's a Fact object, and notify the user accordingly. Wolfgang On Mon, Mar 30, 2009 at 4:32 AM, Jason Morris <[email protected]>wrote: > Hi Ernest, > > I asserted a bean into working memory via (add) using its default > behavior. Right now, the bean does not have PropertyChangeSupport > wired up. > Now, I've added a call to (update) at the end of rules that modify > this bean so as to manually update the underlying shadow fact as the > docs suggest (See 5.3.3. Responding to changes). > > However, when I run the app, I <generically> get: > > Jess reported an error in routine DefinstanceList.getShadowFactForObject > while executing (update ?fact) > while executing defrule ... > Message: Object not a definstance: > > Now, I thought that was odd, since the docs say that (add) is just a > general form of (definstance), so I'd expect my add-ed bean to be a > definstance nonetheless. > What am I missing? > > Cheers, > Jason > > ----------------------------------------------------------- > Morris Technical Solutions LLC > [email protected] > (517) 304-5883 > > > -------------------------------------------------------------------- > 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]. > -------------------------------------------------------------------- > >
