Hi, I am building a WS on top of an existing API using Axis. Initially, I was planning to reuse some existing beans as parameters to the WS. For example, the API already has an Order bean which I could fairly easily reuse in the WS as a parameter to the processOrder() operation. Are other folks doing this sort of thing? I am beginning to doubt this decision because...
-The bean has a property of type Map and from what I've read, maps tend to reduce interoperability. -I'm worried that once I expose this bean in the WS, changes that used to be easy - like adding a new property - will be more complicated because I'll always need to rollout a new wsdl at the same time (and possibly newly generated client stubs) to keep the axis bean serializers/deserializers happy. I guess I'd like to have the ability to not have to rollout the changes to the WS right away if I don't have to - this is valid because the bean is used in other contexts. I'm not even really sure about this last point but I remember a recent thread which led me to believe this was the case. Anyway, are most folks creating beans specific to the WS or are they reusing existing beans? I hate the idea of creating a SoapOrder bean which has the same properties as the regular Order bean but it sounds like I will need to if I want flexibility. Paul
