You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@struts.apache.org by "Paul Benedict (JIRA)" <ji...@apache.org> on 2009/05/04 05:59:30 UTC

[jira] Closed: (STR-3175) Struts "process-action" chain should not depend on ServletActionContext because ServletActionContext is not an interface.

     [ https://issues.apache.org/struts/browse/STR-3175?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Paul Benedict closed STR-3175.
------------------------------

    Resolution: Won't Fix
      Assignee: Paul Benedict

This issue cannot be fixed without breaking backwards compatibility. It's one of those things that a developer would say "if I only knew that then I wouldn't have coded it that way", and Struts 1.x thrives on full backwards compatibility.

> Struts "process-action" chain should not depend on ServletActionContext because ServletActionContext is not an interface.
> -------------------------------------------------------------------------------------------------------------------------
>
>                 Key: STR-3175
>                 URL: https://issues.apache.org/struts/browse/STR-3175
>             Project: Struts 1
>          Issue Type: Improvement
>         Environment: n/a
>            Reporter: ori
>            Assignee: Paul Benedict
>
> Several commands in package org.apache.struts.chain.commands.servlet depend on the specified context being an instance of ServletActionContext which is not an interface.
> Users that wish to use a custom ActionContext implementation must subclass ServletActionContext, which is not ideal.
> It would be much easier to have interfaces for ServletContext and WebContext and require that the context be an instance of those interfaces. I've opened up an issue with the chain project for this:
> See http://issues.apache.org/jira/browse/CHAIN-47

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.