[
https://jira.jboss.org/browse/WELD-550?page=com.atlassian.jira.plugin.sys...
]
Nicklas Karlsson closed WELD-550.
---------------------------------
Resolution: Out of Date
Trunk throws
org.jboss.weld.context.NonexistentConversationException: WELD-000301 Could not restore
long-running conversation 1 because id not known
org.jboss.weld.conversation.AbstractConversationManager.setupConversation(AbstractConversationManager.java:150)
which is appropriate for catching. There were changes made since 1.0.0 so I consider this
obsolete until otherwise proven.
Conversation timeout results in a NullPointerException
------------------------------------------------------
Key: WELD-550
URL:
https://jira.jboss.org/browse/WELD-550
Project: Weld
Issue Type: Bug
Components: Conversations, Scopes & Contexts
Affects Versions: 1.0.0.GA
Environment: Oracle Glassfish Server 3.0.0
Reporter: Brian Leathem
Attachments: mavenproject.zip
When a conversation time's out, I get a NPE when I try to access a property of a
ConversationScoped bean. This error condition would be easier to trap if something like a
ConversationExpired Exception were thrown instead, or if it were possible to configure
navigation to a different page when the conversation expired.
--
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