Bootstrapping James from "other server containers"

[Levent Guendogdu <l....@feature-it.com>]

Hi all,

I hope this is not a FAQ. I've played with James a bit. IIRC, there are
two main ways to bootstrap it. We have our own application server which
contains any number of services. Now I need to bootstrap James from
within that application server. 

I've looked into the Jame's Main class, but it seems it's not meant to
be bootstrapped from there. 

Could anyone give me a quick hint of what would be a good approach to
bootstrap James from within another java application?

Thanks a lot.

Bye,
 Lev.


---------------------------------------------------------------------
To unsubscribe, e-mail: server-user-unsubscribe@james.apache.org
For additional commands, e-mail: server-user-help@james.apache.org

RE: Bootstrapping James from "other server containers"

[Levent Guendogdu <l....@feature-it.com>]

Thanks for your reply. Its our own framework we are using for our
applications. This framework has the ability to run services and I want
to implement a service adapter for James. I'd simply like to have more
control over James than simply "starting run.sh" from that adapter. But
the "problem" is of how to bootstrap James programmatically. 

I see the problem with running too many thingies inside one JVM,
especially when it comes to 3rd party libraries and the version hell.
But since I also plan to use mailets to interface with our application,
I'd like to go this way for now.

Thanks for any pointers,

Lev.

On Mon, 2003-07-28 at 20:32, Noel J. Bergman wrote:
> James is built upon the Avalon component technology.  If you can run that,
> you can run James.  There have been some messages posted about running James
> with JBoss, for example.  What is the underlying framework for your
> application server?
> 
> In fact, we've received requests from administrators that promote running
> James in multiple JVMs.  Basically, they want to separate SMTP, pipeline,
> and other services into individual JVMs.
> 
> Personally, I think that running all of one's server applications in one JVM
> is a recipe for problems.
> 
> 	--- Noel
> 
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: server-user-unsubscribe@james.apache.org
> For additional commands, e-mail: server-user-help@james.apache.org


---------------------------------------------------------------------
To unsubscribe, e-mail: server-user-unsubscribe@james.apache.org
For additional commands, e-mail: server-user-help@james.apache.org

RE: Bootstrapping James from "other server containers"

["Noel J. Bergman" <no...@devtech.com>]

James is built upon the Avalon component technology.  If you can run that,
you can run James.  There have been some messages posted about running James
with JBoss, for example.  What is the underlying framework for your
application server?

In fact, we've received requests from administrators that promote running
James in multiple JVMs.  Basically, they want to separate SMTP, pipeline,
and other services into individual JVMs.

Personally, I think that running all of one's server applications in one JVM
is a recipe for problems.

	--- Noel


---------------------------------------------------------------------
To unsubscribe, e-mail: server-user-unsubscribe@james.apache.org
For additional commands, e-mail: server-user-help@james.apache.org