Re: [morph-developer] Copying Objects to Maps
Brought to you by:
orangeherbert,
sgarlatm
|
From: Matt S. <Mat...@wh...> - 2007-02-26 22:12:53
|
Matt Benson wrote: > Hmph--hadn't noticed the Spring file. :) This is > something I would like to think more about for the > long-term. I've been looking at this stuff for > several hours today (and once more revisited the > UNfruitful path of having SDT flat-out implement > NodeCopier, though I almost got there) and now I think > a tiny piece of effort that would have quite a bit of > yield would simply be a boolean > appendDefaultComponents flag for SDT. This would > greatly simplify Spring (or otherwise) configuration > of an application's top-level SDT where the developer > provides custom transformer implementations, but wants > to defer to Morph's default behavior for standard > cases. Hopefully this would cover >= 90% of what > developers would want to do, while still leaving the > door open for more complex configurations. > > "Make easy things easy and hard things possible." > Yes, it is a huge pain in the neck to customize the SDT because of the need to exactly duplicate the default transformers that come with Morph and make sure the custom transformers come before the built-in ones. I hadn't really considered adding a boolean flag like this, and I do agree it would be a very minor change with a very large benefit. I would also be in favor of the default value for the flag to be true. I believe SimpleDelegatingReflector would also benefit from a similar change. Matt S |