[jbossseam-issues] [JBoss JIRA] Updated: (JBSEAM-2465) Asynchronous method call from page action

Pete Muir (JIRA) jira-events at lists.jboss.org
Wed Mar 19 19:29:26 EDT 2008

     [ http://jira.jboss.com/jira/browse/JBSEAM-2465?page=all ]

Pete Muir updated JBSEAM-2465:

    Fix Version/s: 2.1.0.GA
                       (was: 2.1.0.BETA1)

> Asynchronous method call from page action
> -----------------------------------------
>                 Key: JBSEAM-2465
>                 URL: http://jira.jboss.com/jira/browse/JBSEAM-2465
>             Project: JBoss Seam
>          Issue Type: Bug
>          Components: Core
>    Affects Versions: 2.0.0.GA
>         Environment: Windows XP running Tomcat 5.5.25 using Seam 2.0.0.GA with POJO's (that is no EJB3 at all)
>            Reporter: Pierre Ingmansson
>            Priority: Minor
>             Fix For: 2.1.0.GA
>   Original Estimate: 1 hour
>  Remaining Estimate: 1 hour
> If a page-tag in pages.xml includes a action that is asynchronous like this:
> <page action="#{myAction.doSomethingAsynchronously}" view-id="/myView.xhtml">
> And if something goes wrong while executing the method "doSomethingAsynchronously", the error is not logged at all.
> In my case the call to the "myAction"-bean resulted in a RequiredException (due to some misconfiguration on my part), but the error was never logged so I had to debug the internal Seam-code to find out what went wrong. If the method "doSomethingAsynchronously" would have thrown a exception itself, I suspect that the behaviour would be the same (no stacktrace inte the log that is..).

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