[
https://jira.jboss.org/browse/WELD-549?page=com.atlassian.jira.plugin.sys...
]
Marcel Kolsteren commented on WELD-549:
---------------------------------------
Just a comment related to the possibility of dropping the ConversationAwareViewHandler.
The getActionURL method now covers four cases:
1. form actions
2. link hrefs
3. Ajax calls, and
4. redirect URLs
According the the Weld documentation (5.3.2. Conversation propagation), the conversation
is automatically propagated in all cases except 2. So I think dropping the
ConversationAwareViewHandler is only possible if there is another solution for covering 1,
3 and 4.
Conversation propagated by default with h:link
----------------------------------------------
Key: WELD-549
URL:
https://jira.jboss.org/browse/WELD-549
Project: Weld
Issue Type: Bug
Components: Web Tier integration (JSF, JSP, EL and Servlet)
Affects Versions: 1.0.1.Final
Environment: GlassFish Server Open Source Edition 3.0.1 on Mac OS 10.6 and
Windows 7. WELD-000900 1.0.1 (SP2)
Reporter: David Beaumont
Priority: Critical
Fix For: 1.1.0.Beta2
Attachments: CdiConvoBug.war
I created a long running conversation by running a method on a conversation scoped bean:
private boolean initialized;
public void init() {
if(initialized) return;
conversation.begin();
initialized = true;
}
From a facelets page using the JSF2 event system:
<f:metadata>
<f:event type="preRenderView" listener="#{convoBean.init}" />
</f:metadata>
If a conversation has been made long-running, the h:link tag will produce links with the
conversation query parameter, thereby propagating the conversation whether that was what
you wanted or not.
I.e:
<p>Link: <h:link outcome="page2.xhtml" value="a link"
/></p>
produces
<p>Link: <a href="/CdiConvoBug/page2.jsf?cid=3">a
link</a></p>
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira