Thanks for the pointers Henri. I'll post the changes in Bugzilla as soon as I could.
Right now, I'm formatting the java code to follow the current code formatting. However, I couldn't find no Jalopy .codestyle file on the Internet that would allow me to accelerate this process. Regards, Gabriel 2006/5/4, Henri Yandell <[EMAIL PROTECTED]>:
On 5/3/06, Gabriel Belingueres <[EMAIL PROTECTED]> wrote: > Hi, > > I'd like to know if there are any prospects on aligning the beanutils with JSTL. I'm not sure if there are many plans with BeanUtils, it's in need of love. > AFAIK, DynaBeans currently do not work with JSTL standard because > there is no accessor to the values Map variable from the outside, so > you have to subclass BasicDynaBean and put an accessor to the values > Map to use it from a JSP page. This sounds like a valuable change to DynaBeans to me. > Also, since I'm working a lot with the (disconected) RowSetDynaClass, > and this creates by default BasicDynaBeans, I have to subclass > RowSetDynaClass so as to overwrite the createDynaBean() method, but > there is no information on the javadocs that tell that we can safelly > do that without loosing forward compatibility with future beanutils > releases. > > I downloaded the beanutils source code and very easily I created an > abstract class (let's call it AbstractRowSetDynaClass) that has an > abstract protected DynaBean createDynaBean() method, and then create > RowSetDynaClass by subclassing AbstractRowSetDynaClass, with the > current implementation of the createDynaBean() method. This way, there > are no loss of backward compatibility in the RowSetDynaClass class AND > the design intent is clearly specified so that anyone is allowed to > safely replace the dynabean kind created, and this information is > easily found by reading the javadocs. Probably worth doing, though need to see which methods should go in the implementation and which in the abstract. > I have already implemented those changes in the source code...don't > know if anyone is interested in them. Always interested. Making a Bugzilla issue and attaching as a patch will at the very, very worst sit in there for other users to find. More likely, it will sit in there for a bit until someone pushes a bunch of bits into a new release of BeanUtils - and it will help build the critical mass to nudge someone into wanting to do that. Hen --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
