every web app has its own web-app classloader which loads the jars in WEB-INF/lib so if the axis jar is in each WEB-INF/lib then every instance of Axis should be isolated from every other instance of Axis if that's what you mean. (statics are stored in the Class object and every classloader will have their own Class object so even statics won't be shared)
as for integrating deploy.wsdd changes into server-config.wsdd i use a text editor and copy-paste. it's only needed when you change your data types or interface (operations list) so once your service API is stable you don't have to worry about it (until you change your interface/data layer - then it's good to have that mental note). basically if deploy.wsdd changes you need to copy those changes over. and until you add custom handlers (like WSS4J's WSDoAllReceiver) or custom serializers you can copy-paste the whole <service> block over. hth. .............ron. >> but if you're just talking about configuring a server while it's down >> WEB-INF/server-config.wsdd is your file. > That's roughly what I had in mind. Now, a few more questions, if you don't > mind :) > > - can I have Axis deployed in multiple WS ? (which would each have a different > server-config.wsdd) > - how could I automatically write/merge a server-config.wsdd file from the > wsdd file generated > by Wsdl2Java ? > > Best regards, > > Frederic >
