On 2/15/07, robert burrell donkin <[EMAIL PROTECTED]> wrote:
On 2/15/07, David Woldrich <[EMAIL PROTECTED]> wrote:
> Robert,
>
> Ok, fair enough. Well, honestly for starters, I would love to deploy
> James as a monolithic Enterprise App or Web App if we could work out the
> lifecycle issues (meaning System.exit() isn't the only way to achieve
> orderly server shutdown.) It's been awhile since I looked deep enough
> at that code to say whether that problem has already been solved or
> not. So, if I could get that, it would totally solve my short term
> itch. If you think that that's a rabbit hole not worth diving into, I
> will trust your judgement. But, if it is, I'd like to tackle that first
> and get it overwith.
i really think that the best approach would be to deploy JAMES as a
service available to enterprise applications rather than as an
enterprise application. so, i prefer the idea of deployment as a
plugin but i'm not a geronimo guru. i think that the first step should
be to ask the geronimo team whether this would be the best approach.
this probably means posting something appropriate to the dev list.
All Geronimo-deployed objects are wrapped as GBeans, so G. can handle
the object lifecycle, inter-dependencies and all that. For a native
integration with G. we would need to hack some sort of GBean wrapper
around James. Maybe a look at how other G.-integrations have been done
(for example Tomcat) may give an idea how this could be done.
http://cwiki.apache.org/GMOxKB/what-on-earth-is-a-gbean-why-are-they-different-from-mbeans.html
G. also has some sort of integration with Spring. Maybe this is a way
to go without GBeans, but I never looked more deeply into this.
http://cwiki.apache.org/GMOxDOC10/spring.html
for connectivity to the JAMES service, this is where i think that
service bus and JCA ideas are powerful. rather than thinking about an
EJB, multiple transport mechanisms would be powerful: EJB, WS, JMS,
JCA and so on. adopting a bus might give a lot of benefits for very
little effort.
JCA would be the standardized way to deploy any kind of service which
is not an enterprise application (EAR) or web application (WAR) into
any J2EE server.
For this, you would also need to detach James' components from the
current container and boot the whole James component ecosystem
independent from the container. To me this seems more complicated than
"simply" deploying components in a Geronimo-dependent way.
I am very excited to see any sort of integration :-) . It's a pitty I
cannot get my hands dirty with that, currently, because lack of time
:-(
Bernd
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
