Kinda of late for this but when I said before that it was a good idea
to get this into "core", why I meant was this, to be one of the
supported plugins distributed with core and the others.

I'm all +1 for it.

musachy

On 9/28/07, Ted Husted <[EMAIL PROTECTED]> wrote:
> +1
>
> As Don mentioned, we could also look at a combined Struts JAR which
> assembled Struts-Core and the standard plugns (like annotations), into
> a single JAR.
>
> I'd also like to start rolling 2.1.x soon, but I would suggest that
> this type of refactoring and API extension could continue in both the
> 2.0.x and 2.1.x series, so long as the changes do not remove existing
> API signatures that were not deprecated in a prior GA release.
>
> -Ted.
>
> On 9/24/07, Brian Pontarelli <[EMAIL PROTECTED]> wrote:
> >  So, here's my thought... I think a standard plugin that is part of the main
> > distribution might be best. This would contain all standard annotations and
> > the main implementation for them. And, as part of the plugin we define good
> > extension points to reduce the possible variations, but still allow changes.
> > Then if folks want to completely change the conventions, they can create
> > their own annotations and plugins and not cause too many conflicts. Also,
> > I'd like to possibly pull in some of the JSRs as already mentioned. I think
> > the validation annotations and a few of the others warrant some
> > investigation.
> >
> >  -bp
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>


-- 
"Hey you! Would you help me to carry the stone?" Pink Floyd

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to