A long long long time ago...
On the server side
Axis servlet init parm decided location (forgot specifics)
If not specified, global parm in the service-config.wsdd (forgot specifics)
If not specified attachment directory WEB-INF of servlet.
The System.getProperty("java.io.tmpdir") was purposely not selected as any
default so as to not have several Axis Servlets running on the same system dumping
into the same place!! By keeping them in a WEB-INF dir it was obvious what the
source was too. And there "were" options to override that behavior both by
setting a servlet parameter or specifying it in the configuration file.
Rick Rineholt
"The truth is out there... All you need is a better search engine!"
[EMAIL PROTECTED]
Please respond to [EMAIL PROTECTED]
To: "[EMAIL PROTECTED]" <[EMAIL PROTECTED]>
cc:
Subject: Attachment Destination - Default tmp filepath
Right now axis assumes that context.getRealPath(...) returns a writeable
path for storing attachments and its server-config.wsdd. In production the
server-config isn't a problem, but for attachments we should use a different
default behavior:
1. Default location for attachments should be outside of the war archive, I
recommend System.getProperty("java.io.tmpdir").
2. A user may override this behavior in service-config.wsdd using <parameter
name="attachments.Directory" value="somedir"/>.
The Axis Runtime should not generate this service-config.wsdd entry, because
this removes the axis deployment destination independency. Just imagine that
you want to deploy your axis configuration with your .ear or .war and have
several deploy destinations (local testing per user, pre production,
production system).
Any comments?
Jens
