axis-java-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bugzi...@apache.org
Subject DO NOT REPLY [Bug 17689] New: - Some axis properties are extracted from the Servlet configuration, others from Axis's config; all should be from the AxisEngine
Date Wed, 05 Mar 2003 19:24:57 GMT
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=17689>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=17689

Some axis properties are extracted from the Servlet configuration, others from Axis's config;
all should be from the AxisEngine

           Summary: Some axis properties are extracted from the Servlet
                    configuration, others from Axis's config; all should be
                    from the AxisEngine
           Product: Axis
           Version: future (enh)
          Platform: Other
        OS/Version: Other
            Status: NEW
          Severity: Normal
          Priority: Other
         Component: Deployment / Registries
        AssignedTo: axis-dev@ws.apache.org
        ReportedBy: stevel@apache.org


Right now the AxisServletBase hierarchy often pulls out config info at init()
time from its servlet context, with some hooks for system properties getting
priority. 

However, the .wsdd config design is superior as it provides a single place for
config, lets people plug in new config systems, and can be updated dynamically.


Proposal

0. reference.html needs to be updated to mark the difference for Axis1.1

post 1.1:

1. we move the axis servlet config items into the Axis engine, for a single
config  location.

2. users of the config data either stop caching them, or we offer an
AxisEngineGlobalOptionsListener interface, and a means of registering this
interface with the Engine, for update notification. 

Note that (2) would be something we could do with JMX, if we want to introduce
even more complexity to the system :)

Mime
View raw message