[jbossseam-issues] [JBoss JIRA] Updated: (JBSEAM-2933) Seam 2.1-snapshot, gwt1.5m2, array issues

Wed Oct 8 16:19:20 EDT 2008

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

Nick Vintila updated JBSEAM-2933:
---------------------------------

    Attachment: GWTService.java

Hi, 

Marshalling objects other than primitive types does not work with the the latest Seam, 2.1.0.CR1 and GWT 1.5. Or so I gathered from a number of attempts to do so. The errors popped by the GWT client look quite dramatic so I concluded there is something very wrong (undefined fields..).

I re-wrote GWTService.java using code from GWTs' RemoteServiceServlet.java and RPC.java much like the original author's must have.

Tried to be consistent in prefixing methods taken from GWT classes with the name of the original class such that other people know where to look for when GWT changes.

This approach is far from nice but extending RemoteServiceServlet or using a delegate both failed for obvious reasons.

See attached and advise if you accept the code.

In any case I'd appreciate some heads up on the status and plans on integration with GWT 1.5.

I am thinking to also find a way to use conversations - seems easy to extend the existing code which is common with Seam remoting.... which gives me hope this integration is still in plans.

Thanks in advance
Nick

> Seam 2.1-snapshot, gwt1.5m2, array issues
> -----------------------------------------
>
>                 Key: JBSEAM-2933
>                 URL: https://jira.jboss.org/jira/browse/JBSEAM-2933
>             Project: Seam
>          Issue Type: Bug
>          Components: GWT
>            Reporter: darren hartford
>         Attachments: GWTService.java
>
>
> There are some problems with Arrays of DTO's between seam 2.1-snapshot (4/25/2008) and GWT 1.5m2 remoting/rpc.
> i.e.  SimpleDTO[] getMyDtoArray()
> It is the non-informative 'IncompatibleRemoteServiceException' error and mentions the application out of date, which it is not.  No sample project or test case yet as mentioned in the forum post just identified the source of some problems.

-- 
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