"Rodrigo Reyes" <[EMAIL PROTECTED]> writes:
Avalon is a widely accepted set of patterns, components and interfaces
which are used in many projects. It also provides some implementations
of these components (containers e.g.) and allows many projects to
seamlessly integrate with each others.
As a first step for us it is "Stratum done right".
All IMHO, I haven't done much more yet than glancing over Avalon and
reading some docs.
Regards
Henning
>Hi all
> I have been trying to understand the relation between Turbine services
>and Avalon, but I am still a bit unclear. Is Turbine trying to migrate its
>services to Avalon? Is that what we are calling "avalonization"? If so, why?
>I know the next question is not directly related to Turbine, but if I get an
>answer from you guys here, that could save me from becomming a member of yet
>another mailing list :) Why do we need Avalon? Isn't Avalon doing the same
>job an EJB container is supposed to be doing? Or is Avalon providing extra
>functionality/services? Sorry if this last question seems dumb to many of
>you, but I might not be getting this right yet.
> Thanx in advance...
>Rodrigo
>---------------------------------------------------------------------
>To unsubscribe, e-mail: [EMAIL PROTECTED]
>For additional commands, e-mail: [EMAIL PROTECTED]
--
Dipl.-Inf. (Univ.) Henning P. Schmiedehausen INTERMETA GmbH
[EMAIL PROTECTED] +49 9131 50 654 0 http://www.intermeta.de/
Java, perl, Solaris, Linux, xSP Consulting, Web Services
freelance consultant -- Jakarta Turbine Development -- hero for hire
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
