[jbossseam-issues] [JBoss JIRA] Resolved: (JBSEAM-1602) exception handler not recognizing end-conversation
Norman Richards (JIRA)
jira-events at lists.jboss.org
Thu Jul 5 13:24:53 EDT 2007
[ http://jira.jboss.com/jira/browse/JBSEAM-1602?page=all ]
Norman Richards resolved JBSEAM-1602.
-------------------------------------
Resolution: Cannot Reproduce Bug
I cannot reproduce this error. Exceptions that are handled with a pages.xml handler like the above end the conversation as expected. Uncaught exceptions do not end the conversation. If you are still seeing this with Seam in CVS, plus attach a simple reproducible test case.
> exception handler not recognizing end-conversation
> --------------------------------------------------
>
> Key: JBSEAM-1602
> URL: http://jira.jboss.com/jira/browse/JBSEAM-1602
> Project: JBoss Seam
> Issue Type: Bug
> Components: Core
> Affects Versions: 2.0.0.BETA1
> Environment: Seam-CVS
> Reporter: Hung Tang
> Fix For: 2.0.0.CR1
>
>
> In my application, I'm using pages.xml exception handling mechanism to automatically end conversations when optimistic locking exceptions ever arise.
> This is what I have
> <exception class="javax.persistence.OptimisticLockException">
> <end-conversation/>
> <redirect view-id="/p/home.xhtml">
> <message severity="ERROR">#{messages['concurrentmodification']}</message>
> </redirect>
> </exception>
> However, when it does come up, the conversation is not ending as I want.
> I could reproduce this error in the contact-list example. Just add begin propagation to the editContact and the exception handler will recognize it as a javax.persistence.PersistenceException, but it will not end the conversation as you have told it to.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
More information about the seam-issues
mailing list