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
Yes I agree KISS is better, Vic. It is better by the design.
Maybe you can be person to announce to the Struts 1.0
1.1 user base that all of their Actions are now invalid, they wont compile for Struts 2.0 because you need to upgrade ALL your state methods to get HttpServletRequest and HttpServletResponse and ActionForm and ActionMapping from the Chains context.
Both above method signatures above are not compatible!
But you could have a base class:
execute(context) {
execute(context.getReq(),context.getMapp(),...
}You could go the other way too, not at the same time
execte(req,resp,mapping,the4ththing) {
context = new Context();
context.setReq(req);
context.setMapping(mappping);
execute(context);
}
This is sort of what I do now in bP
So it can be compatible. Beside, we had perform and excute once, so users know.
Also, I imagine a long road to 2.0, people will be using nightly build for a while that only has the new stuff.
.V
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
