// office: +1 386 848 1781OSGi Fellow and OSGi Specification Project lead // mobile: +1 386 848 3788hargr...@us.ibm.com
- Original message -From: BJ Hargrave/Austin/IBMTo: osgi-dev@mail.osgi.orgCc:Subject: Time to moveDate: Wed, Dec 9, 2020 15:41
As part of the mission transfer
As part of the mission transfer to the Eclipse Foundation, the osgi.org and mail.osgi.org servers will be soon shutting down.
So I have asked Eclipse [1] to provision a new osgi-users mail list to replace this osgi-dev mail list. Once provisioned, the new list [2] should be
I kind of like the idea of Optional for field injection. As Neil says, it is short hand for cardinality=ReferenceCardinality.OPTIONAL.
Since R8 supports, Java 8 as the base language level, we can now add support for Optional as a field (and constructor) injection type. Bnd can infer the actual
An open source project for OSGi testing [1] has been working on better support for testing in OSGi environments. We are pleased to announce a first release [2]. Part of the work in this project was to help the AssertJ and JUnit 5 projects make better bundles for use in testing in OSGi environments
I thought Core R8 draft was already at https://www.osgi.org/developer/specifications/drafts/ but it was not. So I put it there.
We are looking to finalize technical work on Core R8 this month. Publication will be 2 months or so later.
I don't have dates to share on Compendium R8.
--BJ
You can of course infer the proper names for osgi.ee names for al recent Java SE releases. The list on the web page may be behind. See https://github.com/bndtools/bnd/blob/master/biz.aQute.bndlib/src/aQute/bnd/build/model/EE.java for the latest list in Bnd.
OSGi is no longer making execution
Your bundle needs to import the PubNub API package which means some other bundle must export the package. So you need to find or make a bundle which exports the PubNub API.
Note: The PubNub code may not work properly in an OSGi environment if it make certain assumptions about the class loading
‐‐‐ Original Message ‐‐‐
On Wednesday 11 March 2020 14:19, Raymond Auge wrote:
Hi Clément,
You may want to also look at https://blog.osgi.org/2020/01/to-embed-or-not-to-embed-your-api.html
:)
- Ray
On Wed, Mar 11, 2020 at 9:16 AM BJ Hargrave via osgi-dev <osgi-dev@mail.osgi.org
Since both bundles B and C offer to export the api.a package, the framework could resolve both bundles to each export the package. Thus you can end up with 2 exports of the api.a package in the framework. So bundle D will import api.a from either bundle B or bundle C and thus will not be able to
If you are using an API which takes a filter _expression_, the filter _expression_ must be well formed. This can include escaping any characters which would otherwise be interpreted as part of the _expression_ language.
The spec,
You can look here https://en.wikipedia.org/wiki/OSGi_Specification_Implementations
--BJ HargraveSenior Technical Staff Member, IBM // office: +1 386 848 1781OSGi Fellow and CTO of the OSGi Alliance // mobile: +1 386 848 3788hargr...@us.ibm.com
- Original message -From: "Clément
Nailed it!
--BJ HargraveSenior Technical Staff Member, IBM // office: +1 386 848 1781OSGi Fellow and CTO of the OSGi Alliance // mobile: +1 386 848 3788hargr...@us.ibm.com
- Original message -From: Raymond Auge via osgi-dev Sent by: osgi-dev-boun...@mail.osgi.orgTo: Milen Dyankov via
Configuration Plugins mutate configuration data each time it is delivered to a configuration target. So the Configuration Plugin must be active before any configuration targets which care about the mutated configuration data.
So this is orthogonal to Configurator which is about putting
Perhaps platform depends upon something which is no longer active?
Since these exceptions seem to be from Eclipse plugins, perhaps Eclipse people can be of more specific help here?
From the spec point of view, bundles in higher start levels are stopped before bundles at lower start levels. I
Factory configurations (in ConfigAdmin) and ComponentFactory (in DS) do not work together. They are mutually exclusive There can be only one thing in charge of making multiple instances of a component.
It can be either factory configurations (in ConfigAdmin), in which case a component instance
of the OSGi Alliance // mobile: +1 386 848 3788hargr...@us.ibm.com
- Original message -From: Peter Kriens To: BJ Hargrave Cc: via bndtools-users , osgi-dev@mail.osgi.orgSubject: [EXTERNAL] Re: [osgi-dev] Conditional TargetDate: Wed, Jun 26, 2019 10:27 I was vaguely aware of this RFC
This seems just like https://github.com/osgi/design/blob/master/rfcs/rfc0242/rfc-0242-Condition-Service.pdf
Are you making an alternate design? Or did you not know of this RFC?
--BJ HargraveSenior Technical Staff Member, IBM // office: +1 386 848 1781OSGi Fellow and CTO of the OSGi Alliance //
Bnd supports Gradle and Maven. So you can use Gradle if you prefer (I personally prefer Gradle.)
OSGi enRoute is now using Maven since it is, by far, much more popular than Gradle. But a Gradle variant of enRoute could also be made. But it is more work to dual maintain the variants. So with
Michael,
Can we please step back to the beginning and describe, in much more detail, the issue you are seeing? I never understood the actual issue you seemed to be having.
--BJ HargraveSenior Technical Staff Member, IBM // office: +1 386 848 1781OSGi Fellow and CTO of the OSGi Alliance //
With OSGi's JAX-RS support [1], you can easily publish and consume RESTy endpoints in your OSGi application.
So there is no need to "leave" OSGi to participate in a microservice environment.
[1]: https://osgi.org/specification/osgi.enterprise/7.0.0/service.jaxrs.html
--BJ HargraveSenior
still controls the lifecycle and coming/going of referenced services/components.
Would such an API make sense? Or would it even be possible?
I think in general this would be very useful in order to create OSGi integrations for third-party libs that need to interact with DS in OSGi.
I hope
See https://github.com/osgi/osgi.enroute/commit/32c54eb654a86e4cd79a80b2e7c5dd659962c44a
--BJ HargraveSenior Technical Staff Member, IBM // office: +1 386 848 1781OSGi Fellow and CTO of the OSGi Alliance // mobile: +1 386 848 3788hargr...@us.ibm.com
- Original message -From: Thomas
You should report this to the Apache Felix SCR JIRA component. That is where the Felix SCR developers can respond to the exception.
--BJ HargraveSenior Technical Staff Member, IBM // office: +1 386 848 1781OSGi Fellow and CTO of the OSGi Alliance // mobile: +1 386 848 3788hargr...@us.ibm.com
There is not a way for a Designate element to alter the OCD to which it refers. So it would be up to any UI to detect that multiple Designates refer to the same OCD and generate a UI which can disambiguate them. So Felix Web Console should be updated.
--BJ HargraveSenior Technical Staff Member,
Thanks for the feedback. I have added a paragraph break to the source file so the next release will have it.
--BJ HargraveSenior Technical Staff Member, IBM // office: +1 386 848 1781OSGi Fellow and CTO of the OSGi Alliance // mobile: +1 386 848 3788hargr...@us.ibm.com
- Original message
There are framework events which indicate the framework has started: https://osgi.org/specification/osgi.core/7.0.0/framework.lifecycle.html#d0e8798
But the larger question is "When have all the bundles completed their initialization and are ready for work?". This is a harder question to answer
The OSGi framework know about things registered via the OSGi framework API such as services and framework listeners. The OSGi framework does not know about everything in the JVM such as threads, open files, open sockets, etc. So it cannot manage them for a bundle. So your bundle need to manage the
Did you try
http://www.osgi.org/xmlns/repository/v1.0.0" name="example"> value="org.apache.felix.framework"/> value="osgi.bundle"/> value="6.0.1" type="Version"/>
Note the use of the local
This should be fixed now.
--BJ HargraveSenior Technical Staff Member, IBM // office: +1 386 848 1781OSGi Fellow and CTO of the OSGi Alliance // mobile: +1 386 848 3788hargr...@us.ibm.com
- Original message -From: Konrad Windszus via osgi-dev Sent by: osgi-dev-boun...@mail.osgi.orgTo:
No. But you can get that from BundleContext which you can have injected.
--BJ HargraveSenior Technical Staff Member, IBM // office: +1 386 848 1781OSGi Fellow and CTO of the OSGi Alliance // mobile: +1 386 848 3788hargr...@us.ibm.com
- Original message -From: Alain Picard via
You can file a bug in the OSGi public bugzilla: https://osgi.org/bugzilla
--BJ HargraveSenior Technical Staff Member, IBM // office: +1 386 848 1781OSGi Fellow and CTO of the OSGi Alliance // mobile: +1 386 848 3788hargr...@us.ibm.com
- Original message -From: Thomas Driessen via
Equinox has the LogService implementation built into the framework, so it starts logging very early.
In the alternate, for framework related information, you can write your own launcher and it can add listeners for the framework event types.
--BJ HargraveSenior Technical Staff Member, IBM //
#the-integration-testbndrun for some information on this.
--BJ HargraveSenior Technical Staff Member, IBM // office: +1 386 848 1781OSGi Fellow and CTO of the OSGi Alliance // mobile: +1 386 848 3788hargr...@us.ibm.com
- Original message -From: "Matthews, Kevin" To: BJ Hargrave Cc:
HargraveSenior Technical Staff Member, IBM // office: +1 386 848 1781OSGi Fellow and CTO of the OSGi Alliance // mobile: +1 386 848 3788hargr...@us.ibm.com
- Original message -From: "Matthews, Kevin" To: BJ Hargrave , "osgi-dev@mail.osgi.org" Cc:Subject: RE: [osgi-dev]
The most recent versions of the gradle and maven support will make the project's dependencies available as bundles to the bndrun files.
For example:
: [osgi-dev] Tool/API to analyze component dependenciesDate: Tue, Jul 17, 2018 8:07 AM
Thanks BJ, from what I see that will do the trick, expect that it is runtime, but I can live with that.
Alain
On Tue, Jul 17, 2018 at 7:58 AM BJ Hargrave <hargr...@us.ibm.com> wrote
Look at the ServiceComponentRuntime service: https://osgi.org/specification/osgi.cmpn/7.0.0/service.component.html#service.component-introspection
It provides access to DTOs which describe each component description, ComponentDescriptionDTO, and actual component instances,
The import range in CNS says it will work with any version 1.x of com.foo. So the resolver is free to resolve CNS to use any 1.x version of the package com.foo. You can control the version sources by limiting which bundles are installed. If you want to get really fancy, you can implement a
Component properties are basically service properties which are basically meant to be things that can go in a Configuration: https://osgi.org/specification/osgi.core/7.0.0/framework.module.html#i3217016. Complex objects including objects implementing functional interfaces are not in scope for a
You can see what I have done for an SLF4J binding for the OSGi Log Service 1.4 spec in R7 at https://github.com/osgi/slf4j-osgi. I will note I have not tried it in a while, so it may be in need of some attention.
--BJ HargraveSenior Technical Staff Member, IBM // office: +1 386 848 1781OSGi Fellow
The OSGi Logger does not have a bundle which sends the log to the console. It may be a nice addition to enRoute to add a bundle which collects the log entries (perhaps via a LogStream) and formats them for output to the console.
--BJ HargraveSenior Technical Staff Member, IBM // office: +1 386 848
Yes. If the -runfw cannot be located, the launcher can manifest an error like this.
--BJ HargraveSenior Technical Staff Member, IBM // office: +1 386 848 1781OSGi Fellow and CTO of the OSGi Alliance // mobile: +1 386 848 3788hargr...@us.ibm.com
- Original message -From: Paul F Fraser
Delete the Service-Component header. Bnd will add it if necessary for any DS components.
--BJ HargraveSenior Technical Staff Member, IBM // office: +1 386 848 1781OSGi Fellow and CTO of the OSGi Alliance // mobile: +1 386 848 3788hargr...@us.ibm.com
- Original message -From: Henrik
I am not sure what your question is. What I saw on the vaadin link should work fine. The bnd-maven-plugin will use the bnd.bnd file in the project for bnd instructions.
--BJ HargraveSenior Technical Staff Member, IBM // office: +1 386 848 1781OSGi Fellow and CTO of the OSGi Alliance // mobile: +1
I made a PR to change to change to 4.0.0 from snapshot.
--BJ HargraveSenior Technical Staff Member, IBM // office: +1 386 848 1781OSGi Fellow and CTO of the OSGi Alliance // mobile: +1 386 848 3788hargr...@us.ibm.com
- Original message -From: Tim Ward via osgi-dev
Yes, this is the way to use the new Logger API with DS < 1.4. DS 1.4 has specific support to call to the getLogger method for the component so that you can use field and constructor injection. But to use the new Logger API with DS 1.3 and lower, you will need to method inject the LoggerFactory and
What version of the Bnd Gradle plugin are you using? There is an issue where newer versions of Gradle can delete output folders (like bin) after Bnd thought it created them. So the builder complained.
This has been fixed for 4.0 with
The R7 final API jars are already built and ready for release to Maven Central once the OSGi members approve the specifications as final (ETA mid April). These jars do not have Automatic-Module-Name manifest entries in them. Just adding that is only a partial step. Unless you also test those jars
You could do this by using a component factory. You would need another component to get the ComponentFactory service and call ComponentFactory.newInstance with the desired endpoint.framework.uuid service property.
But this is probably overkill for a single service. For a single service, you can
Tim correctly cites the spec regarding the order SCR must process the elements in the XML. Since you are using annotations, there is one more thing to know. The javadoc for the Reference annotation states:
In the generated Component Description for a component, the references must be ordered in
You can get the snapshots from https://oss.sonatype.org/content/repositories/osgi/
--BJ HargraveSenior Technical Staff Member, IBM // office: +1 386 848 1781OSGi Fellow and CTO of the OSGi Alliance // mobile: +1 386 848 3788hargr...@us.ibm.com
- Original message -From: Thomas Driessen
The smart thing to do is to wait for the component's service to be
registered. This means that the component's dependencies are satisfied.
The component's bundle being active is just one such dependency but there
can be others.
--
BJ Hargrave
Senior Technical Staff Member, IBM
OSGi Fellow
Bar, you could potentially break users of Bar that directly
referenced the concrete method Bar.doFoo(). In fact I would think removing
doFoo() from Bar should be a major change. The safest thing is to leave
doFoo() in Bar and implement it as calling the super method.
--
BJ Hargrave
Senior
SCR always registers a ServiceFactory for the service since SCR must intermediate the service requests to construct the service object from your implementation class. So even though SCR registers ServiceFactory (which show as SCOPE_BUNDLE), since you have declared the component with
Better would also be for the API to not take a String class name but a Class object. The caller likely has access to the named class (or can easily be configured to have access), while the library code which has to load the class from the String class name generally does not which is why we have
тверг, 7 сентября 2017, 23:31 +03:00 от "BJ Hargrave" <hargr...@us.ibm.com>:
I am sorry I could not help you more. I don't have a detailed checklist of things to do.
What I am saying is that JPMS and OSGi can operate at different layers. They do not need to interact. Java 9 runt
eloper. I am OSGi user. I wrote to this mailing list to getclear technical solutions how to make JPMS and OSGi friends. I tell the truth -advices "set some options to ignore some messages" is not what I am looking for.Best regards, Alex
Четверг, 7 сентября 2017, 22:25 +03:00 от "BJ Har
7, 20:01 +03:00 от "BJ Hargrave" <hargr...@us.ibm.com>:
You can use OSGi on Java 9. Just like any other Java program. While the Java runtime class libraries are modularized with the Java Platform Module System (JPMS), your application running on the Java runtime can rema
You can use OSGi on Java 9. Just like any other Java program. While the Java runtime class libraries are modularized with the Java Platform Module System (JPMS), your application running on the Java runtime can remain modularized by OSGi. OSGi is not going to stop working on Java 9 :-) In other
From the javadoc of the Reference annotation:
The field option is based upon the policy and cardinality of the reference and the modifiers of the field. If the policy is ReferencePolicy.DYNAMIC, the cardinality is 0..n or1..n, and the field is declared final, the field option is
Thats is not a safe collection type. Why not let DS manage the field?
If you need to use a final field, then you need to use a thread safe collection.
--BJ HargraveSenior Technical Staff Member, IBM // office: +1 386 848 1781OSGi Fellow and CTO of the OSGi Alliance // mobile: +1 386 848
If you need to create unique component instances with specific service property values, then you would need to use ComponentFactory. However, then your components would need to reference the proper ComponentFactory and call it to create the desired instance.
@Component(factory="B") public
I assume you are using a Bnd workspace since you mention cnf/build.bnd. So you can set a version property in cnf/build.bnd for bundle versions which you can reference in Gradle. In a non-Bnd gradle sub-project, you can ask the workspace via rootProject.bndWorkspace which holds the Bnd Workspace
-From: Mark Raynsford <list+org.o...@io7m.com>Sent by: osgi-dev-boun...@mail.osgi.orgTo: osgi-dev@mail.osgi.orgCc:Subject: Re: [osgi-dev] Racing the BundleTrackerDate: Thu, Jun 1, 2017 6:34 AM
On 2017-05-31T22:27:59 +0000"BJ Hargrave" <hargr...@us.ibm.com> wrote:>
The BundleTracker uses SynchronousBundleListener to be able to see all the BundleEvent types including RESOLVED. So your use of the BundleTracker must follow the advice for users of SynchronousBundleListener. See the doc for SynchronousBundleListener.
Since SynchronousBundleListener are
You are free to use it. Try to avoid collisions with other users by using a subfolder with a unique name for you.
--BJ HargraveSenior Technical Staff Member, IBM // office: +1 386 848 1781OSGi Fellow and CTO of the OSGi Alliance // mobile: +1 386 848 3788hargr...@us.ibm.com
- Original
...@mail.osgi.orgTo: osgi-dev@mail.osgi.orgCc:Subject: Re: [osgi-dev] Error reporting?Date: Thu, May 25, 2017 3:50 PM
On 2017-05-25T19:35:52 +"BJ Hargrave" <hargr...@us.ibm.com> wrote:> Why not the BundleTracker code log to the LogService or even slf4j? Then any is
Why not the BundleTracker code log to the LogService or even slf4j? Then any issues are in the log.
--BJ HargraveSenior Technical Staff Member, IBM // office: +1 386 848 1781OSGi Fellow and CTO of the OSGi Alliance // mobile: +1 386 848 3788hargr...@us.ibm.com
- Original message -From:
I doubt it. The region bundles don't provide or require the capabilities themselves.
You will probably need to use the subsystem service to get the subsystem manifest and parse the headers yourself.
--BJ HargraveSenior Technical Staff Member, IBM // office: +1 386 848 1781OSGi Fellow and CTO of
ace).
Neil
On 4 May 2017, at 15:02, BJ Hargrave <hargr...@us.ibm.com> wrote:
This is not true from a binary compatibility point of view. See https://docs.oracle.com/javase/specs/jls/se7/html/jls-13.html#jls-13.4.15. Changing the return type is the equivalent of deleting the old method and a
This is not true from a binary compatibility point of view. See https://docs.oracle.com/javase/specs/jls/se7/html/jls-13.html#jls-13.4.15. Changing the return type is the equivalent of deleting the old method and adding a new method. So it is in fact a binary incompatible change: A major change
Semantic Versioning in OSGi is about binary compatibility and not source compatibility.
Adding a default method to an interface is always a minor version increment. For provider type interfaces, the consumer can depend upon the new method and must declare that by requiring the higher minor
Also, the controller component should not register a service. "@Component(service={})". If you say "service={}" then you are "immediate=true".
Maybe you should make an enroute app note for this?
--BJ HargraveSenior Technical Staff Member, IBM // office: +1 386 848 1781OSGi Fellow and CTO of the
So why isn't this just the case already? SCR processes the XML, cannot load the impl class and logs that in the log. End of story. When bundle resolves again later and can access the class, when SCR processes the XML, it can load the impl class and thus the component is good to go.
--BJ
When DS registers your component as a service, it already registers its own object implementing ServiceFactory. This is necessary to register the service while still allowing delayed activation of your component. So DS's ServiceFactory object is called by the framework when someone gets the
Yes. You need to use the correct property name: .cardinality.minimum. See 112.6.2.2 in the DS spec.
@ObjectClassDefinition
@interface MyConfiguration {
String name;
// this will make a property named stuff.cardinality.minimum
// which is the minimum cardinality for the
If you have any comments on and RFC or spec draft, please make them in the OSGi public bugzilla system as requested in the documents. Thanks.
--BJ HargraveSenior Technical Staff Member, IBM // office: +1 386 848 1781OSGi Fellow and CTO of the OSGi Alliance // mobile: +1 386 848
e will end up delegating to Log4j2 or Logback most likely (see pax-logging for example).
On 6 April 2017 at 13:58, BJ Hargrave <hargr...@us.ibm.com> wrote:
It is indeed a service. The spec writing for these changes are not in the draft spec so you can see https://github.com/osgi/design/blob
It is indeed a service. The spec writing for these changes are not in the draft spec so you can see https://github.com/osgi/design/blob/master/rfcs/rfc0219/rfc-0219-LogService-Update.pdf for some more detail/background on the change.
Also see https://github.com/osgi/slf4j-osgi which holds an
The ordering is the same regardless of whether the reference is static or dynamic.
I have clarified the text in 112.3.8.1 for this in the DS 1.4 spec.
--BJ HargraveSenior Technical Staff Member, IBM // office: +1 386 848 1781OSGi Fellow and CTO of the OSGi Alliance // mobile: +1 386 848
BTW, osgi.annotation does not contain DS annotations.
DS annotations are in osgi.cmpn and org.osgi.service.component.annotations.
--BJ HargraveSenior Technical Staff Member, IBM // office: +1 386 848 1781OSGi Fellow and CTO of the OSGi Alliance // mobile: +1 386 848 3788hargr...@us.ibm.com
Sure you can add it through the annotations. It is just a component property.
@Component(property="C.cardinality.minimum=4")
where C is the name of the reference to serviceC.
@Reference(name="C")
void setC(C c)
--BJ HargraveSenior Technical Staff Member, IBM // office: +1 386 848 1781OSGi
Yes, this is how I think it will work best: a tooling story. But Java 9 modules are not a finalized design yet, so the Bnd devs are not looking at anything to do this yet.
If you have ideas/opinions of this topic of Bnd changes, you should take it to the bndtools-users@ mail list.
--BJ
Seems like they should all be active. You may need to check with the felix-dev list about Felix SCR's handling of this.
--BJ HargraveSenior Technical Staff Member, IBM // office: +1 386 848 1781OSGi Fellow and CTO of the OSGi Alliance // mobile: +1 386 848 3788hargr...@us.ibm.com
-
Sounds like it wants Blueprint. Maybe just the API package, maybe the implementation. I would not expect a Blueprint implementation to run in jre embedded.
Have you looked at https://projects.eclipse.org/projects/technology.mosquitto ?
--BJ HargraveSenior Technical Staff Member, IBM // office:
Feb 14, 2017 2:45 PM
On 2/13/2017 10:07 AM, BJ Hargrave wrote:
Not in R6. Under discussion for R7 is a service property for the ServiceComponentRuntime service which would hold a change count for the DTO set. Then whenever the DTO set changes, the service properties for the ServiceComponentR
Not in R6. Under discussion for R7 is a service property for the ServiceComponentRuntime service which would hold a change count for the DTO set. Then whenever the DTO set changes, the service properties for the ServiceComponentRuntime service would change. So you could listen for MODIFIED service
Perhaps you should go through the tutorials then.
--BJ HargraveSenior Technical Staff Member, IBM // office: +1 386 848 1781OSGi Fellow and CTO of the OSGi Alliance // mobile: +1 386 848 3788hargr...@us.ibm.com
- Original message -From: "Leschke, Scott" Sent by:
I think that this list is not the forum to discuss jpm4j which is perhaps why it was suggested to take the discussion off list.
--BJ HargraveSenior Technical Staff Member, IBM // office: +1 386 848 1781OSGi Fellow and CTO of the OSGi Alliance // mobile: +1 386 848 3788hargr...@us.ibm.com
I am not aware of any support in -runbundles to set start levels for bundle. But the bnd launcher should start the bundle in the order they are specified on the -runbundles instruction. Did you try putting those bundles first that need to be started first?
--BJ HargraveSenior Technical Staff
12:35 AM
On 11/21/2016 8:11 AM, BJ Hargrave wrote:
If you want to create a specific number of services each configured by a factory configuration instance, then prototype scopes services are orthogonal to your needs.If not prototype scope services...for service instances configured by f
I think you need to ask this in a felix list since you are asking about how felix fileinstall works.
--BJ HargraveSenior Technical Staff Member, IBM // office: +1 386 848 1781OSGi Fellow and CTO of the OSGi Alliance // mobile: +1 386 848 3788hargr...@us.ibm.com
- Original message
There is a life cycle mismatch here. For a prototype scope service, a new instance is created for each consumer of the service. So there are potentially an infinite number of service instances.
For factory configurations, there are a finite number of configuration instances because someone has
No. All component instances for the prototype scope service share the same component properties. But each instance represents a different service consumer. This is much the same as a bundle scope service where each component instance has the same component properties but represents a different
As stated in the front matter of the RFC, you should provide feedback to the OSGi public bugzilla system at https://osgi.org/bugzilla/.
Thanks,
--BJ HargraveSenior Technical Staff Member, IBM // office: +1 386 848 1781OSGi Fellow and CTO of the OSGi Alliance // mobile: +1 386 848
Not really. Fragments are not bundle in that they do not have a class loader or a separate activation life. They can be attached to zero or more host bundles (non-fragment bundles). So to start them is not possible. To make it a no-op will break an invariant: After callings start, the bundle must
There is not such a method.
--BJ HargraveSenior Technical Staff Member, IBM // office: +1 386 848 1781OSGi Fellow and CTO of the OSGi Alliance // mobile: +1 386 848 3788hargr...@us.ibm.com
- Original message -From: Benson Margulies Sent by:
There is nothing specific to OSGi about execing external applications. That is just normal java.
--BJ HargraveSenior Technical Staff Member, IBM // office: +1 386 848 1781OSGi Fellow and CTO of the OSGi Alliance // mobile: +1 386 848 3788hargr...@us.ibm.com
- Original message -From:
That is just a downloading issue. Not an issue OSGi-related issue.
--BJ HargraveSenior Technical Staff Member, IBM // office: +1 386 848 1781OSGi Fellow and CTO of the OSGi Alliance // mobile: +1 386 848 3788hargr...@us.ibm.com
- Original message -From:
You need to put the native lib in the bundle and put a Bundle-NativeCode header in the bundle's manifest with the necessary information. See the OSGi Core spec for details.
--BJ HargraveSenior Technical Staff Member, IBM // office: +1 386 848 1781OSGi Fellow and CTO of the OSGi Alliance //
1 - 100 of 383 matches
Mail list logo