I think it is not quite so easy to write a deserializer for the ArrayList. The custom Deserializer can only feeding children deserializers (of the Arraylist) back to the DeserializerContext, who seems to be tacking child objects onto the Parent Object as class attributes. In case the parent is the ArrayList, we need the context to do an ArrayList.add(Object child) instead. Maybe there is a way to subclass the DeserializerContext to override the usu behavior for adding child elements as class attributes, but I don't see any examples of this.
Any ideas? Bruce List: axis-user Subject: RE: samples for ArrayList From: "Cory Wilkerson" <cwilkerson () travelnow ! com> Date: 2003-08-27 18:28:27 [Download message RAW] Seeing as how an ArrayList is an ordered set of items, you could easily write a \ serializer/deserializer pair to handle passing ArrayLists between services. I'm not \ sure if the Axis server side and client side tools already have some deserializer \ built in for the list interface -- seems like a good idea if they don't. The bottom line is, ArrayList won't be serializable/deserializable across platforms \ w/o some effort on your end to describe it. -----Original Message----- From: Bruce Ho [mailto:[EMAIL PROTECTED] Sent: Wednesday, August 27, 2003 1:00 PM To: [EMAIL PROTECTED] Subject: samples for ArrayList Does anyone out there have a working sample for passing an ArrayList (of user \ generated objects) using Axis, including Java code, wsdl, and wsdd? Is it only a myth that an ArrayList can be passed? The numerous postings in this \ group suggest that no one has had any luck with this. Bruce
