Why does server-config.wsdd not get created when log says so, but only later?

[Colin Sampaleanu <co...@exis.com>]

I have a bit of chicken and egg situation here. I want to run the admin 
client on a remote system to deploy something, but can't until I change 
the remote admin setting in the server-config.wsdd file. However, axis 
only seems to actually create this file when I deploy something, despite 
the fact that it puts out the log message saying it is creating it
---
- Unable to find config file.  Creating new servlet engine config file: 
/WEB-INF/server-config.wsdd
---
even when you hit the '..../services' URL. Is there any way of forcing 
axis on that machine to actually write out the config file short of 
deploying something (from locally)?   If it actually wrote out the file 
when it said it was going to (by hitting the view services url) that 
would be fine.

I realize I can copy an existing server-config.wsdd file from somewhere 
else, but I would prefer not to do that since I would then have to 
configure a few other things as well that are specific to the machine 
(location of attachements dir, etc.)

Regards,

Colin