Re: JMS Exception

Hi Nivi, is it possible to get a XML input sample ? Regards JB On Friday 20 February 2009 - 12:42, Nivetha Shri wrote: Hi All Am getting the following exception when i send an xml message to a output queue using apache camel and servicemix. My xml is a valid one Here is the stack

Re: Camel 3.0.1 camel-groovy feature install fails

FYI, It’s already changed on Karaf 4.2.9-SNAPSHOT and it will be included in 4.2.9 release. The change has been communicated on the Karaf mailing list. Regards JB > Le 25 févr. 2020 à 22:21, Gerald Kallas a écrit : > > Found the reason. > > org.ops4j.pax.url.mvn.cfg > > This one > >

Re: Install of camel-jackson on Karaf 4.2.7 w/ Camel 3.1.0 causes an error (same worked with Karaf 4.2.7 w/ Camel 3.0.1)

Hi, That’s normal due to JDK 9+. Previously JAXB was provided by the JDK, but not anymore. So, you have to add the JAXB bundle before installed camel-jackson. I’m working on Camel features to have condition depending of the JDK version. Regards JB > Le 28 févr. 2020 à 16:40, Gerald Kallas a

Re: Install of camel-jackson on Karaf 4.2.7 w/ Camel 3.1.0 causes an error (same worked with Karaf 4.2.7 w/ Camel 3.0.1)

jdk version "1.8.0_222" >>> OpenJDK Runtime Environment (build 1.8.0_222-b10) >>> OpenJDK 64-Bit Server VM (build 25.222-b10, mixed mode) >>> >>> Tried with Karaf 4.2.8, same error. >>> >>>> Jean-Baptiste Onofre hat am 28. Fe

Re: Newbie questions around AMQ and Camel Redelivery

Hi, You can maybe take a look on http://blog.nanthrax.net/?p=820 Basically, Camel and ActiveMQ redelivery are two different things. When using JMS, most of the time, I prefer to use ActiveMQ redelivery (via connection factory or configured in the destination

Re: Newbie questions around AMQ and Camel Redelivery

ted session? > Any reason why you want explicit control so that you need to call > Message.acknowledge()? > Cheers > n > > On Sat, 8 Feb 2020 at 05:43, Jean-Baptiste Onofre wrote: >> >> Hi, >> >> You can maybe take a look on http://blog.nanthrax.net/?p=820

Re: Camel 3.2.0 install

+1 to update the doc. By the way, I’m volunteer to cut camel-karat 3.2.1 with this fix (it could be helpful for our users IMHO). Thoughts ? We just had the same question on the Karaf user mailing list. Regards JB > Le 10 avr. 2020 à 21:08, Andrea Cosentino a écrit : > > It's our fault in

Re: Camel 3.2.0 install

n. There some work in progress. > > Il sab 11 apr 2020, 07:19 Jean-Baptiste Onofre ha scritto: > >> +1 to update the doc. >> >> By the way, I’m volunteer to cut camel-karat 3.2.1 with this fix (it could >> be helpful for our users IMHO). Thoughts ? >> >&g

Re: Salesforce not working with camel 3.2

Hi, Yes, I also identified the same issue: it works with Camel 3.0.1 and 3.1.0 but not in 3.2.0. I created https://issues.apache.org/jira/browse/CAMEL-14927 to fix it as I’m also impacted. Regards JB > Le 17 avr. 2020 à 12:26, Ajmera,

Re: Salesforce not working with camel 3.2

> Thanks and Regards, > Hemang Ajmera > > -Original Message- > From: Jean-Baptiste Onofre > Sent: 17 April 2020 17:07 > To: users@camel.apache.org > Subject: Re: Salesforce not working with camel 3.2 > > Hi, > > Yes, I also identified the same issue: it wor

Re: Camel version 3.0.2

+1 to update your project to 3.1.x. Regards JB > Le 13 mars 2020 à 15:21, Andrea Cosentino a écrit : > > Yes, exactly. The idea is upgrading to 3.1.x > > Il giorno ven 13 mar 2020 alle ore 15:18 Alex Dettinger < > aldettin...@gmail.com> ha scritto: > >> Hi remco, >> >> If I recall

