Ah... can someone educate me as to why not just subclass chain context, would it not let you just do the same thing you said bellow?
(and w/o servlet api).


.V


Don Brown wrote:

The summary of our discussion, as I understand it, would be to create a ActionContext, which would not be a subclass of any commons-chain contexts, but would contain the commons-chain, probably WebContext instance available via a getter. This would allow us to have one ActionContext instance, and not have to subclass the different faces, portlet, and servlet instances. The Action class would be replaced by an Actionable (name not decided) interface which would have one method, execute(ActionContext ctx). This ActionContext would also have basically all the methods from Action like saveToken(), etc.

Don



--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]



Reply via email to