If we are talking about the struts-extras JAR, then why not encapsulate all this in an struts-extras package that people can include when they include the extras JAR.
One of the remarkable things about Struts 2 is how easiy it is to add your own interceptor or your own result. We should encourage people to help themselves, and try to break out of the mindset that Struts is a blackbox. Distributing the Extras as an optional plugin, that is not directly linked to the core, is an excellent opportunity to show people how easy it is to extend Struts, without touching the original distribution. -Ted. On 8/30/06, Don Brown <[EMAIL PROTECTED]> wrote:
I believe that Struts should work, out of the box, to require as little effort as possible. We want to make things easier right? Well, a good place to start is to build in functionality that can be used as easily as possible. This means: - To use Struts Extras features, just add the jar. No extra configuration/work required. - The default stack should do just about anything you need it to do. Only the most advanced users will need to create their own interceptors and stacks. - Custom struts.xml shouldn't be needed for most apps. By adopting Able-style conventions, a new user should be able to throw the Struts jar in, write an Action, and write a JSP. No need to read cryptic reference docs or learn new XML schemas to throw up a simple app. Sure, each of these things, by themselves, could be debated and aren't strictly necessary, but taken as a whole, they represent a significant effort to make development easy. It is that overarching vision that I think we are lacking here, choosing rather to debate all these minor features, which will result in a framework that reflects its confused development. Don
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
