You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@beehive.apache.org by "Jeremiah Johnson (JIRA)" <be...@incubator.apache.org> on 2005/02/02 19:19:17 UTC
[jira] Created: (BEEHIVE-231) Discuss Jpf.NavigateTo.currentPage expected behavior
Discuss Jpf.NavigateTo.currentPage expected behavior
----------------------------------------------------
Key: BEEHIVE-231
URL: http://issues.apache.org/jira/browse/BEEHIVE-231
Project: Beehive
Type: Task
Components: NetUI
Environment: This bug was discovered on Fedora Linux using Tomcat 5.0.25.
Reporter: Jeremiah Johnson
Priority: Minor
It doesn't sound like the expected behavior has been defined for how Jpf.NavigateTo.currentPage should work in relation to back-button use, so I am entering this Jira task to ensure that the question gets addressed. If a user hits the back button (from page B, for example) to get to page A and then causes an action on that page (page A, again) to forward to Jpf.NavigateTo.currentPage, then the user will go to page B. When I ran across this case, I expected to see an updated page A rather than go to page B.
I wish that I could say all of that more clearly, but I figure that it may be more helpful to attach a sample. I will attach a sample to clarify.
- jeremiah
--
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
-
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
[jira] Updated: (BEEHIVE-231) Discuss Jpf.NavigateTo.currentPage expected behavior
Posted by "Rich Feit (JIRA)" <be...@incubator.apache.org>.
[ http://issues.apache.org/jira/browse/BEEHIVE-231?page=history ]
Rich Feit updated BEEHIVE-231:
------------------------------
Version: V1Alpha
V1Beta
Fix Version: V1
One workaround is to prevent caching of pages forwarded to from actions. In WEB-INF/netui-config.xml, you'd put this:
<pageflow-config>
<prevent-cache>always</prevent-cache>
</pageflow-config>
This issue does deserve some thought, though. It may be possible to add a token parameter to each rendered form/anchor, to help the server keep track of what's going on.
> Discuss Jpf.NavigateTo.currentPage expected behavior
> ----------------------------------------------------
>
> Key: BEEHIVE-231
> URL: http://issues.apache.org/jira/browse/BEEHIVE-231
> Project: Beehive
> Type: Task
> Components: NetUI
> Versions: V1Alpha, V1Beta
> Environment: This bug was discovered on Fedora Linux using Tomcat 5.0.25.
> Reporter: Jeremiah Johnson
> Assignee: Rich Feit
> Priority: Minor
> Fix For: V1
> Attachments: BEEHIVE-231.tar
>
> It doesn't sound like the expected behavior has been defined for how Jpf.NavigateTo.currentPage should work in relation to back-button use, so I am entering this Jira task to ensure that the question gets addressed. If a user hits the back button (from page B, for example) to get to page A and then causes an action on that page (page A, again) to forward to Jpf.NavigateTo.currentPage, then the user will go to page B. When I ran across this case, I expected to see an updated page A rather than go to page B.
> I wish that I could say all of that more clearly, but I figure that it may be more helpful to attach a sample. I will attach a sample to clarify.
> - jeremiah
--
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
-
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
[jira] Updated: (BEEHIVE-231) Discuss Jpf.NavigateTo.currentPage expected behavior
Posted by "Jeremiah Johnson (JIRA)" <be...@incubator.apache.org>.
[ http://issues.apache.org/jira/browse/BEEHIVE-231?page=history ]
Jeremiah Johnson updated BEEHIVE-231:
-------------------------------------
Attachment: BEEHIVE-231.tar
Here are the steps that I would recommend for the attached file:
$ tar xf BEEHIVE-231.tar
$ cd BEEHIVE-231
$ ant -f /home/jjohnson/projects/beehive/build/dist/apache-beehive-incubating-svn-snapshot/ant/webappRuntimeCore.xml -Dwebapp.dir=/home/jjohnson/projects/BEEHIVE-231 deploy.beehive.webapp.runtime
$ ant -f /home/jjohnson/projects/beehive/build/dist/apache-beehive-incubating-svn-snapshot/ant/buildWebapp.xml -Dwebapp.dir=/home/jjohnson/projects/BEEHIVE-231 build
$ jar cf BEEHIVE-231.war *
$ mv BEEHIVE-231.war $CATALINA_HOME/webapps
Then point your browser at http://localhost:8080/BEEHIVE-231/
You should see a page with a couple links that shows, 'You are on the Index page.'
Click on the link labeled, 'Update this page.', then you should just see the page refresh.
Click on the link labeled, 'Go to the next page.', and the page should change and show, 'This is the Next page.'
Now click the back button to get back to the index page.
Click on the link labeled, 'Update this page.', and you will see the next page.
- jeremiah
> Discuss Jpf.NavigateTo.currentPage expected behavior
> ----------------------------------------------------
>
> Key: BEEHIVE-231
> URL: http://issues.apache.org/jira/browse/BEEHIVE-231
> Project: Beehive
> Type: Task
> Components: NetUI
> Environment: This bug was discovered on Fedora Linux using Tomcat 5.0.25.
> Reporter: Jeremiah Johnson
> Priority: Minor
> Attachments: BEEHIVE-231.tar
>
> It doesn't sound like the expected behavior has been defined for how Jpf.NavigateTo.currentPage should work in relation to back-button use, so I am entering this Jira task to ensure that the question gets addressed. If a user hits the back button (from page B, for example) to get to page A and then causes an action on that page (page A, again) to forward to Jpf.NavigateTo.currentPage, then the user will go to page B. When I ran across this case, I expected to see an updated page A rather than go to page B.
> I wish that I could say all of that more clearly, but I figure that it may be more helpful to attach a sample. I will attach a sample to clarify.
> - jeremiah
--
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
-
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
[jira] Updated: (BEEHIVE-231) Discuss Jpf.NavigateTo.currentPage expected behavior
Posted by "Rich Feit (JIRA)" <be...@incubator.apache.org>.
[ http://issues.apache.org/jira/browse/BEEHIVE-231?page=history ]
Rich Feit updated BEEHIVE-231:
------------------------------
Fix Version: TBD
(was: V1)
I definitely think this needs to be addressed -- I just don't think we can do it in the v1 timeframe. One possible options is to submit a token per-page (perhaps optionally) -- this could be compared to what the server thinks is the most recent page.
> Discuss Jpf.NavigateTo.currentPage expected behavior
> ----------------------------------------------------
>
> Key: BEEHIVE-231
> URL: http://issues.apache.org/jira/browse/BEEHIVE-231
> Project: Beehive
> Type: Task
> Components: NetUI
> Versions: V1Alpha, V1Beta
> Environment: This bug was discovered on Fedora Linux using Tomcat 5.0.25.
> Reporter: Jeremiah Johnson
> Assignee: Rich Feit
> Priority: Minor
> Fix For: TBD
> Attachments: BEEHIVE-231.tar
>
> It doesn't sound like the expected behavior has been defined for how Jpf.NavigateTo.currentPage should work in relation to back-button use, so I am entering this Jira task to ensure that the question gets addressed. If a user hits the back button (from page B, for example) to get to page A and then causes an action on that page (page A, again) to forward to Jpf.NavigateTo.currentPage, then the user will go to page B. When I ran across this case, I expected to see an updated page A rather than go to page B.
> I wish that I could say all of that more clearly, but I figure that it may be more helpful to attach a sample. I will attach a sample to clarify.
> - jeremiah
--
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
-
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
[jira] Assigned: (BEEHIVE-231) Discuss Jpf.NavigateTo.currentPage expected behavior
Posted by "Kenneth Tam (JIRA)" <be...@incubator.apache.org>.
[ http://issues.apache.org/jira/browse/BEEHIVE-231?page=history ]
Kenneth Tam reassigned BEEHIVE-231:
-----------------------------------
Assign To: Rich Feit
> Discuss Jpf.NavigateTo.currentPage expected behavior
> ----------------------------------------------------
>
> Key: BEEHIVE-231
> URL: http://issues.apache.org/jira/browse/BEEHIVE-231
> Project: Beehive
> Type: Task
> Components: NetUI
> Environment: This bug was discovered on Fedora Linux using Tomcat 5.0.25.
> Reporter: Jeremiah Johnson
> Assignee: Rich Feit
> Priority: Minor
> Attachments: BEEHIVE-231.tar
>
> It doesn't sound like the expected behavior has been defined for how Jpf.NavigateTo.currentPage should work in relation to back-button use, so I am entering this Jira task to ensure that the question gets addressed. If a user hits the back button (from page B, for example) to get to page A and then causes an action on that page (page A, again) to forward to Jpf.NavigateTo.currentPage, then the user will go to page B. When I ran across this case, I expected to see an updated page A rather than go to page B.
> I wish that I could say all of that more clearly, but I figure that it may be more helpful to attach a sample. I will attach a sample to clarify.
> - jeremiah
--
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
-
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira