Re: [equinox-dev] replaceable OSGi runtime again

[Danail Nachev <d_nachev@xxxxxxxxxx>]

Not exactly:)

Currently, this bundle contains a classes, which enable registry
deployment on frameworks different than Equinox. I wonder at what goal
this bundle aims:
- support Equinox bundles (registry, preferences, etc.). In other words,
this bundle will support the bundles which are developed in Equinox project
- support bundles initially written for Equinox. In other words, enable
the deployment of a bundle, which was developed on Equinox framework and
later deployed on another framework.

If the bundle aims at the second goal, then I think that there are
packages which should be included in the supplement bundle. Those are
the public packages (not marked with x-internal or x-friends directives)
exported by org.eclipse.osgi bundle (such as
org.eclipse.osgi.framework.eventmgr and
org.eclipse.osgi.service.environment). Because their use isn't
discouraged, the chance that they will be used is big.

Another question here is, which exactly bundles are planned to be
available on other frameworks (assuming that the target framework
implements all needed OSGi features)?
...

I see that I have missed this discussion. Only the registry is to be
supported. As it seems, this discussion will be postponed for the next
release.

BR,
Danail

Jeff McAffer wrote:
> 
> The supplement bundle is intended to capture those parts of the Equinox
> framework implementation that are not available when running other
> frameworks (or in some cases, without OSGi).  It is literally a subset
> of the full framework (check outhe org.eclipse.osgi project structure).
> 
> I'm not sure if this answers your question.
> Jeff
> 
> 
> 
> *Danail Nachev <d_nachev@xxxxxxxxxx>*
> Sent by: equinox-dev-bounces@xxxxxxxxxxx
> 
> 02/27/2007 05:13 AM
> Please respond to
> Equinox development mailing list <equinox-dev@xxxxxxxxxxx>
> 
> 
> 	
> To
> 	Equinox development mailing list <equinox-dev@xxxxxxxxxxx>
> cc
> 	
> Subject
> 	Re: [equinox-dev] replaceable OSGi runtime again
> 
> 
> 	
> 
> 
> 
> 
> 
> Another question which is related is what is purpose of supplement
> bundle - is it providing support for equinox bundles (registry,
> preferences, etc) on other frameworks or its purpose can be extended to
> support bundles written for Equinox framework and deployed on different
> framework?
> 
> Danail Nachev wrote:
>> Hi,
>>
>> I'm not very sure where this discussion should take place - here or
>> dsdp-ercp-dev mail list. I'm posting it here, because the previous
>> discussion was here and because equinox project should be interested in
>> this.
>>
>> So, there is a goal in eRCP project, described in short here:
>>
>> http://dev.eclipse.org/mhonarc/lists/equinox-dev/msg01578.html
>>
>> Now I can see that we are almost there. However, there are two things,
>> which concern me:
>>
>> 1. update.configurator checks whether the org.eclipse.osgi bundle is in
>> ACTIVE state. I don't know if this is necessary. If this check is
>> needed, perhaps it should be replaced with something more decoupled like
>> checking for particular service?
>>
>> 2. core.runtime bundle require org.eclipse.osgi bundle. This was already
>> discussed. The conclusion was that it can't be fixed for now because of
>> the backward compatibility. However, here is one crazy idea, which is
>> not ideal, but it is a start:
>>
>> core.runtime is modified to require org.eclipse.osgi and
>> equinox.supplement optionally and reexport them. This way, when you
>> deploy the core.runtime bundle, it will import the available bundle
>> (org.eclipse.osgi on Equinox and equinox.supplement on other frameworks)
>> and reexport it. The equinox.supplement's exports can be extended via
>> fragment manifest, so the adapter bundle can modify the supplement
>> bundle's class space to be roughly the same as org.eclipse.osgi class
>> space. This way, you should be able to deploy core.runtime without
>> modification.
>>
>> Also I think that we should provide a document, describing how Eclipse
>> runtime can be deployed on other frameworks. This will ease the
>> integration of eRCP on devices where OSGi framework is already
>> available. Does such document already exist?
>>
>> Because I hadn't chance to test anything those are things, which I was
>> able to spot by examining the current source tree. I will try to come
>> back with more details when I had a chance to run some code.
>>
>> Kind regards,
>> Danail
>> _______________________________________________
>> equinox-dev mailing list
>> equinox-dev@xxxxxxxxxxx
>> https://dev.eclipse.org/mailman/listinfo/equinox-dev
>>
>>
> 
> -- 
> -------------------------------------------------
> Danail Nachev . Software Engineer/Development Tools
> ProSyst Labs EOOD
> 1606 Sofia, Bulgaria . 48 Vladajska Str.
> Phone:  +359 (0)2 952 35 81/102 . Fax +359 (0)2 953 26 17
> http://www.prosyst.com . d_nachev@xxxxxxxxxx
> -------------------------------------------------
> stay in touch with your product.
> -------------------------------------------------
> _______________________________________________
> 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