Re: Camel 3.0.1 Jetty HTTP Basic Authentication - configuration in a route following the doc doesn't work

Hi I guess the documentation is not aligned with jetty version actually used. You are using Karaf 4.2.8 ? Camel jetty feature uses the jetty version provided by pax-web/karaf, so the documentation is not maybe correct for 9.4.22/27. Regards JB > Le 4 avr. 2020 à 10:08, Gerald Kallas a

Re: Broken feature dependencies in 3.2.0

Hi, It moved to camel-karaf repo and the feature should be updated. Can you please create a Jira ? I will fix that. Sorry for the inconvenience. Regards JB > Le 6 avr. 2020 à 14:42, Константин Чернов a écrit : > > Hi! > > > > Tried to update to 3.2.0 on karaf-4.2.8, got following error:

Re: Broken feature dependencies in 3.2.0

Ah yes, I just saw that. It’s already fixed but not released yet. Regards JB > Le 6 avr. 2020 à 14:50, Andrea Cosentino a écrit : > > No, I fixed that days ago. > > Il giorno lun 6 apr 2020 alle ore 14:49 Константин Чернов < > k.j.cher...@gmail.com> ha scritto: > >> Ah, okay. >> >> I

Re: Broken feature dependencies in 3.2.0

Don’t we have to update the provided feature in camel-karat ? It would be easier for users. Regards JB > Le 6 avr. 2020 à 14:46, Andrea Cosentino a écrit : > > No, it's a known bug. > > We released it > > You just need to update the feature > >

Re: Basic authentication of WAB using Jaas in Karaf

Hi, Sorry I was busy with Karaf 4.2.9 preparation and ActiveMQ releases. About several port, yes, it’s possible: http://blog.nanthrax.net/?p=352 Then you have to assign servlet to port using VirtualHosts (no other way for now). I already created couple of

Re: Connecting to IBM MQ Cloud using camel JMS component

Hi, What you are describing is direct MQ channel, no MQ JMS. It’s possible to use JMS with IBM MQ but using JMS channel. So, you create the connection factory like this: > class="com.ibm.mq.jms.MQQueueConnectionFactory"> > > > > > > >

Re: add/remove JAAS users and roles within a Camel route?

Hi, You mean on a JAAS backend ? JAAS doesn’t provide anything about that. That’s why in Karaf we have the "backend" service attached to some login modules. In your Camel route, you can interact with these services (as the jaas:* commands do in Karaf). Regards JB > Le 20 mai 2020 à 19:50,

Re: [ANNOUNCEMENT] Apache Camel 3.5.0 (LTS) with Spring Boot and Karaf Sub-Projects Released

Hi Raymond, 3. No plan for ServiceMix as ServiceMix is going to move to attic (discussion in progress). Of course, you can use Camel in Karaf (and eventually create your own custom distribution similar to ServiceMix). Regards JB > Le 8 sept. 2020 à 14:36, ski n a écrit : > > I do it through

Re: Rép. : Re: claimCheck availability within ServiceMix 7.0.1 (Apache Camel 2.16.5)

td5724329.html > > Hope it's help you > > Regards. > >>>> > De : Jean-Baptiste Onofre > À : > Date :2020-09-01 09:15 > Objet : Re: claimCheck availability within ServiceMix 7.0.1 (Apache > Camel 2.16.5) > > Hi > > claimCheck has

Re: claimCheck availability within ServiceMix 7.0.1 (Apache Camel 2.16.5)

Hi claimCheck has been introduced on Camel 2.21, so it’s not available on ServiceMix. Any chance to update to Karaf with Camel 2.x+ ? In the discussion we had on SMX, I proposed to cut a SMX release with updated versions before moving the project to the attic. Regards JB > Le 1 sept. 2020 à

Re: BeanInject in OSGI-container

Hi, I plan to improve the BeanRepository in camel-osgi. If your camel-context is in blueprint (), then it should take only the ref you defined in the blueprint container. When you say "inject", you mean something like this: ? Regards JB > Le 14 oct. 2020 à 16:11, Jörg Jansen a > écrit

Re: casisp-runtime - an Apache Camel / Karaf based integration container with a simple model driven deployment

