On 11/13/05, Laurie Harper <[EMAIL PROTECTED]> wrote: > Well I initially proposed it back in September and took the lack of > objections to imply agreement...
At that point, it was an enhancement request from a user. It got one response from a committer which suggested an alternative approach. > > Given the size of the new dependency, can this be made configurable so > > that only the users who want to use this feature be required to add > > the 276k jar? After all, the original reason for the enhancement was > > to support "reusable components that must access form beans". IMO, > > this would really limit the audience that this feature targets. > > Well, that's the use case that prompted me but I think it simplifies the > use of dyna beans in any circumstance where you want to reference its > properties in a JSP. > > I could rework things to check for CGLIB in the classpath and revert to > the traditional behaviour if it's unavailable, though the documentation > would then need caveats about downloading/installing CGLIB to get the > functionality. > > L. Several items are "optional" even now. commons-validator, jakarta-oro, commons-fileupload, antlr. In each case, you'd have to use specific features before they become required. This change requires the new jar even if an app decides not to use the new feature. I guess I'm just not convinced that the new dependency is worth it, especially to something as basic as using DynaActionForm. This is why I'd +1 Joe's and Niall's suggestions. In either case, I'm hoping I can avoid having to include this in my app if I don't need the feature it provides. Hubert --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
