[
https://issues.jboss.org/browse/JBSEAM-4658?page=com.atlassian.jira.plugi...
]
Marek Novotny closed JBSEAM-4658.
---------------------------------
Fix Version/s: 2.2.1.Final
Resolution: Done
this was fixed in JBSEAM-4755
<s:conversationPropagation> better validation of type
parameter
---------------------------------------------------------------
Key: JBSEAM-4658
URL:
https://issues.jboss.org/browse/JBSEAM-4658
Project: Seam 2
Issue Type: Bug
Affects Versions: 2.2.1.CR1
Environment: JBoss AS M3
Reporter: Andrew Wheeler
Assignee: Marek Novotny
Priority: Minor
Fix For: 2.2.1.Final
The examples for <s:conversationPropagation> in section 7.1 of the documentation
state that a nested conversation is started with type="nested". If used with a
commandLink this causes handleConversationPropagation to begin a null pageflow. The result
is that a NullPointerException is thrown.
Section 33.1.1.5 correctly states that type should be "nest".
I suggest that a check is performed on the conversationPropagation control to throw an
exception if the wrong type is passed. The documentation should be corrected to be
consistent.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:
http://www.atlassian.com/software/jira