Hi Gerald, Thanks for sharing ! Great to see a new solution powered by Karaf and Camel. I will take a deeper look. Regards JB > Le 9 oct. 2020 à 16:37, Gerald Kallas a écrit : > > Dear all, > > I've just published the first release of an Apache Camel / Karaf based > integration container

Re: Camel Salesforce Component & Plugin Issues

Hi Jean-Marc, Did you create a Jira about that already ? Do you use the maven plugin to generate the DTOs ? Regards JB > Le 17 août 2020 à 19:38, Jean-Marc Reynaud a > écrit : > > Dear Camel Team, > > > I'm facing a bit of a show-stopper with the Camel Salesforce Component. > > > The

Re: MethodNotFoundException upgrading to Camel 3.4.2 (Blueprint and Karaf)

Hi Alex, Not yet, I will get back on this one asap. Did you create a Jira about that ? I will keep you posted. Regards JB > Le 19 août 2020 à 15:21, Alex Soto a écrit : > > Any update on this, JB? > > Best regards, > Alex soto > > > > >> On Aug 15, 20

Re: MethodNotFoundException upgrading to Camel 3.4.2 (Blueprint and Karaf)

Hi, It seems to be related to a change on the camel-bean processor. Let me reproduce it and make a bisect to identify the change. Thanks ! Regards JB > Le 14 août 2020 à 22:32, Alex Soto a écrit : > > Hello, > > I have a Camel application using Blueprint XML running on Karaf 4.2.9. Some

Re: Camel 3.4.4 feature:install camel-json-validator causes an error

Hi, What JDK version are you using ? I bet you are using JDK 11 (this bnd error can occurs with JDK 11 or "old" maven-bundle-plugin version). The problem is probably in the camel-json-validator bundle. Can you please create a Jira and assign to me, I gonna fix that. Regards JB > Le 28

Re: Camel 3.3.0 and activemq

Hi, For ActiveMQ, you need to repo-add spring-legacy first. I just try on fresh Karaf and it works fine (with ActiveMQ 5.15.12). Zookeeper doesn’t seem related, I guess it’s required by openhab right ? Regards JB > Le 24 mai 2020 à 18:33, Carl van Denzen a écrit : > > I try to install camel

Re: Camel & NiFi

Hi, You can use ActiveMQ with persistent message between routes, it creates kind of resilience. It’s what I’m doing with most of my users/projects. It allows to resume and persist. Regards JB > Le 26 mai 2020 à 20:54, FabryProg a écrit : > > Camel and NiFi..  > > I used both in

Re: Rest registry has no services

Hi, AFAIR, getRestRegistry() will work only for REST DSL. If you use the Blueprint DSL, you should check the consumer of your routes (cafes, rest, whatever). Regards JB > Le 21 juil. 2020 à 16:14, Alex Soto a écrit : > > Hello, > > I have a few Rest Services defined with Camel Blueprint DSL

Re: camel-undertow in Camel > 3.2

Hi, Sorry I’m late on the message. I think it makes sense to wrap (as private) the 3rd party lib in the component assembly bundle. That’s what I’ve started to do. The problem is more than we (at Camel Karaf) should be a better job about the component. I’m working on lot of refactoring and

Re: Camel to not lookup OSGi services when looking up a bean

