[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [equinox-dev] Eclipse for Server-side environments
|
Definite interest on this side.
Jeff
"Kaegi, Simon"
<Simon.Kaegi@xxxxxxxxxx>
Sent by: equinox-dev-bounces@xxxxxxxxxxx
05/30/2005 03:16 PM
|
Please respond to
Equinox development mailing list |
|
|
To
| "Equinox development
mailing list" <equinox-dev@xxxxxxxxxxx>
|
|
cc
|
|
|
Subject
| [equinox-dev] Eclipse for
Server-side environments |
|
I'm interested in doing work on
the Eclipse framework to allow it to run embedded as part of a servlet
application.
In this environment each servlet
application can launch it's own independently configured instance of Eclipse.
This has three implications:
- Several instances of Eclipse
might be running in the same JVM
- Eclipse can't control how resources
on the JVM's bootloader have been configured or initialized.
- The servlet application needs
a communication channel to interact with the Eclipse framework
EclipseStarter alludes to start-up
from a Servlet, but in practice it's a bit tricky for a few reasons:
1) A few of the VM's singleton
operations are called during initialization -- e.g. URL.setURLStreamHandlerFactory.
If these operations have already been called by the servlet container (or
another instance) the framework aborts.
2) System properties are used
for configuring the framework. This defeats the notion of independently
configured instances.
3) Can't access resources/classes
on the servlet classpath (by default the parent classloader is set to use
the Boot ClassLoader) You can use the System property "osgi.parentClassloader=fwk"
to force launching using the servlet classpath however this dramatically
reduces the modularity benefits of Eclipse
The first two collectively fall
under work with the broader goal of "running independent instances
of Eclipse in the same VM".
The third is more a question of
having the facilities to save the launching application's classloader and
then use it selectively where desired (perhaps something like "Eclipse-BuddyPolicy:
fwk" if it existed.)
I'd be keen to contribute to an
effort to resolve these issues in the 3.2 time frame.
Is this work of interest to anyone
else?
I have a prototype (based on 3.1M7
- handles the first two issues) that I'd be willing to polish and contribute
to foster discussion.
-Simon
From: equinox-dev-bounces@xxxxxxxxxxx
[mailto:equinox-dev-bounces@xxxxxxxxxxx] On Behalf Of Jeff McAffer
Sent: Thursday, May 19, 2005 11:39 PM
To: Equinox development mailing list
Subject: Re: [equinox-dev] How should one propose a new Work Area
Simon,
What do you have in mind? The best way is to put out some ideas and
see if they fit into the overall theme of Equino and if there are people
interested in working on them.
Jeff
--
Hi,
I'm wondering how one should go about proposing a new work area?
Thanks.
-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.
Cognos Forum
Our Annual Customer Conference
Orlando, June 26-29, 2005
Best Practices.
Tips and Techniques. Expert Advice.
Get more from your Cognos investment.
Register today at www.cognos.com/cognosforum_______________________________________________
equinox-dev mailing list
equinox-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/equinox-dev
