Hi Dan, I had similar problems because I wanted to use a custom provider. My solution was to not use WSDL2Java for the generation of server side code. Instead, I used XDoclet to generate the deploy.wsdd (well actually I just generated the server-config.wsdd for all services. This works really well because all I have to do is put a couple of tags in my classes and I can generate service definitions as well as typemappings etc. I also now know that what I'm deploying is truly related to my code and if the code changes, so will the deployment descriptor.
Nathan -----Original Message----- From: Dan Ciarniello [mailto:[EMAIL PROTECTED] Sent: Tuesday, 19 October 2004 7:51 AM To: [EMAIL PROTECTED] Subject: WSDL2Java and deploy.wsdd When WSDL2Java generates server side code, it does not overwrite the binding implementation class which is a good thing. It does, however, overwrite the deploy.wsdd which is both good and bad. It's good because one wants one's code changes reflected in the wsdd. It's bad because any handlers that have been added to the wsdd are overwritten. Is there any way to setup handlers and request/response flows so that they are automatically added to the wsdd when it's generated? Thanks, Dan.