; registry when resolving bean names. But seems hardcoded? > > - Martin > > On 29.06.2020 09:34, Jean-Baptiste Onofre wrote: >> Hi Martin, >> >> What about implementing a caching service as proxy in front of your bean ? >> It’s pretty easy with Karaf (and you hav

Re: org.apache.karaf.specs.locator not found

Hi Alex, I don’t see this error on Jenkins, so I guess this error is in your itest. Can you share a simple project to reproduce ? By the way, I added karaf user mailing list as it’s Karaf related. Thanks, Regards JB > Le 13 juil. 2020 à 18:11, Alex Soto a écrit : > > With Karaf 4.2.9 and

Re: Karaf 4.2.9 w/ Camel 3.4.0 - ActiveMQ isn't starting

Hi, Did you add the spring-legacy feature repo ? ActiveMQ doesn’t support Spring 5.x, Spring 4.x only for now, that’s why you need to do: feature:repo-add spring-legacy Regards JB > Le 24 juin 2020 à 11:31, Gerald Kallas a écrit : > > Dear all, > > I've setup an (finally offline) instance

Re: Camel to not lookup OSGi services when looking up a bean

Caching is an option indeed. Be careful about OSGi service dynamism (to avoid side effect when the service is not there actually). Regards JB > Le 27 juin 2020 à 07:59, Claus Ibsen a écrit : > > You can cache the bean so the lookup is only done once. > > to("bean:foo?cache=true") > > In

Re: Basic authentication of WAB using Jaas in Karaf - the trick doesn't work any longer w/ Karaf 4.2.9 and Camel 3.4.0

Hi, Yes Karaf 4.2.9 upgraded to Pax Web 7.2.15 and Jetty 9.4.28.v20200408. Can you please send a private message about issues you have with Karaf 4.2.9 and Camel 3.4.0 (as I’m working on camel karaf for 3.5.0) ? Thanks, Regards JB > Le 28 juin 2020 à 22:02, Gerald Kallas a écrit : > > I

Re: Basic authentication of WAB using Jaas in Karaf - the trick doesn't work any longer w/ Karaf 4.2.9 and Camel 3.4.0

I thought Gerald already explained it on the mailing list. My intention is more to create the Jira with the details. Regards JB > Le 29 juin 2020 à 07:33, Andrea Cosentino a écrit : > > I think it's good to have the details shared in public. > > Il lun 29 giu 2020, 07:30 Jean-

Re: camel-kafka connection issue

Hi, Don’t you have another trace in the log, like missing Avro packages (ClassNotFoundException) in the Kafka bundle client ? I saw an issue with pulsar bundle missing Avro import (it used avro.* import whereas "new" Avro release uses org.apache.avro.*). Maybe Avro optional import is required

Re: Camel to not lookup OSGi services when looking up a bean

Hi Martin, What about implementing a caching service as proxy in front of your bean ? It’s pretty easy with Karaf (and you have a caching service on demand). So, the Camel Route will always request the bean, but the bean logic can be cached. Thoughts ? Regards JB > Le 29 juin 2020 à 09:29,

Re: Basic authentication of WAB using Jaas in Karaf - the trick doesn't work any longer w/ Karaf 4.2.9 and Camel 3.4.0

Thanks, I will take a look. Regards JB > Le 29 juin 2020 à 08:31, Gerald Kallas a écrit : > > I'm going to create the tickets for the issues. We may extend these so far > with additional information. > > Best > - Gerald > >> Jean-Baptiste Onofre hat a

Re: camel-kafka connection issue

T_LISTENER=yes >depends_on: > - zookeeper > > volumes: > zookeeper_data: >driver: local > kafka_data: >driver: local > > networks: > default: >external: > name: casisp > > >> Jean-Baptiste Onofre hat am 29.06.2020 08:14 g

Re: Camel website: documentation or projects

I agree with Andrea. Single page and links to docs make sense. Regards JB > Le 18 juin 2020 à 08:51, Andrea Cosentino a écrit : > > I'd say this should be under Documentation and I'd expect to find > description of projects and links to docs, I guess. > > One page it's for sure more clear

Re: camel-mail does not fetch attachments in Karaf.

pl.java:2053) > ~[?:?] > at java.lang.ClassLoader.loadClass(ClassLoader.java:352) ~[?:?] > > Just to test out, I also tried including javax.activation in the > dependencies > > >javax.activation >activation >1.1 > > > and embedding it in the bundle > > > > >org.apac

Re: camel-mail does not fetch attachments in Karaf.

gt; >javax.activation >activation >1.1 > > > and embedding it in the bundle > > > > >org.apache.felix >maven-bundle-plugin >true >

Re: camel-mail does not fetch attachments in Karaf.

actly should I change the context > loader in my code. > > I tried but I do not know where. > > Could you please help me out? > > Thank you. > > Regards, > Cooshal. > > On Mon, Jun 8, 2020 at 9:34 AM Jean-Baptiste Onofre wrote: > >> You can find some de

Re: camel-mail does not fetch attachments in Karaf.

