Re: [osgi-dev] Usage of prototype components

There must be at least one "getter" of the service for that to occur. I guess you need to debug who/what is triggering this instance. - Ray On Sun, Aug 2, 2020 at 5:01 PM Paul F Fraser via osgi-dev < osgi-dev@mail.osgi.org> wrote: > Hi, > > My aim is to only instantiate a prototype component

Re: [osgi-dev] Library development

FYI, One thing few people realize is that Service Loader Mediator does allow your providers to be consumed via the service registry. If you use the bnd SPI annotations I already mentioned this is a default behavior. - Ray On Thu, May 21, 2020 at 9:19 AM Raymond Auge wrote: > Another

Re: [osgi-dev] Library development

Another alternative designed specifically for this scenario is the OSGi Service Loader Mediator Specification [1]. Java's default _service_ mechanism is Service Loader SPI. The Service Loader Mediator Specification adds a veneer of pure metadata over this to allow it to function in OSGi. There

Re: [osgi-dev] Service binding issue and package wiring

You cannot have two bundles where: - each exports the same package (and does not import it) - AND each exports a service for a type in said package - AND those services are compatible Basics of OSGi Classloading: - each bundle is loaded in a separate classloader - classloaders load classes (and

Re: [osgi-dev] Intermittent failure to getService

On Wed, Mar 11, 2020 at 10:02 AM Raymond Auge wrote: > Prototype scope is super important. It's true we don't have a huge number > of uses (it may be less than 1% of all services), but where you need them > they are incredibly useful, particularly in modelling behaviours defined > outside the

Re: [osgi-dev] Intermittent failure to getService

Prototype scope is super important. It's true we don't have a huge number of uses (it may be less than 1% of all services), but where you need them they are incredibly useful, particularly in modelling behaviours defined outside the realm of OSGi. For instance, JAX-RS expects resources to be

Re: [osgi-dev] Service binding issue and package wiring

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> wrote: > Since both bundles B and C offer to export the api.a package, the > framework

Re: [osgi-dev] Maven (Tycho) cannot resolve OSGi Core bundle

On Fri, Jan 3, 2020 at 10:29 AM Martin Petzold wrote: > IMHO: Manifest-first is best. p2 is hell. maven-bundle-plugin and bnd > "hate" Eclipse. It was never easy. The worst ever was not to find together! > Sounds like you may not have tried bndtools.m2e integration in a long time or ever. OSGi,

Re: [osgi-dev] Maven (Tycho) cannot resolve OSGi Core bundle

I would recommend, since you are using maven, not really using tycho for much AND in order to future proof your OSGi application you should probably migrate to bnd-*-maven-plugin(s) [1] These are better integrated with maven, maven scopes and give you a full cycle of tools to go from building to

Re: [osgi-dev] Maven (Tycho) cannot resolve OSGi Core bundle

A bit of rational about why companion jars are unresolvable: The OSGi specs are to a very high degree independent from each other. There's no reason for you to be forced to use all R5 specs, or all R6 or whatever. Those are simply marketing versions. What you are really using are the individual

Re: [osgi-dev] Maven (Tycho) cannot resolve OSGi Core bundle

Yes and yes. OSGi started adding the unresolveable requirement at release 6 IIRC. So if you are using a prior releases of the companion jars (including cmpn, enterprise) they won't give you this failure, so you should upgrade. *Replacements:* Replace the compendium APIs with their respective

Re: [osgi-dev] Maven (Tycho) cannot resolve OSGi Core bundle

On Thu, Jan 2, 2020 at 12:17 PM Martin Petzold via osgi-dev < osgi-dev@mail.osgi.org> wrote: > Dear OSGi gurus, > I have a dependency on "org.osgi:osgi.core" (7.0.0) in my POM. The reason > is that I need access to the "org.osgi.framework" package. I am using Maven > (3.6) and Tycho (1.5.1) for

Re: [osgi-dev] serviceloader

You could also use bnd's `@ServiceProvider` and/or `@ServiceConsumer` annotations which handle all of this magic for you. The addition of the service capability was recently added so is not available until next release (5.0.0), but everything else is handled. Before 5.0.0 this is what I

Re: [osgi-dev] Questions about R7 Configurator

... not just DS, but OSGi CDI too with Bean Property Types [1]! :) [1] https://osgi.org/specification/osgi.enterprise/7.0.0/service.cdi.html#service.cdi-bean.property.types On Tue, Dec 17, 2019 at 7:03 AM David Leangen via osgi-dev < osgi-dev@mail.osgi.org> wrote: > > Hi David, > > Ah, ok.

