On Tue, 17 Apr 2001, Incze Lajos wrote:
> > Port a fix from the "commons" version of this module (which Struts will
> > ultimately migrate to when the commons version is released).
> >
>
> Just some questions. Will the beanutils be facotred out from struts
> or they will remain here (with some sort of sync mechanism)? Also,
> are there other candidates to be factored out to commons (e.g.
> digester)? incze
>
We haven't talked much here on STRUTS-DEV about the "Commons" project -- I
suggest that people take a look:
http://jakarta.apache.org/commons
and subscribe to the JAKARTA-COMMONS mailing list if they are
interested. The basic idea is to make it easier to share components of
existing Jakarta subprojects with the other subprojects (and vice
versa). My initial contributions have been the bean utilities classes and
the Digester.
IMHO, we're too close to a 1.0 final release to go mucking around with
APIs people are currently depending on. Therefore, the approach I'd like
to take is:
* For Struts 1.0 continue to use the internal versions of beanutils
and digester, but deprecate them (manually synching changes as
appropriate).
* For Struts 1.1, remove the internal versions and migrate to the
new ones in Commons.
* If any additional pieces of Struts get factored out, follow the same
basic strategy.
It is also possible that some of the functionality on the 1.1 TODO list
will be implemented (at least partially) as Commons packages, to the
extent that it is general purpose in nature and not dependent on the
Struts framework.
Craig
