I feel like I'm missing something here. On my server, I have a hierarchy of beans. The client will call one method (which will go over SOAP to the server) and get the whole hierarchy as the return value. Some of the beans will have methods that will in turn invoke SOAP calls back to the server. But I don't want the bean getter & setter methods to go back to the server, I want them to work on the local, client-side bean instances that I received from the first call. I should clarify that I want to use WSDL2Java to generate my stubs, because obviously I could hand-roll my solution to the above.
Right now the stubs that WSDL2Java generates make remote SOAP calls on the getter and setter methods. I guess I could define some complex types and then write my own serializer and deserializer code, but then I think: why am I writing serializers and deserializers for beans, which are supposed to serialize for free??? So I guess I'm really raising 2 issues: - how can I work with a bean hierarchy client-side, and use WSDL2Java, but NOT define custom types and NOT write my own serializers? - how does one go about mixing remote SOAP methods with Bean getter/setter methods and still get WSDL2Java to generate all the stubs nicely. Any tips, clarications, code samples, etc gratefully accepted. Thank you, Bob Woodley __________________________________________________ Do You Yahoo!? Try FREE Yahoo! Mail - the world's greatest free email! http://mail.yahoo.com/
