+1
I think that this plugin is of great worth to every day development. I would
like to echo some other people's sentiments that a unified plugin would be a
significant value add to new struts developers. I know that there is much
overlap and confusion between:
1. Zero-config
2. Code behind
3. Smart urls
4. REST
5. Convention
It took me a while to mentally model the differences / similarities between
them all , and surely I can't be the only one :)
I understand that ideally plugins should have high cohesion and low coupling...
but having so many options does more harm than good in this case. IMO this is
an example of plugin fragmentation that should be resolved with a unified,
best-of-breed approach, leaving the other plugins as they are for those
concerned about deprecation.
Bob
> Date: Tue, 13 May 2008 23:39:39 -0400> From: [EMAIL PROTECTED]> To:
> dev@struts.apache.org> Subject: [VOTE] Bring Convention plugin into trunk and
> deprecate Zero Config> > With the addition of @IntereceptorRefs to the
> Convention plugin, it is> now possible to do most of the action mapping using
> annotations. Also> having 2 plugins to do the same thing is really confusing
> for users,> so we should deprecate Zero Config (good thing is that it was
> always> "experimental").> > If you have had a chance to look at the
> Convention plugin, please vote:> > [+1] Move the Convention plugin to trunk
> and deprecate Zero Configuration plugin> [-1] Leave it in sandbox.
> (reasons?)> > > regards> musachy> -- > "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]>
_________________________________________________________________
