[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
RE: [equinox-dev] OSGi for Server-side...

Tom asked...
> Do you have an idea of what projects would be included in this
> incubator? (org.eclipse.osgi, org.eclipse.core.runtime etc.)
 
Good question. I'm thinking about those in the RCP minus the UI plugins.
org.eclipse.osgi (definitely)
org.eclipse.core.runtime (definitely)
 
org.eclipse.update.configurator (maybe)
(I've run with and without but generally find it convenient)
(Important for anyone who wants to work with org.eclipse.update.core)
 
Also:
org.eclipse.core.runtime.compatibility (??)
(I wonder if it's safe to drop this? -- I'm currently maintaining changes here)
 
--
 
> ...it may be helpful to provide a list of the issues or at least post the
> existing bugs related to this area
 
I'll try...
1) Running when someone else has set the URL and URLConnection singletons needed by the URLHandlerService
    - patched but needs polishing
2) Using the Conditional Permission Admin Service when someone else has set the SecurityManager.
    - avoided this so far but it's an important consideration in some server-side environments
  - without control of the SecurityManager we lose the capability to do postponed decisions (?)
    - What are the repercussions? Is there something we can do about it?
3) Use of System Properties and other globals
  - prevents independently configured instances from running
  - Changes are cross-cutting and potentially hazardous to backwards compatibility.
4) Communication between Eclipse and the outside world and vice-versa
  - good possibility of a code contribution here (at least for a servlet container scenario)
5) Ensuring long term stability in terms of system resource usage.
    - ensuring that bundles are well behaved and allow GC to happen
   (this is really just ongoing work relevant to the platform as a whole)
  - ensuring that Equinox can be shutdown and restart cleanly
 
In terms of necessary bug patches - 107909 and 112646 are the only ones that really impede progress.
Would it be reasonable to start with just those two and then follow the 3.2 HEAD for other fixes?
 
-Simon
 
 


From: equinox-dev-bounces@xxxxxxxxxxx [mailto:equinox-dev-bounces@xxxxxxxxxxx] On Behalf Of Jeff McAffer
Sent: Monday, October 24, 2005 11:56 AM
To: Equinox development mailing list
Subject: Re: [equinox-dev] OSGi for Server-side...


+1 to the initial idea.

As Simon and Tom point out, some of this work is going on already but it is disjoint and hard to pull together.  An incubator is the perfect cure for the technical problems as well as giving a focal point to the work.  

To move forward on this we should pull together a proposal that scopes the work to be done.  This helps new people understand what work is being done so they can join in or propose additional work and/or usecases.  It would be good to outline some scenarios that should be addressed if the incubator is successful as well as some thoughts on timing (e.g., is this something for 3.2 or longer term or ...)

The proposal need not be complex/long, just think of what you would want the incubator website to say.

Oh yeah, and you need a name.  Without getting too fancy, perhaps something like "Server-side" (e.g., The Equinox Server-side incubator).

Jeff



Justin Deoliveira <jdeolive@xxxxxxxxxxxxxxxx>
Sent by: equinox-dev-bounces@xxxxxxxxxxx

10/24/2005 11:26 AM

Please respond to
Equinox development mailing list

To
Equinox development mailing list <equinox-dev@xxxxxxxxxxx>
cc
Subject
Re: [equinox-dev] OSGi for Server-side...





Hello all,

I have recently joined this list and this topic is the reason why. I
found a bug report filed by Simon that contains a list of patches.

https://bugs.eclipse.org/bugs/show_bug.cgi?id=107909

So what from what I can gather work on this issue lives in the form of
these patches? And a new incubator is how you plan on moving them in?

Thanks,

Justin

Thomas Watson wrote:
>
> +1
>
> I have seen a lot of interest in this area and there are various
> enhancement bugs already in progress in this area.  It would be helpful
> to start an incubator to flush out all the details and build a community
> to provide feedback and test out the ideas we have.
>
> Do you have an idea of what projects would be included in this
> incubator? (org.eclipse.osgi, org.eclipse.core.runtime etc.)
>
> I'm familiar with the issues Simon is talking about for the server side,
> but it may be helpful to provide list the issues or at least post the
> existing bugs related to this area.  Thanks.
>
> Tom
>
>
>
> *"Kaegi, Simon" <Simon.Kaegi@xxxxxxxxxx>*
> Sent by: equinox-dev-bounces@xxxxxxxxxxx
>
> 10/24/2005 09:57 AM
> Please respond to
> Equinox development mailing list
>
>
>                  
> To
>                  "Equinox development mailing list" <equinox-dev@xxxxxxxxxxx>
> cc
>                  
> Subject
>                  [equinox-dev] OSGi for Server-side...
>
>
>                  
>
>
>
>
>
> Hi all,
>
> I'd like to suggest that we create an incubator to hold current work for
> embedding Equinox/Eclipse in server-side environments. The current
> process of getting a series of slightly out of date patches and applying
> them to the HEAD is error-prone and impedes further improvement. What
> I'd like to see is something approaching a ready made environment where
> developer's can dig into the integration issues.
>
> At this stage I'm just trying to gauge interest. What do you think?
>
> -Simon
>
>  
>         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.
>
>         _______________________________________________
> equinox-dev mailing list
> equinox-dev@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/equinox-dev
>
>
> ------------------------------------------------------------------------
>
> _______________________________________________
> equinox-dev mailing list
> equinox-dev@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/equinox-dev


--
Justin Deoliveira
The Open Planning Project
http://topp.openplans.org
_______________________________________________
equinox-dev mailing list
equinox-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/equinox-dev

 
       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.