We run James in 4 different environments including production.
Management & maintenance of James has always been a grey area because it
does not fall under a J2EE App Server.
In fact it is the only application which we run outside of Weblogic 8.1.

I would be very interested in helping out in this regard.



|---------+--------------------------------->
|         |                                 |
|         |  "Bernd Fondermann"             |
|         |  <[EMAIL PROTECTED]|
|         |  m>                             |
|         |  10/10/2006 08:56               |
|         |  Please respond to "James Users |
|         |  List"                          |
|         |                                 |
|---------+--------------------------------->
  
>-----------------------------------------------------------------------------------------------------------------------------|
  |                                                                             
                                                |
  |      To: "James Users List" <server-user@james.apache.org>                  
                                                |
  |      cc:                                                                    
                                                |
  |      Subject:  Re: My vote for deployment of James as a Web Application     
                                                |
  
>-----------------------------------------------------------------------------------------------------------------------------|




On 10/10/06, David Woldrich <[EMAIL PROTECTED]> wrote:
> Steve Brewin wrote:
> > Yes, this is right except that counter to David's requirements, without
a
> > substantial rework of James such a JCA would have to connect to James
> > running in a separate JVM. This is because James acquires and manages
its
> > own resources, which precludes running as a local J2EE managed
connector
> > that obtains resources, such as threads and DB connections from the
J2EE
> > app. server.
> >
> > As this is the case, its hard to see what advantage is gained by
> > implementing a James JCA, which I guess is why no-one has done it.

The original post's goal was to run James within a J2EE server. I
never intended to suggest this would be easy or possible at all ;-)
...

> > So in the near future, I don't see how your request could be
> > fullfilled, except...

But nevertheless, I think it would be a benefitial long time goal.
Even though this is probably not the use case for the majority of
James users.
And JCA would be the right way to do this.

> I have contributed to open source projects before, but usually just to
> contribute bug fixes or to file bug reports.  I am currently working on
> collaboration software at http://cardmeeting.com that I hope to
> integrate James with at some point as the project matures and
> notifications are needed.  If I didn't have CardMeeting, I'd probably
> take you up on your suggestion - I feel like James is one of the most
> important Apache top level projects and there's not enough visibility on
> it yet.  A lot of glory yet to be had.  :)

:-) thank you for the flowers. stay tuned!

  Bernd

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





---------------------------------------------------------------------------
This e-mail message (including attachments, if any) is intended for the use
of the individual or entity to which it is addressed and may contain
information that is privileged, proprietary , confidential and exempt from
disclosure.  If you are not the intended recipient, you are notified that
any dissemination, distribution or copying of this communication is
strictly prohibited.  If you have received this communication in error,
please notify the sender and erase this e-mail message immediately.
---------------------------------------------------------------------------


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

Reply via email to