Another thing to keep in mind here... The way the conventions plugin works is that it hooks in UnknownHandlers. If conventions is to become the new default, I think a classpath-scanning ConfigurationProvider should be created (IMHO).
-Wes On Tue, Mar 15, 2011 at 4:26 PM, Philip Luppens <philip.lupp...@gmail.com> wrote: > On Tue, Mar 15, 2011 at 9:13 PM, Ben McCann <bmcc...@google.com> wrote: >> I didn't realize you could setup Struts2 without XML. That sounds fantastic >> to me. I'd vote in favor of moving it to the core or at least highlighting >> it in the documentation. Having to do configuration in XML is the one thing >> I dislike about Struts2 despite being a longtime and happy user of the >> framework. I much prefer doing configuration in code or via annotations. >> FYI, Matt, I've been using extensionless URLs with Struts2 for awhile >> without the plugin. Try doing something like <constant >> name="struts.action.extension" value="action,,"/> >> >> [snip] >> > > Funny, for me it's the exact opposite: I much prefer to have my > configuration done in XML. Centralized (but split up per role, for > example), easily searchable, bulk operations, changeable without > requiring recompilations, ... especially for larger or fast-moving > applications, the XML configuration files are much clearer than the > annotation counterpart. > > My 2 cents, > > Phil > > > > -- > "We cannot change the cards we are dealt, just how we play the hand." > - Randy Pausch > -- Wes Wannemacher Head Engineer, WanTii, Inc. Need Training? Struts, Spring, Maven, Tomcat... Ask me for a quote! --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@struts.apache.org For additional commands, e-mail: dev-h...@struts.apache.org
