Pointer:  get the sources for Phoenix from the Apache Jakarta CVS
repository and take a look at 

        org.apache.avalon.phoenix.launcher.JMXLauncher

This is the JMX Mbean that is used to start Phoenix inside an
application server.  You can duplicate this functionality in your
framework.  

Regards
Steve


> -----Original Message-----
> From: Levent Guendogdu [mailto:[EMAIL PROTECTED] 
> Sent: Monday, July 28, 2003 11:46 AM
> To: James Users List
> Subject: RE: Bootstrapping James from "other server containers"
> 
> 
> 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: [EMAIL PROTECTED]
> > For additional commands, e-mail: [EMAIL PROTECTED]
> 
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
> 
> 

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

Reply via email to