shale-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Mike Meessen (JIRA)" <>
Subject [jira] Created: (SHALE-287) Faulty behavior of the "token" component with Apache MyFaces >1.1.1
Date Mon, 18 Sep 2006 10:05:31 GMT
Faulty behavior of the "token" component with Apache MyFaces >1.1.1

                 Key: SHALE-287
             Project: Shale
          Issue Type: Bug
          Components: Core
    Affects Versions: 1.0.3, 1.0.4-SNAPSHOT
         Environment: OS: Microsoft Windows XP SP2
Servlet Container: jakarta-tomcat-5.5.9
            Reporter: Mike Meessen

This issue appears when using Apache MyFaces as of version 1.1.2. The MyFaces project states
the following about their 1.1.2 release:

This is the first official release of what we are now calling the "core." The core refers
to the JSF 1.1 implementation as specified by JSR-127. It has passed Sun's TCK and is considered
to be 100% compliant with the spec.

So as a conclusion, I think everyone who's still using MyFaces 1.1.1 should hurry upgrading
his code to be 1.1.2 compliant.
Allthough Shale should be JSF-implementation-independant, it seems this issue appears or not
depending on the used MyFaces version.

Steps to reproduce the issue:

* Use a simple JSF submission form to which you add Shale's Token tag to check for illegal
form resubmissions.
* As long as you submit the form correctly, everyting works fine.
* Press F5 (page refresh) once, the browser warns about HTTP POST data resubmission.
* Discard the warning and go on resending the same HTTP request.
* Shale recognizes the resubmission and acts correctly (no application logic gets invoked).

**** This is the part where the behavior changes according to what MyFaces version is used:

With MyFaces 1.1.1

* Resubmit the form correctly (using the submit button).
==> The workflow goes on and the form is correctly submitted.

With MyFaces 1.1.2 and above

* Resubmit the form correctly (using the submit button).
==> Nothing happens. No new token is generated, so no application logic gets invoked and
the workflow stucks.

I attached a sample project which demoes the issue.


This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
For more information on JIRA, see:


View raw message