[jbossseam-issues] [JBoss JIRA] Updated: (JBSEAM-2547) Seam remoting cannot decode Collection objects correctly

[P C (JIRA)]

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

P C updated JBSEAM-2547:
------------------------

    Priority: Critical  (was: Major)

> Seam remoting cannot decode Collection objects correctly
> --------------------------------------------------------
>
>                 Key: JBSEAM-2547
>                 URL: http://jira.jboss.com/jira/browse/JBSEAM-2547
>             Project: JBoss Seam
>          Issue Type: Bug
>          Components: Remoting
>    Affects Versions: 2.0.0.GA
>         Environment: JBoss 4.x AS, Javascript and Seam Integration
>            Reporter: P C
>         Assigned To: Shane Bryzak
>            Priority: Critical
>
> Through the use of Seam Remoting, I find that there is a "bug" in how seam decodes Collection objects on the client side (javascript). For example, on the server side, I am doing the following in a stateless seam bean:
> @Stateless at Name ("test")
> class TestAction implements Test {
> List getTestItems() {...}
> }
> On the Client Side (Javascript):
> var test = Seam.Component.getInstance("test");
> test.getTestItems(callBack);
> var callBack(result) {
> }
> When the seam proxy decodes the message it cannot determine the object types inside the returned collection so it returns someting undefined. But if I define Generics then it works:
> List<ConcreteClass> getTestItems() {...} 
> It seams to me that the Seam Proxy has trouble parsing objects in an abstract collection.

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