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.
I aqgree that DAO should be outside of Sturts.
I do not think Workflow should be inside. Becuase I do not think it is a good practice. It may be needed by some people... as a plug in.
Integrating StrutsTestCase would help with the Unit tests,
although it will have to be heavily modified in parallel
to keep up with changes in development.
I also do not think testing should be insdide. There are many that look into JVM, into container's JSP, etc. and people should inovate.
I use OpenSTA, becuase I want to see what happens under load.
However... Monitoring and Managing the application while runing in production maybe should be included. Ex: Jamon.
I used it, and it's great.
I works similar to log4j.
Or at least it should be documented.
In days of ClientServer, 3 tier ment:
Data Layer, Presentation Layer and Managment Layer.
So you no longer going to pass in request and response objects
around, but instead have a context instead. Maybe it would
be a little inconvenient for every Action to call ``context.getRequest()'' all the time. Perhaps we can keep them
please. I dont mind losing the form bean. I could live with
``context.getForm()'', because for some environments you dont
need to buffer a user's input. e.g. web services, or even a flat file.
public ActionForward someStateAction( org.apache.commons.chain.Context context,
some.generic.request request,
some.generic.response response );
Why not just KISS and public ActionForward someStateAction( org.apache.commons.chain.Context context );
It can *all* go into context(or a Map!!!), else we have the tilesAction execute signature.
I can allways do a
map.get("request")This would work for SOAP or other protocols.
.V
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
