<tony.q.weddle <at> gsk.com> writes: > > > Just a couple of point on this. > The JavaBean specification does not requite > a getter and setter for each property. A get method implies a readable > property (in Axis terms, it means that property can be serialised). A set > method implies a modifiable property (in Axis terms, it means the property > can be deserialised). > Simon mentioned a special constructor on BeanSerializer > and BeanDeserializer. If this can be used to do what Tim wants, only BeanSerializerFactory > and BeanDeserializerFactory subclasses would be needed, to create the appropriate > instance, and specified in the mapping. However, a quick scan of the BeanDeserializer > indicates that it might not do the job - sorry, if I've got that wrong. > Tony >
And I assume Axis does not care about a BeanInfo, does it? So is there a way to achieve what I need short of renaming the getXXX and setYYY methods to something else which in some cases is not even possible (e.g. I have a CusomException which overrides the Throwable.getMessage(), now I end up with a getMessage1() method and a "message1" element in the complex type in the WSDL which I do not want or need, and renaming the method getMessage() in my CustomException is not an option in this case). I think Axis really needs a descriptor of some sort that let's the user pick and choose what's being exposed. Thank you, Tim
