Specifying config information in resources rather than files

[Brian Levine <BL...@BlueRipple.com>]

Hi,

I suppose this falls into the enhancement request category.  Right now, the
config manager class can be specified in a configuration file (default =
soap.xml).  In my case, I'm using soap.xml so that I can use the
XMLConfigManager to read a DeployedServices.xml deployment descriptor.
Since both the soap.xml and DeployedServices.xml files need to be actual
files in the filesystem, I can't incorporate them into a WAR file.  This is
inconvenient since I'd really like to deploy this information with my
webapp.

One way to address this would be to write a ConfigManager implementation
that reads the deployment information out of a resource in the WAR file.  In
order to obviate the need for the soap.xml file, the custom ConfigManager
class would need to be specified as a servlet init parameter rather than in
the soap.xml file.

If I've missed some other way to work around this problem, please let me
know.

Thanks.

-brian