Re: [osgi-dev] @ConsumerType vs @ProviderType

ethod was added to `DataContext` since that > API is marked `@ProviderType` the package version increase would only have > to be minor. Is that correct? > That is correct! - Ray > > On Wed, Oct 16, 2019 at 6:06 PM Raymond Auge via osgi-dev < > osgi-dev@mail.osgi.org> wrote

Re: [osgi-dev] @ConsumerType vs @ProviderType

Let me see if I can take a crack at it! Though I'm often told I also don't understand when I try to explain it. :D Suppose you have an API like so: interface DataHandler { void processData(DataContext context); } This API has 2 interfaces `DataHandler` and `DataContext` Now you happen to

Re: [osgi-dev] @ConsumerType vs @ProviderType

Let me see if I can take a crack at it! Though I'm often told I also don't understand when I try to explain it. :D Suppose you have an API like so: interface DataHandler { void processData(DataContext context); } This API has 2 interfaces `DataHandler` and `DataContext` Now you happen to

Re: [osgi-dev] Deactivating a component manually

TabViewModel and on and on. > > Alain > > > On Sat, Sep 21, 2019 at 10:34 AM Raymond Auge via osgi-dev < > osgi-dev@mail.osgi.org> wrote: > >> Hey Alain, >> >> Just trying to understand the use case better, so a couple questions: >> >> Since yo

Re: [osgi-dev] Deactivating a component manually

Hey Alain, Just trying to understand the use case better, so a couple questions: Since your component is prototype scope, and if no one has any instances of it why bother disabling it, isn't it effectively only a fairly inert service reference at that point? Are you saying that when released as

Re: [osgi-dev] Using Gradle or Maven on a new OSGi project

On Thu, Jul 25, 2019 at 11:24 AM Stephen Schaub via osgi-dev < osgi-dev@mail.osgi.org> wrote: > Over on the bndtools list, Raymond Auge indicated that live code > deployment isn't supported in Eclipse with a standard Gradle project > structure. > Yet! :) but it's not too far away I would think.

Re: [osgi-dev] Help with the OSGi Converter

I don't have a concrete answer since I'd have to also debug. However, I can make a suggestion to perhaps try: org.apache.felix org.apache.felix.converter 1.0.8 which is Apache Felix implementation of the osgi converter spec. What you'll find is that it's moving along a little faster with

Re: [osgi-dev] Migrating from OSGI to Microservices

On Thu, May 2, 2019 at 10:53 AM BJ Hargrave via osgi-dev < osgi-dev@mail.osgi.org> wrote: > 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. > >

Re: [osgi-dev] Multiple bind attempts to 8080

In the second case, could the runbundles contain duplicate felix jetty bundles (like of different versions)? - Ray On Sat, Mar 23, 2019 at 9:58 AM jhrayburn--- via osgi-dev < osgi-dev@mail.osgi.org> wrote: > I have multiple sets of bundles for different capabilities. > > > > AuthApp > >

Re: [osgi-dev] Combine requirements from different namespaces

Instead of trying to kick people out of the party, why even let them in to begin with? i.e. sounds like you have the well documented problem of _not well curated repository_ - Ray On Sun, Mar 3, 2019, 07:35 Michael Lipp via osgi-dev, < osgi-dev@mail.osgi.org> wrote: > Is it possible to write a

