ATM in AbstractJamesService we have protected abstract Object getConfigurationData(); protected abstract ProtocolHandler newProtocolHandlerInstance();
each of which is overridden in each server subclass and then downcast in the handler to a configuration object of the correct type. i think it would be better to push responsibility for creating a fully configured protocol handler into the subclass and eliminate getConfigurationData(). the revised lifecycle should make this possible now but would mean that dynamic reconfiguration of handlers would no longer be possible. opinions? objections? - robert [1] http://svn.apache.org/repos/asf/james/server/trunk/avalon-socket-library/src/main/java/org/apache/james/socket/AbstractJamesService.java --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