Hi, How are you looking for the attachment ? In the class loader resource or using path ? I guess your attachement files are not found (either because it’s not private package of your bundle, or not imported correctly). Regards JB > Le 4 juin 2020 à 15:03, Kushal Gautam a écrit : > > Camel

Re: camel-mail does not fetch attachments in Karaf.

/components/imap-consumer >> >> I am using Open JDK 8 for this project. >> >> Kindly, please let me know if I should provide anything more. >> >> Thank you again. >> >> Regards, >> Cooshal. >> >> On Mon, Jun 8, 2020 at 2:11 PM Jean

Re: OSGI service Call using Camel route

Hi, How do you package your Camel Java DSL ? Is it in a blueprint bundle with ? Do you have the reference to the service ( with blueprint) in your camel bundle ? Regards JB > Le 17 juil. 2020 à 20:51, vignesh k a écrit : > > I get method not found exception when I try to connect/call OSGI

Re: OSGI service Call using Camel route

Hi, Did you try to use # for bean ref ? I’m not sure it will work mixing blueprint and Java DSL, I’m pretty sure it works fully in blueprint. Regards JB > Le 19 juil. 2020 à 21:30, vignesh k a écrit : > > > // Blueprint referencing the OSGI service > > >

Re: OSGI service Call using Camel route

Yes, it’s what I thought: the Java DSL doesn’t use the same bean container. As you are mixing blueprint and Java DSL, the bean from blueprint are not visible in Java DSL. So, either you only use blueprint, or load the service ref in Java DSL (without blueprint, directly in a bundle). Regards

Re: camel rest and missing jmx endpoint

i 26 novembre 2020 00:28 > À : users@camel.apache.org > Objet : RE: camel rest and missing jmx endpoint > > Hi Jean-Baptiste, > > I just found out that your mail went to spam...  > > I will of course create a Jira and let you know. > > Regards, > Nicolas >

Re: How to choose a camel component for Http Endpoint Producer and / or Consumer

Hi, It depends of the features you need and the dependencies. For instance, Camel Jetty is "large" but provide a good set of features (it’s used internally in some other components like the salesforce one). Regards JB > Le 4 déc. 2020 à 22:00, Alex Luo a écrit : > > Hi Dear, > > I am

Re: Salesforce streaming issue

Thanks for the update Zoran. I gonna take a look and test. Regards JB > Le 18 déc. 2020 à 13:12, Zoran Regvart a écrit : > > Hi Cameleers, > this has been targeted for releases 3.7.1 and 3.8.0, if you can, it > would be of great help to test this before we release. > > zoran > > On Wed, Dec

Re: [jira] [Resolved] (CAMEL-15936) ClassNotFoundException: org.eclipse.jetty.server.HttpConfiguration$Customizer not found by org.eclipse.jetty.aggregate.jetty-all-server

Hi, Do you have jetty version aligned with Karaf ? Can you share a sample project to reproduce the exception ? Thanks, Regards JB > Le 11 déc. 2020 à 14:26, Prabhu Sharma a écrit : > > Hi Team, > > Could you please suggest any hint on below issue > > Regards, > Prabhu Sharma > > > On

Re: JMX issues with processor

Hi Nicolas, Which camel version are you using ? And which runtime ? Regards JB > Le 14 déc. 2020 à 19:24, CASAUX Nicolas a > écrit : > > Hello ! > > I may have found two minor bugs with data available from processors through > JMX. > > 1) > When I use processors like : >

Re: Increase Exchange timeout value

Hi, It depends of your consumer endpoint (from). Here you are using InOut ExchangePattern, so, the "from" is waiting for the out message but either the out message is not populated or not set at all. If you set the out message "too late", check the configuration of your consumer endpoint.

Re: camel rest and missing jmx endpoint

Hi Nicolas, It sounds like a bug to me (maybe filtering only on URI and not the verb). Can you please create a Jira I will take a look ? Thanks, Regards JB > Le 7 nov. 2020 à 08:54, CASAUX Nicolas a > écrit : > > Hello, > > I’m using some camel rest routes and found something unexpected

Re: Are you using binary distribution?

