[jbossseam-issues] [JBoss JIRA] Commented: (JBSEAM-2935) Seam Remoting/GWT1.5M2, change to 'Long' behavior (impacts Date?)

Norman Maurer (JIRA) jira-events at lists.jboss.org
Fri Nov 7 10:22:36 EST 2008

    [ https://jira.jboss.org/jira/browse/JBSEAM-2935?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12437464#action_12437464 ] 

Norman Maurer commented on JBSEAM-2935:

Any chance to get a fix in the near future ? We think about using seam as "backend" for our new GWT project, but with this bug its just impossible :-/

> Seam Remoting/GWT1.5M2, change to 'Long' behavior (impacts Date?)
> -----------------------------------------------------------------
>                 Key: JBSEAM-2935
>                 URL: https://jira.jboss.org/jira/browse/JBSEAM-2935
>             Project: Seam
>          Issue Type: Bug
>          Components: GWT
>    Affects Versions: 2.1.0.A1
>            Reporter: darren hartford
>            Assignee: Shane Bryzak
>            Priority: Blocker
> From: 1.5M2 announcement post -- http://groups.google.com/group/Google-Web-Toolkit-Contributors/browse_thread/thread/2f659fe351ff0b4c
> "  - "long" emulation. The Java language defines "long" types to be 64-bit
> signed integers, whereas JavaScript only supports 64-bit floating point
> numbers, which cannot accurately represent the same whole-number range as a
> true "long" type. GWT 1.5 M2 transparently emulates long types properly to
> more faithfully maintain Java semantics in web mode. "
> Although this is from GWT 1.5M2, the risk/return of them changing this is unlikely. It appears that this also impacts Dates.
> This has been tested against Seam 2.1-snapshot (4/25/2008) and GWT 1.5M2 on jboss 4.2. Other datatypes are working correctly, Long and Dates are not.  This seems to only impact the RPC mechanism.
> symptoms (on client side) for Long.  Same symptoms for java.util.Date:
> ==============
> getLong had a failure: com.google.gwt.core.client.JavaScriptException: (TypeError): orig has no properties
>  message: orig has no properties
>  fileName: http://dhartford:8080/sample-ejb3-gwt-client/com.domain.app.gwt.SeamEjbRemote/0838C54E584391EEA8D10F2AD23CB3D5.cache.html
>  lineNumber: 7172
>  stack: java_lang_Long_parseLong__Ljava_lang_String_2I(undefined,16)@http://dhartford:8080/sample-ejb3-gwt-client/com.domain.app.gwt.SeamEjbRemote/0838C54E584391EEA8D10F2AD23CB3D5.cache.html:7172
> com_google_gwt_user_client_rpc_core_java_lang_Long_1CustomFieldSerializer_instantiate__Lcom_google_gwt_user_client_rpc_SerializationStreamReader_2([object Object])@http://dhartford:8080/sample-ejb3-gwt-client/com.domain.app.gwt.SeamEjbRemote/0838C54E584391EEA8D10F2AD23CB3D5.cache.html:4258
> com_domain_app_gwt_client_SeamGwtStandardDataService_1TypeSerializer_instantiate__Lcom_google_gwt_user_client_rpc_SerializationStreamReader_2Ljava_lang_String_2([object Object],"java.lang.Long/4227064769")@http://dhartford:8080/sample-ejb3-gwt-client/com.domain.app.gwt.SeamEjbRemote/0838C54E584391EEA8D10F2AD23CB3D5.cache.html:2102

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