On Dec 19, 2007 6:24 AM, Chris Rose <[EMAIL PROTECTED]> wrote: > > 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.
The Phoenix-based distribution is the proven deployment, used since years and many releases. The Spring-based distribution is experimental. It should integrate quite well with other Spring-based applications or container-agnostic components. It is not different to the Phoenix distribution and does in fact wrap Avalon components and emulate Phoenix. Bernd --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
