Alex:
Yes. I get it now. My BeanConverter can pull the bean from
*ObjectConverter's* object using ReflectionUtils (same as
ObjectConverter had just done before calling my BeanConverter).
Its slightly redundant (repeating the reflection), but my BeanConverter
gets more information doing your way.
Thanks for the help.
-- Dan
Dan I understand your point, but here is my argument to pass the
original object and not the bean only:
if I pass you only the bean than you don't have any reference back to
the original object, and if your bean converter needs more logic to do
the insert/update (which may happen a lot of times) than you have no
chance to do this.
My idea was that by passing the original object and the beandescriptor
so that you know exactly on what property your code is invoked than
you can do a bunch more things.
Does this help?
./alex
--
.w( the_mindstorm )p.
