Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
RE: [equinox-dev] Eclipse Server-Side Platform

Hi Dennis,
 
The proposal looks interesting and covers a number of important areas. I'll try to comment and ask questions on your list when I get the chance..
I believe that some of the work done here is an enabler for aspects of your integration in server-side environments.
 
IMO the most fundamental problems associated with embedding Equinox in an appserver were addressed in 3.2M4.
As it stands today (with a little work) you can safely launch and integrate with Equinox in the context of a single web application.
Similar integration could be done with other application containers and I'm definitely interested in lending a hand.
 
Improvements are still needed to allow multiple independently configured instances of Equinox to run in the same VM.
Naturally, I'd really like to see these changes made it in time for the 3.2 release, but there is a fair bit of work and validation to do.
I'm hopeful, but we'll see.
 
-Simon


From: equinox-dev-bounces@xxxxxxxxxxx [mailto:equinox-dev-bounces@xxxxxxxxxxx] On Behalf Of O'Flynn, Dennis
Sent: Tuesday, January 03, 2006 1:20 PM
To: 'equinox-dev@xxxxxxxxxxx'
Subject: [equinox-dev] Eclipse Server-Side Platform

I’m with Compuware working on our proposed project to extend the value of the Eclipse platform to the server-side.  We plan on basing our project on Eclipse 3.2 to leverage OSGi R4 services.  In addition, the Equinox incubator project (http://www.eclipse.org/equinox/incubator/server/) also has some features that are of interest.

 

We would like some feedback on the following:

1)     Comments re: our proposed project (http://www.eclipse.org/proposals/corona/).

2)     What is the probability that some of the Equinox incubator work will find its way into the 3.2 release?

 

Thanks,

-Dennis O’Flynn

 



The contents of this e-mail are intended for the named addressee only. It contains information that may be confidential. Unless you are the named addressee or an authorized designee, you may not copy or use it, or disclose it to anyone else. If you received it in error please notify us immediately and then destroy it.


 
     This message may contain privileged and/or confidential information.  If you have received this e-mail in error or are not the intended recipient, you may not use, copy, disseminate or distribute it; do not open any attachments, delete it immediately from your system and notify the sender promptly by e-mail that you have done so.  Thank you.

Back to the top