RE: Re[2]: [platform-core-dev] Can I use Eclipse Platform Corefunctional

[Jeff McAffer <Jeff_McAffer@xxxxxxxxxx>]

Kai, 

Yes to all.  Keep in mind my earlier
comment that the extension registry is quite independent of OSGi.  The
goal here would be to have the extension registry out there as a completely
stand-alone piece.  I don't quite think that what you are proposing
will work well.  OSGi expects to be "on top" and create
classloaders for everything.  You can "start" OSGi from
you Java application but interacting with it will be a challenging exercise
in reflective programming.  

I suggest you look at stripping the
extension registry out of the runtime and using it standalone.  If
you do that, please contribute your experiences back. This is definitely
something that we want to look at doing.

Jeff

"Kai Shen" <kshen@xxxxxxxxxxx>
Sent by: platform-core-dev-bounces@xxxxxxxxxxx

04/13/2005 06:26 PM

Please respond to
"Eclipse Platform Core component developers list."

To	"Eclipse Platform Core component developers list." <platform-core-dev@xxxxxxxxxxx>, "Glyn Normington" <glyn_normington@xxxxxxxxxx>
cc
Subject	RE: Re[2]: [platform-core-dev] Can I use Eclipse Platform        Corefunctionality outside Eclipse?

Follow Glyn's link, I found Equinox Framework Layering.
Hey, Glyn, you
guys are doing something really cool!

It's nice to be able to run Eclipse OSGi framework stand alone. I guess
then I can start the OSGi framework in the main Java program without
having to start another classloader, right? I understand the Eclipse
runtime platform depends on the OSGi framework. If I can start the OSGi
framework stand alone, can I continue to start Eclipse runtime platform?
We'd like to use Eclipse's extension management mechanism (e.g.
ExtensionRegistry, etc.) in the main Java program.

In my opinion, OSGi and org.eclipse.core.runtime are the base of
Eclipse, logically they don't depend on other plug-ins in Eclipse. If we
can make OSGi and core.runtime a standalone component, it will be
wonderful, because then this kernel part (Let's call it "Eclipse
Extension Framework") can be used widely in other Java applications
that
want to use Eclipse's extension mechanism. When people develop their
Java application (either server or client app), they can leave some
extension points in their application and let others to contribute
plug-ins. Other people can use Eclipse to develop their plug-ins. And
the main application will use the "Eclipse Extension Framework"
to
handle those plug-ins (including bundle management, classloading and
extension point management, etc). Doesn't it sound great?

Anyway, it's just my thought when I was reading the responses. Thanks
everyone for participating in this discussion.

Kai

-----Original Message-----
From: platform-core-dev-bounces@xxxxxxxxxxx
[mailto:platform-core-dev-bounces@xxxxxxxxxxx] 

GN> Hi Kai,

GN> It's possible to run the Eclipse OSGi framework stand alone ([1]).
GN> However, I suspect the framework calls the "one shot"
GN> java.net.URL.setURLStreamHandlerFactory, which I gather conflicts
GN> with your server code.

GN> Glyn

GN> [1]
GN> http://dev.eclipse.org/viewcvs/indextech.cgi/~checkout~/equinox-home
GN> /layering/standalone.html

GN> Telephone: +44-(0)1962-815826. Email: glyn_normington@xxxxxxxxxx

GN> _______________________________________________
GN> platform-core-dev mailing list
GN> platform-core-dev@xxxxxxxxxxx
GN> https://dev.eclipse.org/mailman/listinfo/platform-core-dev
_______________________________________________
platform-core-dev mailing list
platform-core-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/platform-core-dev