RE: [Springframework-rcp-dev] Beans

[Keith D. <kd...@cs...>]

Andy,

That's a good point.  I already have SetProperty and GetProperty function
objects that abstract away a particular access implementation.  I'll create
an enhancement in JIRA to make the bean binder configurable with different
process access strategies.

Keith

-----Original Message-----
From: spr...@li...
[mailto:spr...@li...] On Behalf Of
Andy Depue
Sent: Thursday, June 03, 2004 4:49 PM
To: spr...@li...
Subject: [Springframework-rcp-dev] Beans

I've noticed quite a bit of support in spring-rcp for JavaBeans and
properties 
(binding things to a property, setting up input rules for a property, etc).

This is great.  However, there are times when we work at a more "meta" level

than JavaBeans in a UI.  For example, some people use Maps of name/value 
pairs instead of JavaBeans, others might use DynaBeans (from Apache), and 
others might use service data objects, where you retreive property values
via 
get(propertyName) or set(propertyName, value) calls.  I believe it would be 
worth it to keep spring-rcp bean/property access generic enough that it
could 
be used with any kind of "object with properties" concept, and not tied to 
JavaBeans alone.  It could be something as simple as some sort of 
"PropertyAccessor" interface with a default  JavaBeans implementation.

Thoughts or comments?


-------------------------------------------------------
This SF.Net email is sponsored by the new InstallShield X.
>From Windows to Linux, servers to mobile, InstallShield X is the one
installation-authoring solution that does it all. Learn more and
evaluate today! http://www.installshield.com/Dev2Dev/0504
_______________________________________________
Springframework-rcp-dev mailing list
Spr...@li...
https://lists.sourceforge.net/lists/listinfo/springframework-rcp-dev