Menu
▾
▴
Re: [Springframework-rcp-dev] Beans
|
From: Andy D. <an...@ma...> - 2004-06-03 22:16:14
|
The use of JavaBeans for configuration is not what I'm referring to. I too would not want to change the way Spring performs configuration based on standard JavaBeans. What I'm referring to is actual GUI components provided by the spring-rcp project that make it easy to view and edit JavaBean properties from within a UI. For example, spring-rcp provides a dialog that allows you to pass in a JavaBean and a property name. The input dialog will then automatically prompt the user for the value of the property and automatically assign that value to the property on the JavaBean. If my GUI application happens to use some other mechanism for representing business data (such as a ResultSet, a service data object, or a Map), then I can't use spring-rcp's nifty input dialog anymore. On Thursday 03 June 2004 02:35 pm, Ronald Haring wrote: > I'm not sure if I speak out of line, but the complete basis of the > spring framework is build around javabeans, so that would explain why > there are no dynabeans involved, and frankly, I dont think we need it. > The spring is used mostly to configure things and with most configure > properties, you are pretty sure what their names will be. Where would > you want to use the javabeans for in the spring-rcp using maps? Btw, you > can fill maps by using > <bean id="whatever" class="mybean.with.maps"> > <property name='theMap"> > <props> > <property key="someKey">somevalue</property> > <property key="anotherKey">anothervalue</property> > </props> > </property> > </bean> > > Cheers > Ronald > > Andy Depue wrote: > >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 > > ------------------------------------------------------- > 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 |
