Hi,
Still new to all this, so I'm not sure if this observation is accurate. It seems to be that wsdl2java could vastly improved if all of it's concrete classes were generated with delegate code pointing to some user specified implimentation. As it stands, I am forced to generate code, copy it somewhere else, implement my functionality, and then hope that the generated code never changes again (because if it does I have to perform a messy merge). This would be generally useful, but especially to me because I have some code that already implements the beans I need.
Well, what we've done is name our service implementation BlahServiceImpl, which is what wsdl2java generates. when we call the wsdl2java ant task, we set up the output directories so that it will find our Impl class and wsdl2java just reports that it found a BlahServiceImpl and won't generate a new one. We generate the client stubs and server skeletons with every build this way.
Now if there were (or is) a way to tell wsdl2java to use a different name for the 'Impl' class (which is a delegate by the way), that would have saved me some similar consternation and grumbling.
-danch
