Re: Camel with Karaf + Blueprint

Could you share you’re blueprint XML files? I use Blueprint + Karaf extensively, and I’ve always got into trouble if I mistakenly use the Spring namespace. I’d be interested to see what is different about your Blueprint XML files. > On Mar 9, 2017, at 8:24 AM, kumar

Re: Camel with Karaf + Blueprint

I found the isssue now I am able to load routes and beans . but beans I think i have t make as service to regsiter with Camel and access from other route xml files. Strange thing here is I thin k it is bug in Camel- even though I am using blueprint XML dsl it looks for Spring in . *Problem:*

Re: Camel with Karaf + Blueprint

Hello kumar Show me MANIFEST.MF of your bundle. regards Grzegorz 2017-03-09 11:24 GMT+01:00 kumar : > Hi , > > I am getting below issues with loading Camel-Routes.xml (which has > with blueprint namespace). > > > javax.xml.bind.UnmarshalException: unexpected

Re: Camel with Karaf + Blueprint

Hi , I am getting below issues with loading Camel-Routes.xml (which has with blueprint namespace). javax.xml.bind.UnmarshalException: unexpected element (uri:"http://camel.apache.org/schema/blueprint; local:"routes"). Expected elements are <{http://camel.apache.org/schema/spring}aggregate>

Re: Camel with Karaf + Blueprint

0 down vote favorite I am trying to use Camel(2.18.2) + karaf(4.0.8)+blueprint(Aries) for my migration as suggested by experts. I have separated files as Routes XML files and Beans XML files. RouteXml-> it has only Camel Routes BeanXml-> it has only beans defines *Structure::*

Re: Camel with Karaf + Blueprint

Hi, from your description it sounds that haven't exported the instances you would like to access as services. It is not sufficient to export the packages. The instances that shall be available in other bundle must be exported as services and then they can be referenced as service in your

Re: Camel Log - Karaf

Camel uses the id of the route as the logger name by default. If you want to use a different name you can specify the logger name in the On Thu, Oct 20, 2016 at 8:08 PM, ychawla wrote: > Hi Shuston, > I can do log:set DEBUG but then I log everything. I have a file

RE: Camel Log - Karaf

chawla [mailto:premiergenerat...@gmail.com] > Sent: Thursday, October 20, 2016 2:09 PM > To: users@camel.apache.org > Subject: RE: Camel Log - Karaf > > Hi Shuston, > I can do log:set DEBUG but then I log everything. I have a file endpoint > that I > poll from and t

RE: Camel Log - Karaf

Hi Shuston, I can do log:set DEBUG but then I log everything. I have a file endpoint that I poll from and that generates too much logging for it to be useful. Is there a way to isolate it to the route or context level? Thanks, Yogesh -- View this message in context:

RE: Camel Log - Karaf

Try log:set DEBUG > -Original Message- > From: ychawla [mailto:premiergenerat...@gmail.com] > Sent: Thursday, October 20, 2016 11:34 AM > To: users@camel.apache.org > Subject: Camel Log - Karaf > > Hello All, > I have a log statement in a camel route that is at the DEBUG loggingLevel: >

Re: Camel and Karaf compatibility

Hi Usually it means the minimum version. You can use Camel 2.15 on Karaf 3.0.x and 4.0.x as well. Though use the latest releases of Karaf as I think there was a problem with one of the .0 release of those. On Tue, Sep 8, 2015 at 9:59 AM, michael.esmann wrote: >

Aw: Re: Re: Camel with Karaf

@camel.apache.org Betreff: Re: Re: Camel with Karaf Hi, For some component, you have to export them as Osgi services, then referencing in your bp.xml as the prefix you use it in your route. I would do so for the SQL component: reference id=sql interface

Re: Re: Re: Camel with Karaf

An: users@camel.apache.org Betreff: Re: Re: Camel with Karaf Hi, For some component, you have to export them as Osgi services, then referencing in your bp.xml as the prefix you use it in your route. I would do so for the SQL component: reference id=sql interface

Re: Camel with Karaf

Hi Pascal, one quick question, are you using JDK 8.0? I’m facing a similar behaviour when running Karaf on JDK 8.0 - without any Camel: org.osgi.service.blueprint.container.ComponentDefinitionException: java.lang.IllegalArgumentException at

Aw: Re: Camel with Karaf

Gesendet: Dienstag, 25. März 2014 um 16:16 Uhr Von: cemmersb cemme...@gmail.com An: users@camel.apache.org Betreff: Re: Camel with Karaf Hi Pascal, one quick question, are you using JDK 8.0? I’m facing a similar behaviour when running Karaf on JDK 8.0 - without any Camel

Re: Re: Camel with Karaf

- I was not excatly sure what you meant with the question). Greetings, Pascal Gesendet: Dienstag, 25. März 2014 um 16:16 Uhr Von: cemmersb cemme...@gmail.com An: users@camel.apache.org Betreff: Re: Camel with Karaf Hi Pascal, one quick question, are you using JDK 8.0

Aw: Re: Re: Camel with Karaf

2014 um 17:50 Uhr Von: Charlie Mordant cmorda...@gmail.com An: users@camel.apache.org Betreff: Re: Re: Camel with Karaf Hi, For some component, you have to export them as Osgi services, then referencing in your bp.xml as the prefix you use it in your route. I would do so

Re: Camel for Karaf 2.0

L.S., The closest matching Camel version would be 2.5.0, which was using Karaf 2.1.0 at the time it was released. I suspect that 2.6.0 and 2.7.x might install fine as well, but you would have to give those a try to be sure. Regards, Gert Vanthienen FuseSource Web:

Re: Camel for Karaf 2.0

L.S., You'll probably have to strike 2.7.x as an option as well, as those have a reference to mvn:org.apache.karaf.assemblies.features/standard/2.2.0/xml/features or something like that and that's probably not going to work either. Regards, Gert Vanthienen FuseSource

Re: camel-cxf karaf 2.2.0 failure

Its a bit painful to get CXF running in Karaf as you need to mess with the jre.properties to get it working. Its often easiest to copy the jre.properties from Apache ServiceMix project and use that. This is shown how to do in chapter 13 in the Camel in Action book. - Claus Ibsen

Re: Camel + NMR + Karaf (OSGi) possible without ServiceMix?

Ok, I've got the NMR stuff loaded. But have still an unresolved dependency to org.apache.servicemix.camel.nmr. Any idea, what the URI is for the corresponding feature file. That is the one, which contains the camel-nmr feature (if that exists). Thanks, klaus. -- View this message in context:

Re: Camel + NMR + Karaf (OSGi) possible without ServiceMix?

camel-nmr feature is provided by ServiceMix 4 (the main features subproject). It's contained in the features descriptor available on, for example: mvn:org.apache.servicemix/apache-servicemix/4.3.0-SNAPSHOT This features descriptor provides camel-nmr, camel-activemq, examples-camel-osgi,

Re: camel-servlet / Karaf / War / Tomcat

yep but in this case, we create a dependency between CamelHttpTransportServlet and Karaf bootsrap class. This is not really important as I'm not sure that using camel + karaf or SMX4 embedded in a WAR is the best choice. It is better to create a classical WAR in this case containing camel/spring

Re: camel-servlet / Karaf / War / Tomcat

Hi Charles, I think if you can make sure the servlet is deployed before the camel context started, the camel-servlet endpoint can get the access the CamelHttpTransportServlet instance. As the CamelHttpTransportServlet and Karaf are using the same classloader, I think it should be OK for