Glyn,
Will EngineConfigurationFactory be a parameter to AxisEngine constructor? I'd say it
should (I'm just asking :), instead of the EngineConfiguration...
For example
Server application:
new AxisServer(MyEngineConfigFactory(...))
AxisEngine constructor:
AxisEngine(EngineConfigurationFactory cf)
{
EngineConfiguration config = cf.getConfig();
config.configureEngine(this);
. . .
-- Igor Sedukhin .. ([EMAIL PROTECTED])
-- (631) 342-4325 .. 1 CA Plaza, Islandia, NY 11788
-----Original Message-----
From: Glyn Normington [mailto:[EMAIL PROTECTED]]
Sent: Monday, February 04, 2002 10:25 AM
To: [EMAIL PROTECTED]
Subject: Heads up - engine configuration clean-up
Currently, there is no standard way to obtain an engine configuration in Axis. The
result is quite a bit of duplicated code and an inability to predictably override the
defaults.
I'm working on a change to introduce an EngineConfigurationFactory interface with a
DefaultEngineConfigurationFactory implementation which may be overridden via a system
property. The default engine config. factory will produce client engine configurations
based on a WSDD configuration file with filename specifiable in a system property but
with default value as today (Constants.CLIENT_CONFIG_FILE) and server side
configurations similarly configurable but defaulting to the file with name
Constants.SERVER_CONFIG_FILE.
The factory interface and default implementation will also have helper methods which
create an engine configuration based on the appropriate file (as above) but with a
specific Handler added, which will remove some more duplicated code from various
testcases.
I hope to commit the changes in the next day or so.
Glyn