objection, but this was related to a general discussion about binary > distribution of all the Camel subprojects. > > Il giorno gio 14 gen 2021 alle ore 14:16 Jean-Baptiste Onofre < > j...@nanthrax.net> ha scritto: > >> Hi, >> >> What about a Karaf-camel (I proposed and

Re: Are you using binary distribution?

nibucau <https://twitter.com/rmannibucau> | Blog > <https://rmannibucau.metawerx.net/> | Old Blog > <http://rmannibucau.wordpress.com> | Github <https://github.com/rmannibucau> | > LinkedIn <https://www.linkedin.com/in/rmannibucau> | Book > <https://w

Re: Are you using binary distribution?

Hi, What about a Karaf-camel (I proposed and started to work on karamel ;) ) ? I have a branch where I have karamel distribution (including resources for Kubernetes). If there’s no objection, I will create the camel-karat PR. Thoughts ? Regards JB > Le 14 déc. 2020 à 14:37, Zoran Regvart a

Re: route-list in apache-karaf does not work

By the way, do you have JMX enabled on your route (as a workaround) ? > Le 22 janv. 2021 à 07:46, Jörg Jansen a écrit : > > Hi everybody, > > I'm running camel (3.7.0) in a karaf container (4.3.0). > When trying to list all routes with command route-list, I receive the > following error

Re: route-list in apache-karaf does not work

I just tested on Karaf 4.3.0 with Camel 3.7.0, and it works fine for me: karaf@root()> camel:route-list ContextRoute Status Total # Failed # Inflight # Uptime ---- -- ---

Re: route-list in apache-karaf does not work

Hi, Sorry about that, I will fix that today and I will move forward on the test and cleanup I started. Again, sorry for the inconvenience. Regards JB > Le 22 janv. 2021 à 07:46, Jörg Jansen a écrit : > > Hi everybody, > > I'm running camel (3.7.0) in a karaf container (4.3.0). > When

Re: route-list in apache-karaf does not work

camel-2.16.5 > and karaf 4.0.9 (aka servicemix 7.0.1), I think RouteTemplate will be > the better solution. > I will test it and come back in case the issue appears again. > > Sorry again for the inconvenience. > > Joerg > > Am Fr., 22. Jan. 2021 um 08:00 Uhr schrieb

Re: Setting IBM MQ custom property using Camel and JMS doesn't work

HI, By default, camel-jms populate the JMS property using message headers (assuming you don’t use a header filter strategy). Did you try to set the header ? If the header is MQMHD specific, you have to use camel-wmq (from camel-extra) instead of camel-jms. Regards JB > Le 13 janv. 2021 à

Re: Apacke Karaf, Camel and Kafka component

r snappy (not only camel-sql...) raise errors > mentioned above. > In the morning I will create a Jira issue. > > Thanks. > NC > > > On 5/18/21 7:50 AM, Jean-Baptiste Onofre wrote: >> Hi, >> >> That’s a refresh issue due to range in camel

Re: Apacke Karaf, Camel and Kafka component

Hi, The error seems related to Kafka bundle. Can you check if Kafka bundle version is 2.6.0_2 ? Regards JB > Le 17 mai 2021 à 18:42, Nicola Cisternino a écrit : > > Hi all > I'm using Apache Karaf 4.3.1 to route netty socket on Kafka: > > cat > deploy/example.xml <

Re: Apacke Karaf, Camel and Kafka component

gt;> at java.lang.Thread.run(Unknown Source) [?:?] >>> Caused by: org.apache.felix.resolver.reason.ReasonException: Unable to >>> resolve shell/4.3.2: missing requirement [shell/4.3.2] osgi.identity; >>> osgi.identity=org.apache.karaf.shell.core; type=osgi.bundle; >>> version="[4.3.2,4.3.2]"

Re: [camel-rabbitmq] - InOut pattern and temporary queues

Hi Guillaume, Yes, that’s probably the easiest way. To complete a little: - the correlation can be done on the request message id using a temp destination - the correlation can be done on the client ID using physical destinations Most of the time, ReplyTo header contains a physical response

Re: CXF CodeGen Plugin

Hi Mike, The problem is about the JAXB version you are using. Do you define jaxb-api in your pom dependencies ? Regards JB > Le 31 mai 2021 à 06:54, Mike Oliver a > écrit : > > Hi, > > I am trying to add the cxf-codegen-plugin > > > org.apache.cxf > cxf-codegen-plugin > 3.2.4 >

