>They are separate. axisConfig.properties (or whatever) will be to capture
>what are currently (and generally inappropriately) "system" properties
>(system properties ==> global variables ==> bad for modular design).
Fine.
>As long as the requirements I listed in original note are met.. which
M@IBMGB cc:
Subject: Re: [axis] Configuration
properties via system properties
The rules for how server-config.wsdd is located are already rather
complicated. Are you proposing to add axisConfig.properties with another
set of rules or is axisConfig.properties just server-config.wsdd renamed?
If not a renaming, please could we unify the rules and use the same code to
locate b
We have two types of configuration info...
1. That stored in the client-config.wsdd/server-config.wsdd
2. Various 'overrides' that are set as system properties.
I'd like to:
a. introduce a level of indirection for current code that gets system
properties. Chang all calls to go through an
or