Re: [osgi-dev] SCR API

Another option is Aries Component DSL [1]. - Ray [1] https://github.com/apache/aries/tree/trunk/component-dsl On Thu, Feb 21, 2019 at 1:21 PM BJ Hargrave via osgi-dev < osgi-dev@mail.osgi.org> wrote: > There is not plan for Declarative Services to have an API for imperatively > creating

Re: [osgi-dev] ComponentServiceObjects vs ServiceObjects

Thomas, You can only use ComponentServiceReference where you have @Reference. In other words, if you create a raw service tracker, or if you get service directly (and I sincerely hope not), the you _must_ use ServiceObjects. In a few months when you ultimately switch over to CDI integration ;)

Re: [osgi-dev] Clarification on reference behavior regarding field injection

You're chart doesn't appear to list _which_ field (Reference) was associated with any given line (collection vs. scalar). It makes a difference. - Ray On Sat, Feb 16, 2019 at 9:15 AM Thomas Driessen via osgi-dev < osgi-dev@mail.osgi.org> wrote: > Hi, > > I'm trying to get an overview over the

Re: [osgi-dev] Vaadin flow works in bnd workspace, fails in enRoute project

On Sat, Feb 16, 2019 at 12:45 AM Paul F Fraser via osgi-dev < osgi-dev@mail.osgi.org> wrote: > On 16/01/2019 10:51 pm, Tim Ward wrote: > > Is there a bug repot filed for this bug? Otherwise we should do that. > > https://issues.apache.org/jira/browse/FELIX-6029 > > It would appear that

Re: [osgi-dev] Programmatically creating DS components

On Sun, Feb 10, 2019 at 11:20 AM Thomas Driessen < thomas.driessen...@gmail.com> wrote: > Hi Ray, > > I'm not defining any additional manifest header if that's what you mean. I > have no real control over the bundles I need to scan. > > What I do is registering a BundleTracker that scans a

Re: [osgi-dev] Programmatically creating DS components