Re: Rép. : Re: Camel-DNS / Camel 3.7.1 in Karaf 4.2.10 /

Hi, The problem is in the dnsjava bundle: slf4j optional import is missing. I’m fixing that and include in next ServiceMix bundle release. Regards JB > Le 30 avr. 2021 à 14:29, Daniel Langevin a > écrit : > > Hi Claus, > > In the output of headers for the bundles 349(dnsjava),, i dont see

Re: Rép. : Re: Camel-DNS / Camel 3.7.1 in Karaf 4.2.10 /

I created https://issues.apache.org/jira/browse/SM-4761 to track this. I’m cutting release this week end. Regards JB > Le 30 avr. 2021 à 14:29, Daniel Langevin a > écrit : > > Hi Claus, > > In the output of headers for the bundles

Re: bundleReplacements with karaf-maven-plugin

Hi Benjamine, The easiest way is probably to create your own features repository, overriding the feature. Regards JB > Le 3 mai 2021 à 07:55, Benjamin Graf a écrit : > > Hi, > > does anybody know how if possible I can replace a bundle from a feature if a > bit "more complex". > > For

Re: Component "camel-ssh" broken? - NoSuchMethodError: ConnectFuture.getSession()

orno mer 27 gen 2021 alle ore 09:13 Jean-Baptiste Onofre < > j...@nanthrax.net> ha scritto: > >> It’s not tested, but most of the features work fine with Karaf 4.3.0. >> >> However, I agree: I will upgrade to Karaf 4.3.0 for Camel Karaf 3.8.0 >> (it’s already

Re: Component "camel-ssh" broken? - NoSuchMethodError: ConnectFuture.getSession()

It’s not tested, but most of the features work fine with Karaf 4.3.0. However, I agree: I will upgrade to Karaf 4.3.0 for Camel Karaf 3.8.0 (it’s already done ;) ). Regards JB > Le 27 janv. 2021 à 06:30, Andrea Cosentino a écrit : > > Camel 3.7.x doesn't support Karaf 4.3.0, the last version

Re: Component "camel-ssh" broken? - NoSuchMethodError: ConnectFuture.getSession()

Hi Karaf 4.3.0 upgraded to SSHD 2.x (where as Karaf < 4.2.10 uses SSHD 1.x). Camel-ssh should be updated to work with both SSHD 1.x and 2.x. Can you please create a Jira ? I will fix that. Regards JB > Le 26 janv. 2021 à 18:09, Schulze, Jan a écrit > : > > Hi Claus, > > > thanks for your

Re: Simple Blueprint example

Hi, You can find simple examples here: https://github.com/apache/karaf/tree/master/examples/karaf-camel-example Regards JB > Le 22 mars 2021 à 09:18, Michael Oliver a écrit : > > Looking for an example Red Hat Fuse

Re: [HEADS UP] - camel-spring-boot-starter vs camel-spring-boot-engine-starter in Camel 3.9

I think camel-spring-boot-starter is more "classic" name for users. However, it’s great to give the choice in term of dependencies. Regards JB > Le 13 févr. 2021 à 14:39, Claus Ibsen a écrit : > > Hi > > In Camel 3.9 onwards we have modularized camel-spring and the same for > the

Re: Feature camel-atlasmap not found

Hi, It’s Karaf/OSGi specific. In OSGi, a bundle is a jar with additional headers describing the packages that another bundle can use (because we have a graph of class loaders in OSGi instead of a flat one). So, when we have a Camel component, we have two options: 1. The camel component feature

Re: Announcement: New component for creating PDFs from HTML and CSS.

Hi Jeremy, Well done ! You can eventually donate to camel-extra (https://github.com/camel-extra/camel-extra ), it’s up to you. Regards JB > Le 19 juil. 2021 à 16:22, Jeremy Ross a écrit : > > Hi all, > > I've created a new component called

Re: Camel runtime

Hi, I’m not sure I’m the right person to provide advice about the runtime (I might by biased ;)). The only thing that I can share is that I plan to propose karamel (tooling/runtime for camel-karaf upgrading to karaf 5). I hope to have some time in the coming weeks to share some details.