I'm loathe to suggest it, but if the consensus is thatwe should be able to use different service frameworks then I'd suggest a commons-services package that does for Avalon-Merlin,Cornerstone,HiveMind, etc. what commons-logging does for log4j, jdk1.4 logging, etc.
I personally feel that standardizing on a single service framework and porting any components missing to that framework would be better. That avoids the lowest common denominator problem, albeit at the cost of porting and possibly forking some components.
A middle ground would be possible by standardizing on one framework and providing shims into that framework for using the other frameworks.
Which of the above options would you all prefer?
Bill Barnhill
David Le Strat wrote:
Has anybody given a serious look at Avalon Merlin Service Management Framework and how it compares to others?
Reading this from Avalon web site was quite
interesting:
<quote>
Each of these initative, from complex system such as
the James enterprise messaging platform through to
utility components such as the Cornerstone component
suite (thread pools, persistence, task scheduling,
etc.) can be <b>represented in Merlin as pluggable
services within a composite component context</b>. </quote>
It opens all kinds of possibilities...
Regards,
David.
__________________________________ Do you Yahoo!? Free Pop-Up Blocker - Get it now http://companion.yahoo.com/
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
