No, Use the bean serializer as is.
If you leave out the setDummyClass in the class, and don't include a <dummyClass> entry in the SOAP request, the bean serializer will handle this by calling set on "id" and "name". Incoming - your service class will make the call to getDummyClass(). Outgoing - Instantiate the bean with id, name, and the seraizler will call getDummyClass() Ben On Fri, 2003-01-10 at 13:11, [EMAIL PROTECTED] wrote: > and then just subclass the Bean serializer/deserializer? > > -----Original Message----- > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] > Sent: 10 January 2003 18:06 > To: [EMAIL PROTECTED] > Subject: Re: Deserializers > > > I would wrap it in a JavaBean and use BeanSerialzer. > > public class Bean { > > private String id = null; > private String name = null; > > // Getters and setters for id and name below > > public DummyClass getDummyClass() { > > DummyClass dummyClass = new DummyClass(id,value); > > // Do other sets here > > return dummyClass; > > } > > } > > On Fri, 2003-01-10 at 12:57, [EMAIL PROTECTED] wrote: > > I have an object that can only be instantiated when a particular field is > > known. This field is immutable. What is the best way to construct a > > deserializer for this object? (without having to completely rewrite the > > functionality provided by DeserializerImpl for example). > > > > e.g. > > > > public class DummyClass { > > > > public DummyClass (int id, String value){ > > this.id = id; > > this.value = value; > > } > > > > public int getId(){ > > return this.id; > > } > > > > public String getValue(){ > > return this.value; > > } > > > > } > > > > >
