@WebMethod
public Collection<A> getCollection()
{
List lst = new ArrayList();
lst.add(new A());
lst.add(new B());
return lst;
}
When a get on the client the collection i expect to see the first element of type A and the second of type B.
I attached here a patch that will fix this problem. It's kind of a hack but I could not figure out a better way to handle this.
Description
class A
{
....
}
class B extends A
{
..
}
@WebMethod
public Collection<A> getCollection()
{
List lst = new ArrayList();
lst.add(new A());
lst.add(new B());
return lst;
}
When a get on the client the collection i expect to see the first element of type A and the second of type B.
I attached here a patch that will fix this problem. It's kind of a hack but I could not figure out a better way to handle this.
Thanks, but there is a much simpler way to do this - as supplied in the patch in issue XFIRE-583 (which is a duplicate of this issue). I just committed a fix for it in SVN. Cheers
Dan Diephouse - 21/Aug/06 12:08 PM Thanks, but there is a much simpler way to do this - as supplied in the patch in issue XFIRE-583 (which is a duplicate of this issue). I just committed a fix for it in SVN. Cheers
Bug
Closed
Major
Acegi CollectionType doesn't serialize correctly items that are inherited from a base class
XFIRE-583(which is a duplicate of this issue). I just committed a fix for it in SVN. Cheers