[
https://issues.apache.org/jira/browse/ORCHESTRA-40?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12763785#action_12763785
]
Martin Marinschek commented on ORCHESTRA-40:
--------------------------------------------
Ok, so there was a lot of action here, but not really a lot of discussion.
Let's discuss about the base first: Bernd's (and by the way also Manfred's and
mine) point of view is that a JSF application should have a way to be informed
of back-button clicks, forward-button clicks, refreshes, double-submits, etc.
As I see it, an interface implemented by the application should provide a hook
which needs to be called in such cases.
Now for me this is highly conversation-context (=tab or window) related: a
back-button is always clicked within a tab or window. If you want to indicate
to the user that the back-button has been pressed you will need to store a list
of tokens (one per request) and again, I think that should be stored per
conversation-context (not in the session).
If it is not for this, Orchestra should provide ways to handle these problems
cause a solution is desperately needed in the JSF space. AFAIK, only Spring
Webflow provides something out of the box, and with Spring Webflow you are
moving pretty far off the JSF standard, both from a configuration perspective
and a usage perspective (however, I am not saying that Spring Webflow is bad -
it is indeed a very good framework - just not very close to JSF if you take a
deeper look at it).
regards,
Martin
> A transaction token component inspired by the struts transaction processor
> --------------------------------------------------------------------------
>
> Key: ORCHESTRA-40
> URL: https://issues.apache.org/jira/browse/ORCHESTRA-40
> Project: MyFaces Orchestra
> Issue Type: New Feature
> Components: Conversation
> Affects Versions: 1.3.1
> Reporter: Bernd Bohmann
> Assignee: Simon Kitching
> Attachments:
> ORCHESTRA-40-CacheControl+TransactionToken-before-restore-View2.patch,
> ORCHESTRA-40-CacheControl+TransactionTokenListener-after-restore-View3.patch,
> ORCHESTRA-40-CacheControl.patch, ORCHESTRA-40-TransactionToken.patch
>
>
> A transactionToken Component for orchestra inspired by the struts transaction
> processor.
> The transaction token is to be used for enforcing a single request for a
> particular transaction.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
