[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [equinox-dev] Embedding Equinox OSGi and EclipseStarter

Thanks Jeff and sorry for delayed reply everyone.

Whereas FrameworkAdmin API was originally desinged for launching a framework by a
bundle running on a framework (n -> n+1), I modified FrameworkAdmin API
and its implementation for Equinox so that Java program can launch a framework with specified bundles
installed and started (0 -> 1) in framework independent way.

The difference between two is on the point how to get FrameworkAdmin
*Used By a bundle on a running framework:
	get a FrameworkAdmin object from service registry.
- In order to get a proper object for the target framework
implementation, filtering service properties is used.
*Used By a java Program:
	get a FrameworkAdmin object by FrameworkAdminFactory.getInstance(name).
- In order to get a proper object for the target framework
implementation, specifying "magic name of FrameworkAdminFactory
implementation for the target framework", which should be declared by
the implementator in advance.
The codes after getting the object between two has no difference,
Please remind that 

* Originally current FrameworkAdmin API supports launching a framework
not in the same process but only in a different process.
- Supporting launch in the same process is one of the future work.

* It doesn't provide ways how to control the framework launched by this
API ( running in a different process in the current FrameworkAdmin).
- After launching, you will be able to access your own management agents
  bundle or to communicate with equinox console via telnet.

If you want just to launch with some bundles installed and
started in a different process from Java program, you can use this API.
If you want to realize more than that even launching in a different
process or you want to launch in a same process, you need other ways.


Please use it and give your opinion or request for it !

On Wed, 14 Feb 2007 21:36:07 -0500
Jeff McAffer <Jeff_McAffer@xxxxxxxxxx> wrote:

Jeff> Interestingly this exact same situation came up on the Spring OSGi list...
Jeff> Anyway, Ikuo is going to outline how the Framework Admin stuff can be used 
Jeff> to start the first framework as well.  There is some trickiness because 
Jeff> you need to somehow "discover" the support for launching the different 
Jeff> frameworks.  If you are in OSGi you can look up a service with the right 
Jeff> properties.  In plain Java you have to use some antiquated technique.  In 
Jeff> all likelihood the one you want to use will depend on the situation so the 
Jeff> best Ikuo can likely provide is a couple examples that people can adapt.
Jeff> Jeff
Jeff> "Alex Blewitt" <alex.blewitt@xxxxxxxxx> 
Jeff> Sent by: equinox-dev-bounces@xxxxxxxxxxx
Jeff> 02/13/2007 04:12 AM
Jeff> Please respond to
Jeff> Equinox development mailing list <equinox-dev@xxxxxxxxxxx>
Jeff> To
Jeff> "Equinox development mailing list" <equinox-dev@xxxxxxxxxxx>
Jeff> cc
Jeff> Subject
Jeff> Re: [equinox-dev] Embedding Equinox OSGi and EclipseStarter
Jeff> On 13/02/07, Jeff McAffer <Jeff_McAffer@xxxxxxxxxx> wrote:
Jeff> >
Jeff> > not sure if anyone pointed this out...
Jeff> >
Jeff> > http://wiki.eclipse.org/index.php/Equinox_FrameworkAdmin
Jeff> Interesting (and no, they hadn't) but not quite what I had in mind. I
Jeff> need to go from 0 to 1 OSGi frameworks, not from 1 to 1+, so having a
Jeff> bundle to do the launching isn't quite what I'd need, unless there's a
Jeff> 'safe' subset that can run as a Jar as well. Looking through the
Jeff> documentation the focus does seem to be more running as a bundle
Jeff> rather than a standalone Jar.
Jeff> Alex.
Jeff> _______________________________________________
Jeff> equinox-dev mailing list
Jeff> equinox-dev@xxxxxxxxxxx
Jeff> https://dev.eclipse.org/mailman/listinfo/equinox-dev

NTT Cyber Solutions Laboratories

     Ikuo YAMASAKI
        E-mail: yamasaki.ikuo@xxxxxxxxxxxxx