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?
Not in Fortress, but in Phoenix.
(2) well here starts my own struggling - which ones can really be used in Fortress, if they were originally written for ECM or Phoenix
If they were written for ECM, all of them. If they were written for Phoenix, it somewhat depends on how it depends on Phoenix. Most of the time it is due to the "BlockInfo" or "Block Context" dependencies--which can easily be worked around.
- which ones are stable - the current package shuffeling and the lack of an documented overvied makes it difficult to explain
True. We are going through and making releases of all the stable stuff. Basically if it is accessible from http://avalon.apache.org/bindownload.cgi then it is stable.
Hopefully you can give me some more of the basic arguments.
The chief argument is that you will be able to build on somebody elses hard work that has been tested and peer reviewed far more scrutinously than any work you can do in house. Instead of rebuilding all the infrastructure time and again, you can build on the infrastructure that someone else put together for you. It may not be 100% like you want it, but you would be able to get it there by building on the existing work rather than redoing it from scratch.
Then there is the compatibility issues. Why build components when the ones you need already exist? You can't use them if you have a proprietary component infrastructure that is not binary and contract compatible with Avalon.
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
