On Dec 19, 2007 5: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:

<snip>

> >> 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?

not sure there's any consensus on this

OSGI (though COP not IoC) tooling is also a possibility. GBean tool is
also interesting.

i'd like to see the container tooling completely separated from the
components. this would allow cleaner deployment of components in
different environments.

> 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.

phoenix is from an earlier generation of IoC containers. it's
basically avalon so substituting phoenix->avalon in
http://martinfowler.com/articles/injection.html works ok.

but IMHO a deep understanding of pheonix is not required: it just
assembles and configures JAMES. if you want to create a new component,
it's probably easiest to create a new module and then code pure POJOs
using TDD & BDD (JAMES is a little tricky to debug). once that's done
then add pheonix configuration and assembly code. for example, see 1
and 2.

- robert

1. 
http://svn.apache.org/repos/asf/james/server/trunk/phoenix-deployment/src/java/org/apache/james/phoenix/jms/activemq/
2. 
http://svn.apache.org/repos/asf/james/server/trunk/experimental-activemq-function/

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to