[jbossseam-issues] [JBoss JIRA] Updated: (JBSEAM-3209) GWTService RPC does not transfer SerializableExceptions for GWT 1.4

Adrian Stachowiak (JIRA) jira-events at lists.jboss.org
Tue Aug 5 03:16:56 EDT 2008


     [ https://jira.jboss.org/jira/browse/JBSEAM-3209?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Adrian Stachowiak updated JBSEAM-3209:
--------------------------------------

    Summary: GWTService RPC does not transfer SerializableExceptions for GWT 1.4  (was: GWTService RPC doesn not transfer SerializableExceptions for GWT 1.4)


> GWTService RPC does not transfer SerializableExceptions for GWT 1.4
> -------------------------------------------------------------------
>
>                 Key: JBSEAM-3209
>                 URL: https://jira.jboss.org/jira/browse/JBSEAM-3209
>             Project: Seam
>          Issue Type: Bug
>          Components: Remoting
>    Affects Versions: 2.1.0.A1
>            Reporter: Adrian Stachowiak
>            Assignee: Shane Bryzak
>         Attachments: GWTService-patch.txt
>
>
> GWTRemote is constucted in a way that it parses InvocationTargetExceptions in the processCall method. It looks for the cause of the exception and if it is a SerializableException it prepares an answer that contains the actual exception. Unfortunately in the next if statement this already prepared answer is overwritten by the standard "The call failed on the server; see server log for details" message. This way no SerializableException is ever transferred to the client. Only the standard error response.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        



More information about the seam-issues mailing list