Sorry. I didn't read the code carefully.

I believe you could provide simple wrappers for these objects that conform
to the bean standard. These would forward/delegate all method calls to the
*real* object's methods/properties but provide the desired property change
events. Obviously, methods which have side effects would require
notification support from the underlying legacy non-bean.

A little wrapper code may be worth the tradeoff for cleaner rules and would
allow for migration away from the legacy interfaces.

This requires that you to have control over how your instances get created
so that you can inject the wrappers. Depending on your context, this may not
be possible.

Good luck!

alan

> -----Original Message-----
> From: David Young [mailto:[EMAIL PROTECTED]]
> Sent: Tuesday, September 12, 2000 11:33 AM
> To: [EMAIL PROTECTED]
> Cc: [EMAIL PROTECTED]
> Subject: Re: JESS: Reasoning over non-Bean objects
> 
> 
> Hello Alan.
> 
> >>>>> "Alan" == Alan Moore <[EMAIL PROTECTED]> writes:
> 
> Alan> You can still use jess with these objects even if they don't
> Alan> support PropertyChangeListener event firing (I *believe* that
> Alan> they must still conform to the naming conventions for bean
> Alan> properties - e.g. getXXX setXXX - someone please correct me here
> Alan> if I am wrong.)
> 
> Yes, I realize that. And, they do not. In other words, our existing
> classes are in no sense Beans (no getXXX, setXXX). Sorry for not
> making that clear.
> 
> Regards,
> 
> -- 
> 
> -------------------------------------------------------------
> David E. Young
> Fujitsu Network Communications  "The fact that ... we still
> ([EMAIL PROTECTED])         live well cannot ease the pain of
>                                  feeling that we no longer 
> live nobly."
>                                   -- John Updike
> "Programming should be fun,
>  programs should be beautiful"
>   -- P. Graham
> 
---------------------------------------------------------------------
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]
---------------------------------------------------------------------

Reply via email to