Hello I' working on developing web services using axis. In out company we have developed a lot of so called java "services". The "services" look like this:
public interface SomeService { public TransferObject1 doSomeThing(TransferObject2, ...) throws SomeException; } The TransferObjects have the folowing properties: - They are Java Beans (means getter and setters, default constructor) - The Transfer Object's leafs are so called "Business Values". This are "strong typed" Types. They are imutable and define a "value set" for each. - The transfer object does not use primitive java types as leaves. We would now export our "services" as webservices. I played a little bit around with the framework. So i can implement now: - One Serializer and Deserilizer for the BusinessValues (and map them to soap encoding). - Use the BeanSerilizer/Deserialzer with my own subclasses. But i'm not sure about the design. How would you solve the problem? Some design questions: - Would you write custum serializer/deserialier for the Transfer Objects and Business Value's (BV). - Would you use the BeanSerializer for the TransferObject? - If I use custum serializer for the BV's how can i regsiter them for all my services programmatically (e.x. like int/long/ ... in DefaultTypeMappingImpl). - Or would you write a Adapter for the service, using "normal" Java properties. Thx Pascal