Ulrich Mayring wrote:
Stephen McConnell wrote:
Doing this here in Avalon is IMO much more productive.
The Avalon project desperately NEEDS some kind of web connectivity. Off the top of my head it is the only project at Apache that doesn't have it. IMHO this is embarrassing. Yeah, you can say "we have a different focus" or "CoP is a generic technology", but at the end of the day the users don't care about buzzwords, they want functionality.
ABSOLUTELY YES.
There is a whole market of web-service releated interests that really NEED a comprehensive service management framework - and that framework is not a bunch of J2EE implementations and its not some COP framework API. Instead, it's a solution that brings together a pragmatic and concrete COP/SOP aspects to a broad spectrum problem. Avalon has changed in the last year - and it's still changing. We are moving from a framework to a platform. A fundimental part of that platform is web-service integration.
And now someone comes along to finally deliver an official Avalon web integration layer and he is sent through incubation. I think Avalon should be sent through incubation instead, maybe that would clear some egos :)
LOL, ... in fact ROTFL!
Well, yes, but no, .. my take is that there *is* the classic question of tradition/apache-way process to be taken into consideration, and in some quarters - a certain hesitation to make the jump to the new Avalon, but irrespective of that, I'm totally confident that we will clear these obstacles ASAP!
Cheers, Steve.
Ulrich
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
--
Stephen J. McConnell mailto:[EMAIL PROTECTED]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
