You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@beehive.apache.org by "Rich Feit (JIRA)" <de...@beehive.apache.org> on 2005/10/19 02:06:45 UTC
[jira] Created: (BEEHIVE-976) button tag forwards to base class actions even when inheritLocalPaths=true
button tag forwards to base class actions even when inheritLocalPaths=true
--------------------------------------------------------------------------
Key: BEEHIVE-976
URL: http://issues.apache.org/jira/browse/BEEHIVE-976
Project: Beehive
Type: Bug
Components: NetUI
Versions: V1
Reporter: Rich Feit
Assigned to: Rich Feit
Fix For: 1.1
- In the attached set of page flows, hit the derived/Controller.jpf flow.
- Click the "baseAction1" link, which runs an inherited action that forwards to "base1.jsp", an inherited local path.
- On base1.jsp, click the "baseAction2" button (not anchor, which works fine). This should hit the inherited action "baseAction2".
EXPECTED: arrive at base2.jsp
ACTUAL: an error that says:
There is no Struts module configuration registered for /base/baseAction2.do (module path /base).
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
[jira] Updated: (BEEHIVE-976) button tag forwards to base class actions even when inheritLocalPaths=true
Posted by "Rich Feit (JIRA)" <de...@beehive.apache.org>.
[ http://issues.apache.org/jira/browse/BEEHIVE-976?page=all ]
Rich Feit updated BEEHIVE-976:
------------------------------
Attachment: bugs.zip
repro page flows
> button tag forwards to base class actions even when inheritLocalPaths=true
> --------------------------------------------------------------------------
>
> Key: BEEHIVE-976
> URL: http://issues.apache.org/jira/browse/BEEHIVE-976
> Project: Beehive
> Type: Bug
> Components: NetUI
> Versions: V1
> Reporter: Rich Feit
> Assignee: Rich Feit
> Fix For: 1.1
> Attachments: bugs.zip
>
> - In the attached set of page flows, hit the derived/Controller.jpf flow.
> - Click the "baseAction1" link, which runs an inherited action that forwards to "base1.jsp", an inherited local path.
> - On base1.jsp, click the "baseAction2" button (not anchor, which works fine). This should hit the inherited action "baseAction2".
> EXPECTED: arrive at base2.jsp
> ACTUAL: an error that says:
> There is no Struts module configuration registered for /base/baseAction2.do (module path /base).
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
[jira] Closed: (BEEHIVE-976) button tag forwards to base class actions even when inheritLocalPaths=true
Posted by "Rich Feit (JIRA)" <de...@beehive.apache.org>.
[ http://issues.apache.org/jira/browse/BEEHIVE-976?page=all ]
Rich Feit closed BEEHIVE-976:
-----------------------------
Resolution: Fixed
Assign To: (was: Rich Feit)
Fixed with revision 326356. I checked in an automated test for this -- closing.
> button tag forwards to base class actions even when inheritLocalPaths=true
> --------------------------------------------------------------------------
>
> Key: BEEHIVE-976
> URL: http://issues.apache.org/jira/browse/BEEHIVE-976
> Project: Beehive
> Type: Bug
> Components: NetUI
> Versions: V1
> Reporter: Rich Feit
> Fix For: 1.1
> Attachments: bugs.zip
>
> - In the attached set of page flows, hit the derived/Controller.jpf flow.
> - Click the "baseAction1" link, which runs an inherited action that forwards to "base1.jsp", an inherited local path.
> - On base1.jsp, click the "baseAction2" button (not anchor, which works fine). This should hit the inherited action "baseAction2".
> EXPECTED: arrive at base2.jsp
> ACTUAL: an error that says:
> There is no Struts module configuration registered for /base/baseAction2.do (module path /base).
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira