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

[Shane Bryzak (JIRA)]

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

Shane Bryzak closed JBSEAM-2547.
--------------------------------

    Resolution: Cannot Reproduce Bug

I cannot reproduce this issue.  Here's the test case I tried:

Server-side Seam component:

@Name("test")
public class Test
{
   @WebRemote
   public List getTestItems() {
     List values = new ArrayList();
     values.add("Foo");
     values.add(123);
     values.add(new Date());
     
     Foo foo = new Foo();
     foo.setValue("Bar");
     values.add(foo);
     
     return values;      
   } 
}

Server-side POJO bean:

package org.jboss.seam.example.remoting;

public class Foo  {
   private String value;
   public String getValue()  {
      return value;
   }   
   public void setValue(String value)  {
      this.value = value;
   }
}

Client-side include:

  <s:remote include="test,org.jboss.seam.example.remoting.Foo"/>

Client-side code:

    function test() {    
      var test = Seam.Component.getInstance("test");
      test.getTestItems(testCallback);
    }

    function testCallback(result) {
      for (var i = 0; i < result.length; i++)
      {
        alert(result[i]);
        
        if (Seam.Remoting.getTypeName(result[i]) == "org.jboss.seam.example.remoting.Foo")
          alert(result[i].getValue());
      }
    } 

With this test case everything works as expected.  If you can still reproduce the issue then I'm going to need a more detailed test case.

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