Hi, thanks for the tip.
I just think that Karaf provides DOSGi implementation [not in my old
version]. I guess this implementation has the right implementation of
serialization.
Regards
Hervé
On Tue, Apr 24, 2012 at 10:45 PM, Christian Schneider
ch...@die-schneider.net wrote:
As you can not
Hallo,
i have a problem to install the http feature at 3.0.0-SNAPSHOT. There is
the import org.eclipse.jetty.util.ssl missing.
In the log of the #karaf IRC-Channel i read that pax-web uses a newer
version and it could be enough to use a newer jetty version. So i changed
it to version
Hi all,
I have an application that uses Apache ActiveMQ in Karaf. I have a
broker project and multiple other projects that should depend on the
broker service to be started. How do I specify in the maven pom
(maven-bundle-plugin) that the child projects should wait until the
broker is
Hi Jason,
Using a feature, you can define the start-level of the bundles in the
feature.
Regards
JB
On 04/25/2012 05:12 PM, Jason wrote:
Hi all,
I have an application that uses Apache ActiveMQ in Karaf. I have a
broker project and multiple other projects that should depend on the
broker
Never the less you shouldn't rely on the startlevels,
I suggest that your application waits on services provided by the
ActiveMQ broker.
This is far more safe and more OSGi like ;)
regards, Achim
2012/4/25 Jean-Baptiste Onofré j...@nanthrax.net:
Hi Jason,
Using a feature, you can define the
Agree Achim, however, I'm not sure that ActiveMQ register a service per
queue or topic for instance (only for the broker).
Regards
JB
On 04/25/2012 05:18 PM, Achim Nierbeck wrote:
Never the less you shouldn't rely on the startlevels,
I suggest that your application waits on services provided
No, but depending on the configuration it may expose a JMSCOnnectionFactory
which can be obtained from the OSGi registry.
On Wed, Apr 25, 2012 at 17:30, Jean-Baptiste Onofré j...@nanthrax.net wrote:
Agree Achim, however, I'm not sure that ActiveMQ register a service per
queue or topic for
Agree, but the connection factory can be exposed independently (for
instance, the connection factory is deployed in a blueprint descriptor
using Aries, some not in the broker XML) from the broker, and the same
connection factory can be used for different topic/queue.
So even it's a perfect
Hi all,
Thanks for the quick feedback.
FWIW, the broker is registered as a service (javax.jms.ConnectionFactory).
My child projects get the ConnectionFactory from the BundleContext
within the BundleActivator.start(BundleContext) method of my Activator
and attach a MessageListener to a queue.
You have to have an Import-Service statement in the Manifest for the
dependency to be recognized by the OSGi framework.
I reference my services using blueprint and use the maven bundle plugin.
So a suitable entry gets generated automatically. If you
use an Activator you will have to manually
10 matches
Mail list logo
