Hello.
I've already asked the question, but probably not clearly...
I don't understand why I can't resolve the dependency for :
org.apache.camel:camel-activemq:jar:2.25.4
I used this component for a long time on old servicemix environments,
and I'm trying to port my projects to Karaf using Camel
camel-activemq is not out of the box in Apache Camel in Camel v2.
It comes from Apache ActiveMQ 5.x instead.
However starting from ActiveMQ 5.17 then they dropped their camel-activemq
JAR and its no longer available.
Instead use the generic camel-jms instead. Or go back to ActiveMQ 5.16.x
In the
Hello.
I've been working before on ActiveMQ 5.16.5, but as this version leads to
too many problems on Karaf 4.4.1 (spring compatibility among other issues),
I've decided to switch to ActiveMQ 5.17.1.
Before, I think the component camel-activemq was provided by the feature
activemq-camel, but with
You can create your own activemq component that extends the jms component,
and setup the connection factory and all of that just like the old activemq
component did, and install that in karaf
On Fri, Aug 19, 2022 at 12:35 PM Ephemeris Lappis <
ephemeris.lap...@gmail.com> wrote:
> Hello.
>
> I've
That's correct: activemq-camel has been removed.
You can now use camel-jms (recommended) or camel-activeemq.
You can wrap your own component if needed, but I would rather update
to camel-jms (not so hard to do).
Regards
JB
On Fri, Aug 19, 2022 at 12:33 PM Ephemeris Lappis
wrote:
>
> Hello.
>
>
Hello.
I've never seen any documentation about "camel-activeemq" : what's the
feature that provides it ?
As I've said before, I've been trying to use camel-jms but surprisingly
my unique connection factory is not detected, and the component asks for
an explicit declaration. I thought that on
Hi,
here's the documentation about camel-activemq:
https://camel.apache.org/components/3.18.x/activemq-component.html
About the ConnectionFactory, you have to define it as reference in
your route. You can find an example here:
https://github.com/jbonofre/camel-amq-redelivery/blob/master/src/main
Hello.
Sorry for the question about "camel-activeemq" (double e) <>
"camel-activemq". I thought you were talking about another distinct Camel
component... camel-activemq is in fact the component i'd like to use...
I don't understand why using ActiveMQ 2.16.5 and a connection factory that
I create
Hi,
I think this is because of the history of Camel and ActiveMQ. Originally
Camel was aligned with Apache ServiceMix (https://servicemix.apache.org/)
ServiceMix contained:
- Runtime: Apache Karaf
- Several integration tools/frameworks:
- Camel
- ActiveMQ (Classic)
- CXF (Webservices)
Hello again.
As it seems I have no solution to get an implicit connection factory, I've
adapted my POC setting myself a reference. But it seems that it doesn't
work because the service that is created by the jms:create command doesn't
match some class definition.
In my POC's code I've added a dep
Hello.
As you remind us, the end of ServiceMix leads us to find alternative
solutions. In our context, our more than 100 projects are running today on
an old redHat Fuse 6.3, and we consider migrating them to a simpler
solution. Initially, ServiceMix should have been a solution. Now our
perspectiv
"But I didn't imagine that taking out of the shelves ActiveMQ, Karaf and
Camel versions could be so difficult"
Yes, I know that's why I created Assimbly (assimbly.org) which runs the
latest Camel, ActiveMQ together (from Spring Boot and hopefully Karaf 5 as
well). I am not that far though as Camel
Hi,
That's not a problem of package but of OSGi requirement.
You can do:
- do not include requirement in your my-test... bundle
- provide the capability in your feature (similar to
https://github.com/apache/karaf/blob/main/examples/karaf-jpa-example/karaf-jpa-example-features/src/main/feature/fea
Hello again !
Well, I'm not sure I understand what you mean about "requirements" in my
bundle. I have no requirement in my manifest. Here the full copy of the
manifest :
Manifest-Version: 1.0
Bnd-LastModified: 1661240801094
Build-Jdk-Spec: 1.8
Bundle-Blueprint: OSGI-INF/blueprint/routes.xml
Bundl
Hello.
Sorry to answer my own message...
I think I have perhaps an explanation. Reading again the Karaf's
features documentation, I noticed the part that explains how the
resolver detects bundle requirements before installing a feature.
Perhaps this is why it detects that my bundle needs a jms co
Hello again.
Sorry to answer my last email once more...
As I was not very happy after my last test with the
"serviceRequirements=disable", and as I remembered that something is
kept in memory about features, I've cleaned up my Karaf and play the
same test again, and it seems to work fine now. My
Hi,
you have a requirement in your bundle: it's the Import-Service
statement. The problem comes from there: it's nothing about the
runtime.
I would recommend adding configuration to maven-bundle-plugin to not
put this requirement in your bundle MANIFEST.
I already answered similar questions on t
Hello.
You've probably not seen my own answers on the post to update it with
my last tests :
- the bundle has no problem when installed out of the feature, and I
think the service manifest itself is not the issue
- In this manifest, I understand the requirement on the jms service,
but the existing
Hi,
It's normal that the bundle works outside of the feature: it's the
feature resolver who checks the requirements/capabilities of the
bundles/features.
And you didn't get my point: the fact that a ConnectionFactory service
is there or not at runtime doesn't matter. The most important is to
have
Hello.
For sure, I didn't get your point about capabilities. As in my case
the JMS and JDBC services are provided by features outside of the
scope of all my applicative bundles and features, how do you consider
I should provide a "capability" for them, and thus let the resolver
satisfied ? I've se
20 matches
Mail list logo
