Hi folks, the topic was not intended to start any flame wars, but I'll face some team members with the we-won't-depend-on-anyone-else's-code syndrom. To show the cons of the complete Avalon/Fortress package (and all the existing components that may or may not be used in Fortress) is somewhat difficult to pinpoint.
My current basic points: - principal and patterns described in DaW - lifecycle management - configuration capabilities (1) - service for logging, instrumenting, pooling - other available services ready to use(2) (1) XML configuration file, but - multiple configuration files for different services - JMX support somewhere? (2) well here starts my own struggling - which ones can really be used in Fortress, if they were originally written for ECM or Phoenix - which ones are stable - the current package shuffeling and the lack of an documented overvied makes it difficult to explain Hopefully you can give me some more of the basic arguments. Regards, J�rg --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
