Clark, William R. wrote: My perspective only... > > Is there any update on the future of the James container now that the > Avalon framework has gone ex-Jakarta?
This is subject to ongoing discussion, but not viewed as critical. The container codebase is stable and if we do find glitches we have the source code and are readily able to fix it. Our immediate direction is to make a better James by evolving our internal codebase rather than changing the glue that holds it together. > Related, is it possible to deploy the James engine in a > container other > than Phoenix/Avalon? E.g. TomCat? The Phoenix/Avalon container assembles components into a working application with a defined lifecycle. A Tomcat container exposes a J2EE spec. environment to a J2EE compliant application. Same word, entirely different metaphor. There are numerous ways for an application deployed on Tomcat to talk to a running James instance. What are you seeking to achieve? -- Steve
