Yes, you explained it right. -----Original Message----- From: Pathak, Sanjesh [mailto:[EMAIL PROTECTED]] Sent: Thursday, February 06, 2003 5:41 PM To: [EMAIL PROTECTED] Subject: RE: how to serialize/deserialize static final fields
It is an interesting topic. Although I am not an expert on WSDL or BeanSerializer, I think I understand your point. If BeanSerializer does not serialize constants, then there is no way a client can get that information. The information or value of the constant has to be either in WSDL or in the serialized data. If it is not there at both the places, then their is no way a client can get that information. May be you might have to re-design your code like sending this information in the header and asking the client to send it's choice back as a header or add an extra parameter to your service so as to pass that value. Sanjesh -----Original Message----- From: Liviu Chiriac [mailto:[EMAIL PROTECTED]] Sent: Thursday, February 06, 2003 4:31 PM To: 'Mike Burati'; [EMAIL PROTECTED] Subject: RE: how to serialize/deserialize static final fields I understand, by design is not possible. Or at least it is not possible with a BeanSerializer/Deserializer. But what I want to do is not contradictory: I want a user to pick a value out of 3 that I have pre-defined (as constants in my class). I need a way to communicate to the client what those pre-defined values are. When the client sends an object to the server, I check to see which value he picked (out of these 3) and perform different tasks accordingly. (But I need him to pick only one of these 3...) What is the best way to transmit these static constants (associated with a particular class), to the user, if I cannot do it with a BeanSerializer/Deserializer? Liviu
