[Figleaf-developer] current state of Introspector

[Greg S. <ste...@on...>]

Hi Sam,

I was having a look at your introspector code again. We might rethink 
how to handle multiple interfaces. For instance what if I have a class 
that implements all of Informative, but it is a helper class not the 
"real" class? Perhaps we need to look for a class called 
o.getClass().getName()+"Informative" and it must implement Informative. 
Also this helper class will probably need to get a reference to the 
underlyingObject at some point in order to do its work correctly. We 
might want to impose that these helper classes have a single parameter 
constructor that takes the underlying object as argument.

In InformativeImpl you have implemented change listeners, but it looks 
like only if the caller invokes setProperty(String propertyName, Object 
value). But that method isn't in any interfaces, so I don't think it'll 
ever get called. I think the listener functionality needs to be placed 
in the proxy implementation, in the InformativeCallbacks method.

If it's ok with you, I can make these changes and reduce some of the 
redundancy between the interfaces I made and the ones you made.

Greg

P.S. I still only get some of the mails sent to the list, so it's best 
to CC me for now.