Hi Stephen,
I would say, you have two approach:
- in the start method of your bundle, you can create a listener that check if
the ActiveMQ transport connector (the tcp port for instance) is bound and then
you move on.
- AFAIR, ActiveMQ OSGi exposes the BrokerService as an OSGi service. So, you
Hi Dominik,
sorry for the late feedback, I was on different flights.
Can you share your log file (in direct message) ?
In the mean time, I will try to reproduce.
Regards
JB
On 12/08/2017 08:05 AM, Dominik Marciniszyn wrote:
Thank you for advice jbonofre. I tried but the datasource is on the c
OK so the code would not refresh if aries-jpa was not a snapshot?
Quite unfortunately, there is a HUGE (for us) bug in aries-jpa is fixed in
2.7.0 version, which is not released...
I'm able to do a 'fake' release to our local maven repository. I didn't
thought there's some logic in feature refres
So your bundle is refreshed because it's wired to the glassfish
jersey-container-servlet-core bundle, which itself is wired to
javax.persistence bundle, refreshed because:
Should be wired to: org.apache.aries.jpa.container/2.7.0.SNAPSHOT
(through [javax.persistence/2.1.1.v201509150925] osgi.wirin
Bundles to install:
here are only my private bundles listed
Bundles to refresh:
com.eclipsesource.jaxrs.jaxrs-publisher/5.3.1 (Wired to
org.glassfish.jersey.containers.jersey-container-servlet-core/2.22.2 which
is being refreshed)
javax.persistence/2.1.1.v201509150925 (Should be wired to
Hello,
I'm having a small issue where the ActiveMQ Service has not initialized in
time for a bundle I have developed. With our own bundles, we can resolve
ordering with declarative services, using @Reference, but I'm not sure how
to achieve the same with ActiveMQ. Basically, I want to make sure th
You should have a line saying why javax.persistence/2.1.1.v201509150925 is
being refreshed.
Can you paste the whole output ?
Guillaume
2017-12-08 13:53 GMT+01:00 lechlukasz :
> I think I've found the offender.
>
> The message says:
>
> org.glassfish.jersey.containers.jersey-container-servlet-cor
I think I've found the offender.
The message says:
org.glassfish.jersey.containers.jersey-container-servlet-core/2.22.2 (Wired
to javax.persistence/2.1.1.v201509150925 which is being refreshed)
However, there's no indicator why it should be refreshed. The exact bundle
is already installed in th
2017-12-08 12:15 GMT+01:00 lechlukasz :
> Ok thank you, all my features are verified by maven plugin.
>
> So you say that no matter if I have features with dependency="true" or not,
> if the feature is already installed, it will not be touched?
> So the observed behavior, that after installing n
Ok thank you, all my features are verified by maven plugin.
So you say that no matter if I have features with dependency="true" or not,
if the feature is already installed, it will not be touched?
So the observed behavior, that after installing new feature the blueprint
context from bundles from
It's all about constraints.
If something does not work when installed, it means that the constraints
are not correctly expressed.
If you use the maven bundle plugin for example, it should generate service
requirements for the various namespace handlers used. Those will be used
at resolution time,
Does the same appply to features?
Because I've noticed an improvement, after marking the dependent features as
dependency="true":
service1-core
However, if I've done the same for all my features, including system ones
(jpa, transaction-api, transaction etc.) I've ended up with my bundles no
So first, bundles are only updated / refreshed / restarted if necessary.
If there's no change for a given bundle, it won't be touched at all.
The dependency="true" flag means that the artifact can be used by karaf to
solve some constraints, but it won't be installed if not needed.
This is mainly u
Hello,
I'm quite confused about feature dependencies. The documentation about
provisioning doesn't explain much how the dependency="true" is expected to
work. I've tried adding or removing it, but I experience unexpected behavior...
I have a core feature and other features that depend on it. T
14 matches
Mail list logo
