Mapping constants to integer could, for example, easily be done such.
The declarative way that I was believing to be good would be to make a conversion-context class, presumably in beanutils, which would be a set of mappers. It could be called for copy (or set)Property just the static calls currently except, it could be configurable!
Now, maybe such mappers would actually be slow things to load... I don't know...
Instead we have subclass-based attribute-conversion parametrization currently as in UseBean, right ?
paul
Le 10 sept. 04, � 22:59, Hans Gilde a �crit :
This is supported in a generic way by the jelly UseBeanTag and used in
several places like the Swing tags. The way it's supported may look a little inelegant in the code but I agree that it's certainly not due to some huge deficiency in the BeanUtils.
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
