On 18-Dec-07, at 4:05 PM, Robert Burrell Donkin wrote:
On Dec 18, 2007 10:47 PM, Chris Rose
<[EMAIL PROTECTED]> wrote:
Well, I have one question right off: what is James'
_infrastructure_?
I gather that it runs in the Avalon container (?) but because the
Avalon
project seems to have faded out over apache-way I find it difficult
to
get a handle on what exactly Avalon provides.
making this obvious is one of the aims of the modularisation
Heh. I can well imagine.
Is James using Phoenix, or Loom, or anything like that? Or is the
container now self-hosted, as it were?
james requires an IoC container for assembly. phoenix and spring
deployments are in trunk.
That begins to make a certain amount of sense. I noticed what seemed
to be two separate distributions in the build, and could not determine
which one to use and why. Is one or the other of these formally
deprecated, or is the James project slated to support two operating
environments moving forward? I know my way around Spring, in a bare-
bones sort of way, so if Phoenix is an IoC container that's roughly
equivalent I should not be lost.
avalon lifecycle interfaces are used quite extensively
excalibur components (from avalon) are used for bio server framework.
(when JAMES starts offering nio, MINA is the most likely candidate
framework.)
logkit is used extensively for logging (but newer components tend to
use injected JCL allowing adaption to logkit)
excalibur, avalon and commons components are used for pooling and
threading
Thanks again, Robert; this is an excellent overview of the way it all
works (tm). I'm going to see if I can get an instance of James
started on my macbook here and start getting frisky with it.
- robert
---------------------------------------------------------------------
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]
