* Split out file upload handling into a separate pluggable component, with its own configuration. I noticed that this is still in the initial Jericho DTD, but I think it should not be. The file upload implementation is pluggable, and so should be able to have its own config definition.
Feel free to amend that if you like. I've so far managed to avoid file uploading in Struts applications, and so remain blissfully ignorant of the grittier details.
A sort of meta-question: When is Struts no longer Struts? I mean, how much change can we introduce in Struts 2.0 before it becomes so different that it's really a different framework? Do we need to decide on what Struts is, and is not, before we go too far down the path of Struts 2.0? Or do we let whatever falls out just fall out and deal with it later?
Legally, I'd say that Strut is whatever the Struts Community says it is. It's a brand that belongs to the ASF, which we manage on the Foundation's behalf.
Technically, I'd say that Struts (or any framework) is an aggregation of its components. In Struts 1.0, we had mainly Form, Forward, Mapping, Action, and Messaging components. In Struts 1.1, we added Exception, Validation, Composite (or Tile), and PlugIn components.
So long as Struts 2.x retains the same hallmark components in a recognizable form, I'd say it's still Struts. :)
Overall, it's my feeling that Struts does all the right things, it's just that we don't do them in all the right places. :) Being able to extend elements is one example. Encapsulating paths is another.
My own goal for Struts 2.x is to consistently apply all our best practices and eliminate inconsistent and legacy practices. We've got a good thing here; we just need to make it even better. :)
In terms of new functionality, the three biggest fish I'd like to fry are Workflow, SSL, and Unit Testing. Towards that end, I'd like to consider integrating LivingLogic's Workflow, ssl-ext, and Struts TestCase into the Struts 2.x development stream. We may also want to consider adding these as standard options to Struts 1.x, so as to blaze a trail.
Although it's not evident from the Jericho DTD, the intention is to use a Context object in the signatures, perhaps the Commons Chain Context, so as to encapsulate Servlet/Portlet dependencies.
-Ted.
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
