axis-java-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Berin Loritsch <blorit...@apache.org>
Subject Building the Engine
Date Mon, 17 Sep 2001 20:55:54 GMT
As I was beginning to update the configuration for Axis to use Avalon
(remember, the API is changing as little as possible).  It was immediately
apparent that the Handlers, Transports, Services, and TypeMappings would
benefit from a full implementation of the Factory pattern.  The thing is,
that the components there all have the same basic configuration pattern.

This does make it easy to have Factory classes that build the individual
handlers externally.  Currently, everything is forced into the Admin
class.  By moving it into the different packages, it makes it easier
to maintain the configuration needs with the interface of the component
being set up.

This also reduces the amount of bulk in the Admin class.  In the initial
change to the Configuration hierarchy, the bulk of the code is being moved
into the AxisEngine class so that methods that are artificially public can
be closed.  This allows for a more secure architecture by design.

Mime
View raw message