Hi Janos, thought about bundling server-config.wsdd in my .war too ... At the end I decided NOT to do this, one reason was the <parameter name="attachments.Directory" value="... setting, which is (it's a filepath) better to get created by Axis at runtime if you do not know, where the Application Server is installed - and that's the situation for me since I need to provide my web application for a number of customers who will definitely have different installation paths ...
cu Merten > -----Original Message----- > From: Janos Mucsi [mailto:[EMAIL PROTECTED] > Sent: Friday, June 24, 2005 5:59 AM > To: axis-user@ws.apache.org > Subject: where to put server-config.wsdd > > Hi > > The production people at my company say that an > application can not write into its WEB-INF directory > for security reasons (they can not have the Axis > administration servlet running), therefore I need to > prepackage the server-config.wsdd file in my ear. > > The context attribute "javax.servlet.context.tempdir" > required by the servlet specification resolves to > "temp" on WebSphere (outside the ear), however in > Tomcat it points to "work" by default which seems to > be in the war. > > So my question is which is the best practice, to > bundle the wsdd file in the ear beforehand or have > Axis generate it afterwords during web services > deployment. > > I get UnassignableClassExceptions when I bundle the > descriptor in the ear. > > Any input will be greatly appreciated. > > Regards, > > Janos >