Are you implementing this using the extender pattern? If so, I would not use DS. I would use something lower level. There are plenty of good alternatives for doing this, but I would suggest looking at Apache Aries Component DSL [1] (it's what is used to implement Aries JAXRS Whiteboard). - Ray

Re: [osgi-dev] enRoute workspace debugging

The bigger question is why I'm the world are there java files in target? target is the build directory. We are there source files in there? - Ray On Fri, Feb 1, 2019, 13:47 Paul F Fraser via osgi-dev < osgi-dev@mail.osgi.org wrote: > Thomas, > Thank goodness someone else has experienced this. I

Re: [osgi-dev] ContainerRequestFilter/ContainerResponseFilter life cycle

;> As described in the JAX-RS Whiteboard spec >>>>> <https://osgi.org/specification/osgi.cmpn/7.0.0/service.jaxrs.html#d0e133685> >>>>> JAX-RS >>>>> extension instances are required to be singletons (I’m talking about the >>>>> object

Re: [osgi-dev] ContainerRequestFilter/ContainerResponseFilter life cycle

I'm going to assume you are talking about: HttpService[1] or Http Whiteboard[2] w.r.t. the reference to Servlet AND JAX-RS Whiteboard[3] w.r.t. the reference to ContainerRequestFilter These 2(3) features are separate concerns and the ContainerRequestFilter of the JAX-RS whiteboard spec doesn't

Re: [osgi-dev] OSGi Http Client Missing Requirement

On Mon, Jan 21, 2019 at 9:47 PM Paul F Fraser via osgi-dev < osgi-dev@mail.osgi.org> wrote: > On 21/01/2019 7:57 pm, Tim Ward wrote: > > As a separate question - is there a reason that you are trying to use the > Apache HttpClient? OSGi enRoute makes use of the JAX-RS Whiteboard which >

Re: [osgi-dev] Split-package for 3rd party jars/bundle

We made an Uber bundle of the whole ES stack, then only exposed enough to make one of add-on web uis work. - Ray On Wed, Jan 2, 2019, 11:41 Alain Picard Raymond, > > I think this is a good idea but some of their comment was that they were > not even willing to get PR for it since they would

Re: [osgi-dev] Split-package for 3rd party jars/bundle

There appears to be a lot of us who've repackaged lucene/ES (my company has done so also). I wonder if we could perhaps exert so upstream influence and maybe some contributions to make it a better OSGi citizen. I happen to have a friend who recently works at Elasticsearch that has a lot of OSGi

Re: [osgi-dev] enRoute JPA example questions

Even better, a link to the html spec javadoc: https://osgi.org/specification/osgi.enterprise/7.0.0/service.component.html#org.osgi.service.component.runtime.ServiceComponentRuntime - Ray On Fri, Dec 7, 2018, 10:36 Clément Delgrange via osgi-dev < osgi-dev@mail.osgi.org wrote: > Thanks for the

Re: [osgi-dev] dependency chain split due to org.eclipse.osgi bundle

On Wed, Dec 5, 2018 at 11:03 PM Raymond Auge wrote: > It looks like you are exporting the package `javax.annotation` from the > system bundle (say via `org.osgi.framework.system.packages.extra`, i.e. > `-runsystempackages`), while you also have the bundle >

Re: [osgi-dev] dependency chain split due to org.eclipse.osgi bundle

It looks like you are exporting the package `javax.annotation` from the system bundle (say via `org.osgi.framework.system.packages.extra`, i.e. `-runsystempackages`), while you also have the bundle org.apache.servicemix.specs.annotation-api-1.3 deployed. Hope that helps, - Ray On Wed, Dec 5,

Re: [osgi-dev] what is way to use a Resolver and Repository together ?

The basic idea is that you want to represent the capabilities of the existing system as already being provided, used to support the requirements you're searching for, but ultimately excluded from the result, such that only missing capabilities are included in the result. You might want to look at

Re: [osgi-dev] Disposing component instances

Please note that up to a couple of weeks ago there was a bug in Felix SCR managing indirect component prototype instances. https://issues.apache.org/jira/browse/FELIX-5974 So you may want to make sure you have the latest. - Ray On Sun, Nov 25, 2018, 08:21 Alain Picard via osgi-dev <

Re: [osgi-dev] Usinge Cache in Karaf

On Thu, Nov 22, 2018, 15:30 Raymond Auge Scott, is that usable in-process, as in no remoting? > > - Ray > > On Thu, Nov 22, 2018, 14:55 Scott Lewis via osgi-dev < > osgi-dev@mail.osgi.org wrote: > >> On 11/22/2018 8:19 AM, Raymond Auge via osgi-dev wrote: >> >

Re: [osgi-dev] Usinge Cache in Karaf

Scott, is that usable in-process, as in no remoting? - Ray On Thu, Nov 22, 2018, 14:55 Scott Lewis via osgi-dev On 11/22/2018 8:19 AM, Raymond Auge via osgi-dev wrote: > > Mohamed, if I understand correctly, what you really need in order to cache > method calls are proxies around

Re: [osgi-dev] equinox env started notification

... or go look at the Apache Felix (new) systemready project. :) - Ray On Thu, Nov 22, 2018, 13:42 Cristiano via osgi-dev Hi, > > Well, I think there are many possible solutions for that. > > In my opinion, the complicated thing is how the OSGi framework would know > what is necessary to it

Re: [osgi-dev] Usinge Cache in Karaf

Mohamed, if I understand correctly, what you really need in order to cache method calls are proxies around arbitrary services. First I don't think there's a OOTB solution for your problem description specifically to do method caching. Also, OSGi doesn't natively provide a proxy mechanism. In

