|
From: Chris E. <chr...@co...> - 2004-09-25 03:26:48
|
IMO, the suggested solution introduces unnecessary complexity.
If the class isn't final, why not subclass it with something that is a
standard bean that knows how to translate standard bean settings to its
super?
If the class is final, a custom bean factory should do the trick.
katentim @hotmail.com wrote:
> Someone on the forum put forward a requirement for setting multiple
> arguments in a single method for legacy code. Method args. could be
> specified in a similar way to constructor args. While this is a move
> away from Beans, it's not a move away from IoC, POJOs or OO. What do
> others think?
>
> class SomeClass
> {
> public void setNamedValue(String name, Object value) {...};
> public Object getNamedValue(String name) {...};
> }
>
> _________________________________________________________________
> Click here for the latest chart ringtones:
> http://ringtones.com.au/ninemsn/control?page=/ninemsn/main.jsp
>
>
>
> -------------------------------------------------------
> This SF.Net email is sponsored by: YOU BE THE JUDGE. Be one of 170
> Project Admins to receive an Apple iPod Mini FREE for your judgement on
> who ports your project to Linux PPC the best. Sponsored by IBM.
> Deadline: Sept. 24. Go here: http://sf.net/ppc_contest.php
|