On Thursday, December 5, 2002, at 10:49 PM, Costin Manolache wrote:
it's the same old proposal. discussed at length a long time ago. have only one canonical set of basic reflection code that's easy to maintain and bug fix.I'm not sure I understand what is proposed :-)
the MethodUtil's public API is deeply flawed. it can't be maintained effectively since the methods do not have proper contracts.However I'm strongly -1 on removing ( or deprecating ) public code in beanutils, or on adding more dependencies.
it's an issue for me since i'm not willing to maintain, develop and support two separate basic reflection code bases. since errors are hard to track down, it's in everybody's best interests if as many components as possible shared the same reflection code.It works fine and if another package wants to do reflection - that's perfectly fine, but that doesn't mean everyone else is required to stop doing reflection.
i've been convinced that beanutils is not the right place for this code.If duplication is a concern - then just use beanutils ( however duplication is explicitely allowed in commons AFAIK).
the argument is that the basic low level reflection code should be able to be shared by all higher level introspection (beanutils) and components which use introspection-alternatives without having to depend on their peers. having to depend on beanutils is a major issue for some projects.
- robert
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
