[jbossseam-issues] [JBoss JIRA] Updated: (JBSEAM-633) remoting extension in handling exceptions on client side

Pete Muir (JIRA) jira-events at lists.jboss.org
Sat Mar 1 07:53:58 EST 2008

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

Pete Muir updated JBSEAM-633:

    Component/s: Exception Handling

> remoting extension in handling exceptions on client side
> --------------------------------------------------------
>                 Key: JBSEAM-633
>                 URL: http://jira.jboss.com/jira/browse/JBSEAM-633
>             Project: JBoss Seam
>          Issue Type: Patch
>          Components: Remoting, Exception Handling
>    Affects Versions: 1.1.0.GA
>            Reporter: Nico Gau
>         Assigned To: Shane Bryzak
>            Priority: Optional
> Hi all,
> I don't really know what JIRA is by the way, so hopefully nobody is upset by this post. I first mailed Gavin but he told me I should put it in JIRA. 
> I currently work on a project which uses Seam Remoting directly and I didn't find a neat way in handling errors on the client side as Exceptions are not propagated to it. Therefore I changed Seam to transmit all exceptions which can be handled in the javascript part via another callback. E.g.:
> Seam.Component.getInstance('userManager').currentUser(function(user) {
> alert("user: " + user);
> },
> function(ex) {
> alert("exception occured: " + ex.getMessage());
> });
> As the exception handler is optional, the change would not brake any client code. If you are interested in the change, you can reach me at heinzbeinz AT googlemail.com

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