On Mon, 21 May 2001, Martin Cooper wrote:
> The BeanUtils and PropertyUtils classes are marked as deprecated in Beta 2.
> I understand that this is because they will be replaced by the Jakarta
> Commons versions for Struts 1.0. However, it seems that I am now left in a
> situation in which I have to disable deprecations in my build, or live with
> warnings about these classes until Struts 1.0 is released.
>
> In previous situations in which particular methods were deprecated in
> Struts, there was an appropriate alternative to avoid the deprecation. As
> far as I can tell, there is no such alternative in this case. Is this true,
> or is there something I can do to fix the warnings?
>
I think this is primarily a timing question.
The Commons versions of the beanutils classes has not been "released" yet
(although I have some influence on when that happens). Once it's
released, my plan is to include the appropriate JAR files
(commons-beanutils.jar and commons-collections.jar) with Struts so that
people can start using the new classes. In addition, I can switch over
the internal Struts classes to use these JARs (low risk, since beta-2
includes identical source code except for the package name).
Let me see what I can do to get a 1.0 release of commons-beanutils and
commons-collections out the door, so I can feel comfortable in migrating
Struts to it (and including them in the release) prior to Struts 1.0
final.
> Thanks!
>
> --
> Martin Cooper
>
>
>
Craig