Re: [osgi-dev] How to specify a requirements on JSR-353 (Json) implementation

If you use this API dependency instead: org.apache.geronimo.specs geronimo-json_1.1_spec 1.1 it will do exactly what you want. (make sure you also have a recent Aries SpiFly in your runtime dependencies somewhere) - Ray On Tue, Nov 20, 2018 at 8:26 AM Clément Delgrange via osgi-dev <

Re: [osgi-dev] Service component resolution time

One potential solution is for the resolver immediately deliver some warnings with a bit of trace details when it realizes that the computation is exceeding normal levels of complexity. - Ray On Sat, Nov 3, 2018, 11:45 Raymond Auge It would be useful to make this scenario produce a louder

Re: [osgi-dev] Service component resolution time

It would be useful to make this scenario produce a louder perhaps more obvious error message. If you could maybe create an issue for improvement on Apache Felix JIRA, under Resolver project with as many details as you could provide maybe we can do something. These rare and complex scenarios

Re: [osgi-dev] Is there already a standard for aggregating repositories?

On Sun, Oct 21, 2018, 13:38 Raymond Auge, wrote: > Additionally, the OSGi repository format defines the "referral" [1] > element which points at another index file. This way you can combine repos > whoever you like. > ... and yes, bnd supports this. > > - Ray > > [1] >

Re: [osgi-dev] Is there already a standard for aggregating repositories?

Additionally, the OSGi repository format defines the "referral" [1] element which points at another index file. This way you can combine repos whoever you like. - Ray [1] https://osgi.org/specification/osgi.cmpn/7.0.0/service.repository.html#i3236527 On Sun, Oct 21, 2018, 12:57 Peter Kriens

Re: [osgi-dev] How can I destroy all OSGi blueprint components before the OSGi framework is stopped?

You probably want to actually wait for the framework to stop: FrameworkEvent frameworkEvent = Launcher.framework.waitForStop(timeout); if (frameworkEvent.getType() == FrameworkEvent.WAIT_TIMEDOUT) { _log.error("OSGi framework event {} triggered after a {}ms timeout", frameworkEvent,

Re: [osgi-dev] Servlet Context in OSGi

On top of this design we've been able to model full blown WAB support, each WAR get's it's own "servlet context" against which every other resource/servlet/filter in the WAR is targeted. Another common case is re-use of exactly the same pre-built servlet & filter based features with different

Re: [osgi-dev] many bundles with the same propeties file : infinite loop

On Mon, Oct 8, 2018 at 9:46 AM Mohamed AFIF via osgi-dev < osgi-dev@mail.osgi.org> wrote: > > Hello, > > I had in my project a random behaviour of some bundles who Swing between > Active and Starting state, but finally I found out the root cause, > indeed those bundles share the same

Re: [osgi-dev] replace session-config in web.xml with whiteboard

Please feel free to submit an issue about this to the OSGi bug tracker [1]. - Ray [1] https://osgi.org/bugzilla/ On Thu, Oct 4, 2018 at 11:40 AM Nhut Thai Le via osgi-dev < osgi-dev@mail.osgi.org> wrote: > Thank you for the link; unfortunately i'm using paxweb http service so > that config

Re: [osgi-dev] Best practices for providing configs in cloud setups?

I thought this is exactly what the new Configurator Specification [1] is all about. - Ray [1] https://osgi.org/specification/osgi.cmpn/7.0.0/service.configurator.html On Thu, Sep 13, 2018 at 8:30 AM, Christian Schneider < ch...@die-schneider.net> wrote: > I am looking into good ways to

Re: [osgi-dev] How can I reuse servlet filter across bundles

Thai, what you described sounds like a bug in the http whiteboard implementation. Which do you use and could you file a bug against it? - Ray On Wed, Sep 12, 2018, 17:38 Nhut Thai Le, wrote: > Thank you Raymond, > > I called the HttpServiceRuntim.calculateRequestInfoDTO("/token") inside > my

Re: [osgi-dev] How can I reuse servlet filter across bundles

Hello Thai, I don't see anything wrong. It looks like they all "target" the default "ServletContextHelper" (i.e. the same context) and so the filter should apply to each. You should be able to check by getting the HttpServiceRuntime [1] service and calling the method

Re: [osgi-dev] Logger at startup

On Tue, Aug 28, 2018 at 3:13 AM, Peter Kriens wrote: > On 27 Aug 2018, at 22:40, Raymond Auge via osgi-dev < > osgi-dev@mail.osgi.org> wrote: > On Mon, Aug 27, 2018 at 4:19 PM, David Leangen via osgi-dev < > osgi-dev@mail.osgi.org> wrote: >> >> Hi P

Re: [osgi-dev] Logger at startup

On Mon, Aug 27, 2018 at 4:19 PM, David Leangen via osgi-dev < osgi-dev@mail.osgi.org> wrote: > > Hi Peter and Ray, > > Thank you very much for the suggestions! > > I’ll take a look at the code. It is my hope that I don’t need to pull in > any additional dependencies. Maybe I’ll get some hints in

Re: [osgi-dev] Logger at startup

There's setup details in the integration tests [1] HTH - Ray [1] https://github.com/apache/felix/tree/trunk/logback/itests On Mon, Aug 27, 2018 at 9:15 AM, Raymond Auge wrote: > My personal favourite is the Apache Felix Logback [1] integration which > supports immediate logging when follow

Re: [osgi-dev] Logger at startup

My personal favourite is the Apache Felix Logback [1] integration which supports immediate logging when follow the correct steps. I feel it's the best logging solution available. There are a couple of prerequisites as outlined in the documentation. But it's very simple to achieve your goal (NO

Re: [osgi-dev] Enabling debug of SCR with Equinox

Here's a few additional comments to Critiano's suggestion: On Mon, Aug 6, 2018 at 8:38 PM, Cristiano via osgi-dev < osgi-dev@mail.osgi.org> wrote: > hi, > > if you are using the latest equinox, one good alternative is to use the > recently released org.apache.felix.logback. > You can even use

Re: [osgi-dev] Liferay Portlet created with BndTools and Gradle not outputting the right package versioning when building the JAR file

Forgive me for misspelling your name Ramazan. Sincerely, - Ray On Tue, Aug 7, 2018 at 9:01 AM, Raymond Auge wrote: > Hello Raman, > > Since many of the aspects could be related to Liferay specifics, you may > have better luck asking on the Liferay forums here [1] or even on the > Liferay

Re: [osgi-dev] How would you implement SLF4J binding ?

You probably want to use Java SE ServiceLoader, and then on the provider and consumer bundles apply Service Loader Mediator [1] metadata. This means your code is Java SE compliant as a library, but when deployed in OSGi will get treated and backed by service registry and be wired in a OSGi safe

Re: [osgi-dev] OSGi Logging

Apache Felix just recently released a new feature (bundle) which sets up OSGi Log Service and new Loggers using Logback backend. Logback can then be used to manage all the log levels and appenders which can go to console if you wish. You can get a feel for what this does and how it works here

Re: [osgi-dev] Multi-Tenancy with OSGI

link to coordinator spec for reference https://osgi.org/specification/osgi.cmpn/7.0.0/service.coordinator.html - Ray On Mon, Jul 2, 2018 at 3:33 PM, Raymond Auge wrote: > Could this be handled by the coordinator? This API provides an out of band > scope which allows "coordination" of

Re: [osgi-dev] Multi-Tenancy with OSGI

Could this be handled by the coordinator? This API provides an out of band scope which allows "coordination" of operations, which is largely what multi-tenancy is about, although coordination is most commonly associated with something like transactions, but the axis is pretty much the same. - Ray

[osgi-dev] Draft of OSGi R7 CDI Specification

(Note this message is cross-posted to several select lists.) Hello everyone, I wanted to announce the very first public draft of the new OSGi Enterprise R7 CDI Integration Specification (Chapter 152) [1]. This specification, obviously, intends to bring CDI to OSGi so that one complements the

Re: [osgi-dev] Adding a Vaadin dependency causes trouble

Regarding Vaadin, I believe that any jar which has java classes in the root (i.e. no package) are malformed in the eyes of OSGi and bnd will complain about them until you find a way to silence bnd (which may only be possible using the `-fixupmessages` directive). Sincerely, - Ray On Mon, Jun 18,

Re: [osgi-dev] Migrating existing projects to OSGi, ServiceLoader

One other thing you could check is the starting order of your bundles. Most things that use weaving hooks (SpiFly does) is subject to start ordering. so make sure SpiFly is started before the bundles it weaves. Sincerely, - Ray On Thu, Jun 14, 2018 at 5:57 AM, Raffaele Gambelli <

Re: [osgi-dev] Migrating existing projects to OSGi, ServiceLoader

Hello Raffaele, Have you read through the this page starting with http://aries.apache.org/modules/spi-fly.html#making-it-work Also, do you know exactly which ServiceLoader method is used in the Service Interface bundle? (it has to be the single argument ServiceLoader.load(Class) method to work

Re: [osgi-dev] Where is repo01

It's just the synthetic name given to the repo created from that index file. We could probably clean that up to make the name more insightful. Maybe create an issue so we don't forget? - Ray On Thu, Jun 7, 2018, 21:27 Paul F Fraser via osgi-dev, < osgi-dev@mail.osgi.org> wrote: > enRoute app

Re: [osgi-dev] Script for auto-generations standalone enRoute application executable

1) if you are in a bndtools workspace: say you have a project with a bndrun file like so: workspace-root/projectA/my.bndrun then execute the gradle command: cd workspace-root ./gradlew :projectA:export.my 2) if you are in a maven project using the bnd-export-maven-plugin [1]: then execute

Re: [osgi-dev] Apache cxf: add authorization header in Client

o append headers (using jaxrs providers). For more detailed answers - you may need to look cxf mailing list. Hope that this helps you to move forward. Cheers, Lukasz On 1 Mar 2018, at 20:45, Raymond Auge via osgi-dev <osgi-dev@mail.osgi.org> wrote: In an effort to not let your question g

Re: [osgi-dev] Apache cxf: add authorization header in Client

In an effort to not let your question go unanswered I'm going to just say that this list is unlikely to be the place to find your answer. This sounds like a CXF specific question. Have you asked this over at the CXF user mailing list? Sincerely, - Ray On Thu, Mar 1, 2018 at 1:43 PM, Michael

Re: [osgi-dev] Proliferation of DS Components and References

If you have thousands of DS components in one bundle you are probably doing something wrong. Clearly your bundle is not a cohesive unit of modularity. The largest DS based bundles I've seen tend to max out at around 50 components (even that is extreme). Our largest bundle, a bundle which

Re: [osgi-dev] OSGI bundles install on IBM Liberty

solving.md=DwMFaQ=ewHkv9vLloTwhsKn5d4bTdoqsmBfyfooQX5O7EQLv5TtBZ1CwcvjU063xndfqI8U=wKHHp1xupEN1UoR2CPDlg9US2Vs3om5ld5YqSsWMQX8=HH8Gw-cn_T-kd6gx_j2BbQ-yDw3Q20TuuUT5AHmRGgs=5dgDiilIAAv4T5Pi2QAhoAIKfDx6C4voPPFXS-SftOE=> > > > > Awesome! > > > > Thanks Peter! > > - Ray > > >

Re: [osgi-dev] Component Life Cycle: When are DS components/services registered

On Sun, Dec 10, 2017 at 11:45 AM, Konrad Windszus wrote: > Hi Ray, > thanks for confirming. So the relation between bundle life cycle and > component lifecycle is clear now. > The only remaining question is now: > > Is it valid to assume that once a DS component is registered,

Re: [osgi-dev] Component Life Cycle: When are DS components/services registered

Compendium Section 112.5.1 states: > A component must first be enabled before it can be used. A component cannot be enabled unless the > component's bundle is started. See Starting Bundles in OSGi Core Release 6. All components in a bun- > dle become disabled when the bundle is stopped. Core

Re: [osgi-dev] OSGI bundles install on IBM Liberty

solving.md > <https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_osgi_osgi.enroute.site_blob_gh-2Dpages_-5Fappnotes_resolving.md=DwMFaQ=ewHkv9vLloTwhsKn5d4bTdoqsmBfyfooQX5O7EQLv5TtBZ1CwcvjU063xndfqI8U=wKHHp1xupEN1UoR2CPDlg9US2Vs3om5ld5YqSsWMQX8=HH8Gw-cn_T-kd6gx_j2BbQ-yDw3Q20TuuUT5AHmRGgs=5dgDiilIAAv4T5Pi2QAhoAIKfDx6C4voPPFXS-SftOE=&g

Re: [osgi-dev] OSGI bundles install on IBM Liberty

; wrote: > >> I’ve added these points to the Resolve App Note. https://github.com/osgi/ >> osgi.enroute.site/blob/gh-pages/_appnotes/resolving.md >> > > Awesome! > > Thanks Peter! > - Ray > > >> Kind regards, >> >> Peter Kriens >> &

Re: [osgi-dev] OSGI bundles install on IBM Liberty

On Tue, Dec 5, 2017 at 9:42 AM, Raymond Auge wrote: > Hey Kevin, > > Here's what I could find: "Deploying OSGi applications to Liberty" [1] > > Now, this may be a little complicated by the fact that the enroute model > tends to guide you to resolve a whole runtime.

Re: [osgi-dev] making an existing interface method default causes MINOR baseline change

en / Best regards >> >> >> *Dirk Fauth* >> Automotive Service Solutions, ESI application (AA-AS/EIS2-EU) >> Robert Bosch GmbH | Postfach 11 29 | 73201 Plochingen | GERMANY | >> www.bosch.com >> Tel. +49 7153 666-1155 <+49%207153%206661155> | dirk.fa...@de.b

Re: [osgi-dev] making an existing interface method default causes MINOR baseline change

t; Sitz: Stuttgart, Registergericht: Amtsgericht Stuttgart, HRB 14000; > Aufsichtsratsvorsitzender: Franz Fehrenbach; Geschäftsführung: Dr. Volkmar > Denner, > Prof. Dr. Stefan Asenkerschbaumer, Dr. Rolf Bulander, Dr. Stefan Hartung, > Dr. Markus Heyn, Dr. Dirk Hoheisel, > Chr

[osgi-dev] making an existing interface method default causes MINOR baseline change

Hey All, I think the answer is "Yes it's a MINOR change", but I wanted to clarify. Assume I have the following interface in an exported package: public interface Foo { public void doFoo(); } And in the same package I have abstract class Bar which implements Foo: public abstract class Bar

Re: [osgi-dev] Declarative services and optional imports

Hey Robert, We had the same use case and solved it the following way: Given your component which has the optional import package (doesn't matter how it's used): import com.liferay.demo.foo.Foo; // The optional package @Component( enabled = false // disable by default so DS ignores it)public

Re: [osgi-dev] Apache Felix Web Console Components view

Hi Jesse, This question is better posted over on the Apache Felix user mailing list. That's the appropriate forum for your question and where you'll find the Felix experts who can answer your question. Sincerely, - Ray On Nov 16, 2017 15:55, "Jesse Rao via osgi-dev"