Re: camelContext not found in karaf 4.1.0

[achi1955]

Hi I am running karaf 4.1.0 and camel 2.18.3 on raspberyPi I think my problem 
is that I have to mix different Spring versions 3 and 4 as Cristian said. with 
Karaf 4.0.8 and camel 2.17.2 I have no problems, so I will stay there for a 
while … Plamen On 23 Mar 2017, at 17:18, mtod09 [via Camel]  
ml-node+s465427n5796042...@n5.nabble.com  wrote: 

Hmm checking the Camel FAQ web site I come up with this:
Important changes to consider when upgrading
Java 1.8 is now required.
Karaf 2.4.x is no longer supported. Karaf 4.x is the primary supported OSGi 
platform. Jetty 8.x is no longer supported and camel-jetty8 has been removed
spring 4.0 is no longer supported and camel-test-spring40 has been removed
spring 3.x is no longer supported
Upgraded to Spring 4.3.x and Spring Boot 1.4.x
http://camel.apache.org/camel-2180-release.html So I guess I'm ok.
Mike








If you reply to this email, your message will be added to the 
discussion below: 

http://camel.465427.n5.nabble.com/camelContext-not-found-in-karaf-4-1-0-tp5795994p5796042.html
 



To unsubscribe from camelContext not found in karaf 4.1.0, 
click here . 
NAML 




--
View this message in context: 
http://camel.465427.n5.nabble.com/camelContext-not-found-in-karaf-4-1-0-tp5795994p5796062.html
Sent from the Camel - Users mailing list archive at Nabble.com.

concurrentConsumers, failIfNoConsumers confusion

[alapaka]

Hi All;

I am trying to implement a route that can process only one message at a
time; the route should reject incoming messages if it is busy. To be clear,
I do not want messages to be queued for processing, I want them to be
rejected and discarded, preferably with an exception returned to the caller.

It would seem that some combination of options on a seda endpoint should do
the trick, however I am not able to achieve this functionality.

Here is my test code, running on camel 2.16.3 in ServiceMix 6.1.2:

from("seda:test-server?concurrentConsumers=1=true=false")
.log("test server - got request...")
.delay(15000)
.log("test server - sending reply")
.routeId("test-server");

from("direct-vm:test-client")
.log("test client calling server")

.to("seda:test-server?concurrentConsumers=1=true=false")
.log("test client got reply")
.routeId("test-client");

output from calling the "test-client" route 7 times in less than 10 seconds:

2017-03-24 15:09:03,756 | 126 - org.apache.camel.camel-core - 2.16.3 | test
client calling server
2017-03-24 15:09:03,757 | 126 - org.apache.camel.camel-core - 2.16.3 | test
client got reply
2017-03-24 15:09:03,757 | 126 - org.apache.camel.camel-core - 2.16.3 | test
server - got request...
2017-03-24 15:09:04,392 | 126 - org.apache.camel.camel-core - 2.16.3 | test
client calling server
2017-03-24 15:09:04,393 | 126 - org.apache.camel.camel-core - 2.16.3 | test
client got reply
2017-03-24 15:09:05,073 | 126 - org.apache.camel.camel-core - 2.16.3 | test
client calling server
2017-03-24 15:09:05,074 | 126 - org.apache.camel.camel-core - 2.16.3 | test
client got reply
2017-03-24 15:09:07,997 | 126 - org.apache.camel.camel-core - 2.16.3 | test
client calling server
2017-03-24 15:09:07,998 | 126 - org.apache.camel.camel-core - 2.16.3 | test
client got reply
2017-03-24 15:09:11,228 | 126 - org.apache.camel.camel-core - 2.16.3 | test
client calling server
2017-03-24 15:09:11,229 | 126 - org.apache.camel.camel-core - 2.16.3 | test
client got reply
2017-03-24 15:09:11,923 | 126 - org.apache.camel.camel-core - 2.16.3 | test
client calling server
2017-03-24 15:09:11,924 | 126 - org.apache.camel.camel-core - 2.16.3 | test
client got reply
2017-03-24 15:09:12,552 | 126 - org.apache.camel.camel-core - 2.16.3 | test
client calling server
2017-03-24 15:09:12,552 | 126 - org.apache.camel.camel-core - 2.16.3 | test
client got reply
2017-03-24 15:09:18,760 | 126 - org.apache.camel.camel-core - 2.16.3 | test
server - sending reply
2017-03-24 15:09:18,761 | 126 - org.apache.camel.camel-core - 2.16.3 | test
server - got request...
2017-03-24 15:09:33,762 | 126 - org.apache.camel.camel-core - 2.16.3 | test
server - sending reply
2017-03-24 15:09:33,763 | 126 - org.apache.camel.camel-core - 2.16.3 | test
server - got request...
2017-03-24 15:09:48,765 | 126 - org.apache.camel.camel-core - 2.16.3 | test
server - sending reply
2017-03-24 15:09:48,766 | 126 - org.apache.camel.camel-core - 2.16.3 | test
server - got request...
2017-03-24 15:10:03,767 | 126 - org.apache.camel.camel-core - 2.16.3 | test
server - sending reply
2017-03-24 15:10:03,768 | 126 - org.apache.camel.camel-core - 2.16.3 | test
server - got request...
2017-03-24 15:10:18,770 | 126 - org.apache.camel.camel-core - 2.16.3 | test
server - sending reply
2017-03-24 15:10:18,771 | 126 - org.apache.camel.camel-core - 2.16.3 | test
server - got request...
2017-03-24 15:10:33,772 | 126 - org.apache.camel.camel-core - 2.16.3 | test
server - sending reply
2017-03-24 15:10:33,773 | 126 - org.apache.camel.camel-core - 2.16.3 | test
server - got request...
2017-03-24 15:10:48,775 | 126 - org.apache.camel.camel-core - 2.16.3 | test
server - sending reply

I have tried just about every combination of options on both server and
client, yet no joy.
I know there are other ways to implement this e.g. activemq, database lock,
thread pool? etc... however I would rather a cleaner solution, handled
simply at the incoming endpoint - if that is indeed possible.







--
View this message in context: 
http://camel.465427.n5.nabble.com/concurrentConsumers-failIfNoConsumers-confusion-tp5796061.html
Sent from the Camel - Users mailing list archive at Nabble.com.

Re: Need help retaining files in source folder..

[Quinn Stevenson]

Did you try setting idempotent=false in addition to noop=true?  I know 
noop=true sets idempotent=true, but you may be able to override it.


> On Mar 23, 2017, at 2:09 PM, Hari  wrote:
> 
> Thank you souciance..
> 
> I need the file in same folder, as eventually, there would be a process,
> which pick up the file and turn the status to completed, on which i need to
> push the file to another completed folder..
> 
> The folder might contain hundreds of file, however only few of them will
> turn to completed status. I was planning on running camel in quartz for
> every 2 hrs to move the completed files.
> 
> Any ideas on how to manage this will be of great help..
> 
> 
> 
> --
> View this message in context: 
> http://camel.465427.n5.nabble.com/Need-help-retaining-files-in-source-folder-tp5796053p5796055.html
> Sent from the Camel - Users mailing list archive at Nabble.com.

Re: Need help retaining files in source folder..

[Hari]

Thank you souciance..

I need the file in same folder, as eventually, there would be a process,
which pick up the file and turn the status to completed, on which i need to
push the file to another completed folder..

The folder might contain hundreds of file, however only few of them will
turn to completed status. I was planning on running camel in quartz for
every 2 hrs to move the completed files.

Any ideas on how to manage this will be of great help..



--
View this message in context: 
http://camel.465427.n5.nabble.com/Need-help-retaining-files-in-source-folder-tp5796053p5796055.html
Sent from the Camel - Users mailing list archive at Nabble.com.

Re: Need help retaining files in source folder..

[souciance]

I know that is your requirement but wouldn't it make sense to move the
files that failed the filter to some other folder so it will be easier to
notice them rather than keep them in the source folder? Makes everything
more complicated.

On Thu, Mar 23, 2017 at 8:51 PM, Hari [via Camel] <
ml-node+s465427n579605...@n5.nabble.com> wrote:

> Hi,
>
> I am new to camel. I have a requirement to move XML files from one
> directory to another based on some conditions in the content of the XML
> file.
>
> Here is how the route i wrote looks like. The StatusFilter, returns true
> or false , based on the condition. When the condition is not met, I need
> the file to remain in the source folder. The below route does not move the
> file when the filter returns false, which is exactly what i want, but it is
> moving the file to .camel folder.
>
> Need help to retain the file in the source folder, when the condition is
> not met. Tried noop and delete options, but it did not work.
>
> from("file:d:\\data\\inprocess?recursive=true").
> convertBodyTo(String.class).filter().method(new StatusFilter(),
> "filter").
> process(new Processor() {
> public void process(Exchange exchange) throws
> Exception {
> 
> ..
> }
> }).
> to("file:d:\\data\\register\\completed");
>
>
> Please help.
> Regards,
> Hari
>
>
>
>
>
> --
> If you reply to this email, your message will be added to the discussion
> below:
> http://camel.465427.n5.nabble.com/Need-help-retaining-files-
> in-source-folder-tp5796053.html
> To start a new topic under Camel - Users, email
> ml-node+s465427n465428...@n5.nabble.com
> To unsubscribe from Camel - Users, click here
> 
> .
> NAML
> 
>




--
View this message in context: 
http://camel.465427.n5.nabble.com/Need-help-retaining-files-in-source-folder-tp5796053p5796054.html
Sent from the Camel - Users mailing list archive at Nabble.com.

Need help retaining files in source folder..

[Hari]

Hi,

I am new to camel. I have a requirement to move XML files from one directory
to another based on some conditions in the content of the XML file.  

Here is how the route i wrote looks like. The StatusFilter, returns true or
false , based on the condition. When the condition is not met, I need the
file to remain in the source folder. The below route does not move the file
when the filter returns false, which is exactly what i want, but it is
moving the file to .camel folder. 

Need help to retain the file in the source folder, when the condition is not
met. Tried noop and delete options, but it did not work.

from("file:d:\\data\\inprocess?recursive=true").convertBodyTo(String.class).filter().method(new
StatusFilter(), "filter").
process(new Processor() {
public void process(Exchange exchange) throws Exception {

..
}
}).
to("file:d:\\data\\register\\completed");


Please help.
Regards,
Hari







--
View this message in context: 
http://camel.465427.n5.nabble.com/Need-help-retaining-files-in-source-folder-tp5796053.html
Sent from the Camel - Users mailing list archive at Nabble.com.

Camel instanciated as null

[mtod09]

Background :
I'm running camel 2.18.3 on a AWS karaf 4.1.0 platform.

I have a simple route using restlet that works fine but when using a route
with a endpoint activemq artemis it fails with the following error.

org.osgi.service.blueprint.container.ComponentDefinitionException: Name
jmsConnectionFactory is already instanciated as null and cannot be removed.

I'm not sure what I'm doing wrong thanks for the help.

My route.xml

 
http://www.osgi.org/xmlns/blueprint/v1.0.0;
   xmlns:jaas="http://karaf.apache.org/xmlns/jaas/v1.0.0;
  
xmlns:ext="http://aries.apache.org/blueprint/xmlns/blueprint-ext/v1.0.0;>
   
 
 
 


 
 
 


 














http://camel.apache.org/schema/blueprint;>   





/km:FMIMessage/km:Header/km:Route/text()


Route1



org.apache.camel.ValidationException


${exception.message}













--
View this message in context: 
http://camel.465427.n5.nabble.com/Camel-instanciated-as-null-tp5796043.html
Sent from the Camel - Users mailing list archive at Nabble.com.

Re: camelContext not found in karaf 4.1.0

[mtod09]

Hmm checking the Camel FAQ web site I come up with this:

Important changes to consider when upgrading
Java 1.8 is now required.
*Karaf 2.4.x is no longer supported. Karaf 4.x is the primary supported OSGi
platform.*
Jetty 8.x is no longer supported and camel-jetty8 has been removed
spring 4.0 is no longer supported and camel-test-spring40 has been removed
spring 3.x is no longer supported
Upgraded to Spring 4.3.x and Spring Boot 1.4.x

http://camel.apache.org/camel-2180-release.html

So I guess I'm ok.

Mike



--
View this message in context: 
http://camel.465427.n5.nabble.com/camelContext-not-found-in-karaf-4-1-0-tp5795994p5796042.html
Sent from the Camel - Users mailing list archive at Nabble.com.

Re: camelContext not found in karaf 4.1.0

[mtod09]

I'm running into a few issues also.

I'm running Karaf 4.1.0 and Camel 2.18.3 on AWS.

What are the current approved versions?

Mike



--
View this message in context: 
http://camel.465427.n5.nabble.com/camelContext-not-found-in-karaf-4-1-0-tp5795994p5796041.html
Sent from the Camel - Users mailing list archive at Nabble.com.

Unable to Catch an Exception in Netty

[hammod]

I have a Netty interface that accepts a message and puts this message in a
queue (ActiveMQ), if the connection to the queue is down while camel is
running then there is an exception happening in Netty after receiving the
caller's message that I can't catch in any OnException and any ErrorHandler,
I tried using LoadBalance and failover but still the same issue, the problem
in this case is the caller is waiting until timeout and even if the
connection to the queue is restored, Camel is losing the caller's message
and not continuing the route ( which is the worst issue).

My Routes : 





















Stack Trace :

[ #22 - NettyEventExecutorGroup] TransactionErrorHandlerWARN 
Transaction rollback (0x443253a6) redelivered(unknown) for (MessageId:
ID-Mohammadt-460-57273-1490283881916-0-1 on ExchangeId:
ID-Mohammadt-460-57273-1490283881916-0-2) caught: Could not create JMS
transaction; nested exception is javax.jms.JMSException: Error while
attempting to add new Connection to the pool
[ead #21 - NettyServerTCPWorker] NettyConsumer  WARN  Caused
by: [org.apache.camel.CamelExchangeException - Cannot write response to
/127.0.0.1:57441. Exchange[ID-Mohammadt-460-57273-1490283881916-0-2]. Caused
by: [io.netty.handler.codec.EncoderException -
org.springframework.transaction.CannotCreateTransactionException: Could not
create JMS transaction; nested exception is javax.jms.JMSException: Error
while attempting to add new Connection to the pool]]
org.apache.camel.CamelExchangeException: Cannot write response to
/127.0.0.1:57441. Exchange[ID-Mohammadt-460-57273-1490283881916-0-2]. Caused
by: [io.netty.handler.codec.EncoderException -
org.springframework.transaction.CannotCreateTransactionException: Could not
create JMS transaction; nested exception is javax.jms.JMSException: Error
while attempting to add new Connection to the pool]
at
org.apache.camel.component.netty4.handlers.ServerResponseFutureListener.operationComplete(ServerResponseFutureListener.java:54)
[camel-netty4-2.18.2.jar:2.18.2]
at
org.apache.camel.component.netty4.handlers.ServerResponseFutureListener.operationComplete(ServerResponseFutureListener.java:36)
[camel-netty4-2.18.2.jar:2.18.2]
at
io.netty.util.concurrent.DefaultPromise.notifyListener0(DefaultPromise.java:507)
[netty-all-4.1.7.Final.jar:4.1.7.Final]
at
io.netty.util.concurrent.DefaultPromise.notifyListenersNow(DefaultPromise.java:481)
[netty-all-4.1.7.Final.jar:4.1.7.Final]
at
io.netty.util.concurrent.DefaultPromise.notifyListeners(DefaultPromise.java:420)
[netty-all-4.1.7.Final.jar:4.1.7.Final]
at
io.netty.util.concurrent.DefaultPromise.tryFailure(DefaultPromise.java:122)
[netty-all-4.1.7.Final.jar:4.1.7.Final]
at
io.netty.util.internal.PromiseNotificationUtil.tryFailure(PromiseNotificationUtil.java:64)
[netty-all-4.1.7.Final.jar:4.1.7.Final]
at
io.netty.channel.AbstractChannelHandlerContext.notifyOutboundHandlerException(AbstractChannelHandlerContext.java:837)
[netty-all-4.1.7.Final.jar:4.1.7.Final]
at
io.netty.channel.AbstractChannelHandlerContext.invokeWrite0(AbstractChannelHandlerContext.java:741)
[netty-all-4.1.7.Final.jar:4.1.7.Final]
at
io.netty.channel.AbstractChannelHandlerContext.invokeWrite(AbstractChannelHandlerContext.java:731)
[netty-all-4.1.7.Final.jar:4.1.7.Final]
at
io.netty.channel.AbstractChannelHandlerContext.access$1900(AbstractChannelHandlerContext.java:38)
[netty-all-4.1.7.Final.jar:4.1.7.Final]
at
io.netty.channel.AbstractChannelHandlerContext$AbstractWriteTask.write(AbstractChannelHandlerContext.java:1090)
[netty-all-4.1.7.Final.jar:4.1.7.Final]
at
io.netty.channel.AbstractChannelHandlerContext$WriteAndFlushTask.write(AbstractChannelHandlerContext.java:1137)
[netty-all-4.1.7.Final.jar:4.1.7.Final]
at
io.netty.channel.AbstractChannelHandlerContext$AbstractWriteTask.run(AbstractChannelHandlerContext.java:1079)
[netty-all-4.1.7.Final.jar:4.1.7.Final]
at
io.netty.util.concurrent.AbstractEventExecutor.safeExecute(AbstractEventExecutor.java:163)
[netty-all-4.1.7.Final.jar:4.1.7.Final]
at
io.netty.util.concurrent.SingleThreadEventExecutor.runAllTasks(SingleThreadEventExecutor.java:403)
[netty-all-4.1.7.Final.jar:4.1.7.Final]
at io.netty.channel.nio.NioEventLoop.run(NioEventLoop.java:445)
[netty-all-4.1.7.Final.jar:4.1.7.Final]
at
io.netty.util.concurrent.SingleThreadEventExecutor$5.run(SingleThreadEventExecutor.java:858)
[netty-all-4.1.7.Final.jar:4.1.7.Final]
at java.lang.Thread.run(Thread.java:745) [?:1.8.0_91]
Caused by: 

Re: Rollback in Multicast after catching an exception

[hammod]

This solved the problem, Thanks!



--
View this message in context: 
http://camel.465427.n5.nabble.com/Rollback-in-Multicast-after-catching-an-exception-tp5795896p5796037.html
Sent from the Camel - Users mailing list archive at Nabble.com.

Re: camelContext not found in karaf 4.1.0

[Christian Schneider]

That is a good question. I think the current state is not good as mixing 
spring 3 and 4 simply does not seem to work.

I will ask in a separate thread what the plans are.

Christian

On 23.03.2017 12:44, achi1955 wrote:

Hi

will this problem be fixed in the future versions or I really have to migrate 
to blueprint

Regards
Plamen Traianov




On 23 Mar 2017, at 11:54, Christian Schneider [via Camel] 
 wrote:

You can fix this error by adding the spring legacy repo.
features:repo-add spring-legacy 4.1.0
It provides older versions of spring.

Unfortunately camel-spring-dm (2.18) still will not fully work.

The problem is that camel-spring-dm requires spring 3 while the rest of
the camel components requires spring 4.
So in the end both spring versions get installed and it does not work.

So for camel 2.18 you have to move from spring dm to blueprint.

Christian

On 23.03.2017 10:01, achi1955 wrote:


Hi,

now  I get:

Error executing command: Unable to resolve root: missing requirement [root] osgi.identity; 
osgi.identity=camel-spring-dm; type=karaf.feature; version="[2.18.3,2.18.3]"; 
filter:="(&(osgi.identity=camel-spring-dm)(type=karaf.feature)(version>=2.18.3)(version<=2.18.3))" 
[caused by: Unable to resolve camel-spring-dm/2.18.3: missing requirement [camel-spring-dm/2.18.3] osgi.identity; 
osgi.identity=spring-dm; type=karaf.feature; version="[1.2.0,2.0.0)"]


probably something is missing, I installed feature: spring, camel-spring
but as a tried camel-spring-dm I've got the message from above


Plamen


On 23 Mar 2017, at 09:40, Claus Ibsen-2 [via Camel] <[hidden email] 
> wrote:

That is in Camel 2.18 onwards
https://github.com/apache/camel/blob/camel-2.18.x/platforms/karaf/features/src/main/resources/features.xml#L71
 

 
>

But mind Karaf 4.1.x is not officially supported for Camel. Its a new
release and it changed a fair amount of stuff that can break stuff.
Use it with caution.

On Thu, Mar 23, 2017 at 9:23 AM, achi1955 <[hidden email] 
>> wrote:


Hi

it says:

Error executing command: No matching features for camel-spring-dm/0.0.0

achi1955
Plamen Traianov



On 23 Mar 2017, at 09:12, Claus Ibsen-2 [via Camel] <[hidden email] 
>> wrote:

Try install camel-spring-dm feature

On Thu, Mar 23, 2017 at 8:35 AM, achi1955 <[hidden email] 
>> wrote:


I am working for years with Camel and Karaf on RaspberyPi without problems.
Last version I used is Karaf 4.0.8 and Camel 2.17.2. I installed my bundle
into Karaf 4.1.0 and there was no reaction - no error messages , but no
reaction on my camelContext (META-INF/spring/camel-context.xml). I did not
found feature spring-dm, but it was not possible to install.

Are there any changes by by deployment or is there something to install
additionaly?
please help



--
View this message in context: http://camel.465427.n5.nabble.com/camelContext-not-found-in-karaf-4-1-0-tp5795994.html 
 
> 
 
>>
Sent from the Camel - Users mailing list archive at Nabble.com 
.


--
Claus Ibsen
-
http://davsclaus.com  > 
 >> 
@davsclaus
Camel in Action 2: https://www.manning.com/ibsen2  
>  >>


If you reply to this email, your message will be added to the discussion below:
http://camel.465427.n5.nabble.com/camelContext-not-found-in-karaf-4-1-0-tp5795994p5795996.html 
 
> 

Re: Unable to update httpclientconfigurer instance on dynamic to endpoint.

[Abhishek.Jha09]

My api expects the url to be like "http://server-name:port/user/id;. Removing
${headers.id} violates this. And this property changes with every request.
So, I can't remove that and I'm forced to use toD().


Zoran Regvart-2 wrote
> Hi Abhishek,
> try setting the `Exchange.HTTP_PATH` header, something like:
> 
> from("direct:a").setHeader(Exchange.HTTP_PATH,
> simple("${headers.id}").to("http4://localhost8080/user/?httpClientConfigurer=myHttpConfigClient")
> 
> zoran
> 
> On Wed, Mar 22, 2017 at 11:23 PM, Abhishek.Jha09 

> abhij03@

>  wrote:
>> Hi all,
>>
>> Subject pretty much sums up my query. I have a route like
>>
>>from("direct:a").routeId("myroute")
>>
>> .toD("http4://localhost:8080/user/${headers.id}?httpClientConfigurer=myHttpConfigClient")
>>
>> I have set up "myHttpConfigClient" in SimpleRegistry in camel context.
>> When
>> I change the config values of this instance and add the route again to
>> camel
>> context, the config parameters don't change. However, if I do the same in
>> a
>> route created like below, without dynamic to, it works perfectly fine.
>>
>>from("direct:a").routeId("myroute")
>>
>> .to("http4://localhost:8080/user?httpClientConfigurer=myHttpConfigClient")
>>
>> Can anyone please help me with this?
>>
>>
>>
>> --
>> View this message in context:
>> http://camel.465427.n5.nabble.com/Unable-to-update-httpclientconfigurer-instance-on-dynamic-to-endpoint-tp5795918.html
>> Sent from the Camel - Users mailing list archive at Nabble.com.
> 
> 
> 
> -- 
> Zoran Regvart





--
View this message in context: 
http://camel.465427.n5.nabble.com/Unable-to-update-httpclientconfigurer-instance-on-dynamic-to-endpoint-tp5795918p5796026.html
Sent from the Camel - Users mailing list archive at Nabble.com.

Re: camelContext not found in karaf 4.1.0

[achi1955]

Hi

will this problem be fixed in the future versions or I really have to migrate 
to blueprint

Regards
Plamen Traianov



> On 23 Mar 2017, at 11:54, Christian Schneider [via Camel] 
>  wrote:
> 
> You can fix this error by adding the spring legacy repo. 
> features:repo-add spring-legacy 4.1.0 
> It provides older versions of spring. 
> 
> Unfortunately camel-spring-dm (2.18) still will not fully work. 
> 
> The problem is that camel-spring-dm requires spring 3 while the rest of 
> the camel components requires spring 4. 
> So in the end both spring versions get installed and it does not work. 
> 
> So for camel 2.18 you have to move from spring dm to blueprint. 
> 
> Christian 
> 
> On 23.03.2017 10:01, achi1955 wrote:
> 
> > Hi, 
> > 
> > now  I get: 
> > 
> > Error executing command: Unable to resolve root: missing requirement [root] 
> > osgi.identity; osgi.identity=camel-spring-dm; type=karaf.feature; 
> > version="[2.18.3,2.18.3]"; 
> > filter:="(&(osgi.identity=camel-spring-dm)(type=karaf.feature)(version>=2.18.3)(version<=2.18.3))"
> >  [caused by: Unable to resolve camel-spring-dm/2.18.3: missing requirement 
> > [camel-spring-dm/2.18.3] osgi.identity; osgi.identity=spring-dm; 
> > type=karaf.feature; version="[1.2.0,2.0.0)"] 
> > 
> > 
> > probably something is missing, I installed feature: spring, camel-spring 
> > but as a tried camel-spring-dm I've got the message from above 
> > 
> > 
> > Plamen 
> > 
> >> On 23 Mar 2017, at 09:40, Claus Ibsen-2 [via Camel] <[hidden email] 
> >> > wrote: 
> >> 
> >> That is in Camel 2.18 onwards 
> >> https://github.com/apache/camel/blob/camel-2.18.x/platforms/karaf/features/src/main/resources/features.xml#L71
> >>  
> >> 
> >>  
> >>  >>  
> >> >
> >>  
> >> 
> >> But mind Karaf 4.1.x is not officially supported for Camel. Its a new 
> >> release and it changed a fair amount of stuff that can break stuff. 
> >> Use it with caution. 
> >> 
> >> On Thu, Mar 23, 2017 at 9:23 AM, achi1955 <[hidden email] 
> >>  >> >> wrote: 
> >> 
> >>> Hi 
> >>> 
> >>> it says: 
> >>> 
> >>> Error executing command: No matching features for camel-spring-dm/0.0.0 
> >>> 
> >>> achi1955 
> >>> Plamen Traianov 
> >>> 
> >>> 
>  On 23 Mar 2017, at 09:12, Claus Ibsen-2 [via Camel] <[hidden email] 
>    >> wrote: 
>  
>  Try install camel-spring-dm feature 
>  
>  On Thu, Mar 23, 2017 at 8:35 AM, achi1955 <[hidden email] 
>    >> wrote: 
>  
> > I am working for years with Camel and Karaf on RaspberyPi without 
> > problems. 
> > Last version I used is Karaf 4.0.8 and Camel 2.17.2. I installed my 
> > bundle 
> > into Karaf 4.1.0 and there was no reaction - no error messages , but no 
> > reaction on my camelContext (META-INF/spring/camel-context.xml). I did 
> > not 
> > found feature spring-dm, but it was not possible to install. 
> > 
> > Are there any changes by by deployment or is there something to install 
> > additionaly? 
> > please help 
> > 
> > 
> > 
> > -- 
> > View this message in context: 
> > http://camel.465427.n5.nabble.com/camelContext-not-found-in-karaf-4-1-0-tp5795994.html
> >  
> > 
> >  
> >  >  
> > >
> >  
> >  >  
> > 
> >  
> >  >  
> > >>
> >  
> > Sent from the Camel - Users mailing list archive at Nabble.com 
> > . 
>  
>  
>  -- 
>  Claus Ibsen 
>  - 
>  http://davsclaus.com    >  
>  >> @davsclaus 
>  Camel in Action 2: https://www.manning.com/ibsen2 
>     >    

Re: A simple Web Service consumer and producer using Apache Camel

[anirban.gupta4]

We generally generate the java classes from WSDL using Apache CXF when using
Camel. Can we generate the Java classes using wsimport and expose them as
bean? As the syntax of the classes generated using CXF wsdl2java and
wsimport are slightly different.



--
View this message in context: 
http://camel.465427.n5.nabble.com/A-simple-Web-Service-consumer-and-producer-using-Apache-Camel-tp5796012p5796022.html
Sent from the Camel - Users mailing list archive at Nabble.com.

Re: camelContext not found in karaf 4.1.0

[Christian Schneider]

You can fix this error by adding the spring legacy repo.
features:repo-add spring-legacy 4.1.0
It provides older versions of spring.

Unfortunately camel-spring-dm (2.18) still will not fully work.

The problem is that camel-spring-dm requires spring 3 while the rest of 
the camel components requires spring 4.

So in the end both spring versions get installed and it does not work.

So for camel 2.18 you have to move from spring dm to blueprint.

Christian

On 23.03.2017 10:01, achi1955 wrote:

Hi,

now  I get:

Error executing command: Unable to resolve root: missing requirement [root] osgi.identity; 
osgi.identity=camel-spring-dm; type=karaf.feature; version="[2.18.3,2.18.3]"; 
filter:="(&(osgi.identity=camel-spring-dm)(type=karaf.feature)(version>=2.18.3)(version<=2.18.3))" 
[caused by: Unable to resolve camel-spring-dm/2.18.3: missing requirement [camel-spring-dm/2.18.3] osgi.identity; 
osgi.identity=spring-dm; type=karaf.feature; version="[1.2.0,2.0.0)"]


probably something is missing, I installed feature: spring, camel-spring
but as a tried camel-spring-dm I've got the message from above


Plamen


On 23 Mar 2017, at 09:40, Claus Ibsen-2 [via Camel] 
 wrote:

That is in Camel 2.18 onwards
https://github.com/apache/camel/blob/camel-2.18.x/platforms/karaf/features/src/main/resources/features.xml#L71
 


But mind Karaf 4.1.x is not officially supported for Camel. Its a new
release and it changed a fair amount of stuff that can break stuff.
Use it with caution.

On Thu, Mar 23, 2017 at 9:23 AM, achi1955 <[hidden email] 
> wrote:


Hi

it says:

Error executing command: No matching features for camel-spring-dm/0.0.0

achi1955
Plamen Traianov



On 23 Mar 2017, at 09:12, Claus Ibsen-2 [via Camel] <[hidden email] 
> wrote:

Try install camel-spring-dm feature

On Thu, Mar 23, 2017 at 8:35 AM, achi1955 <[hidden email] 
> wrote:


I am working for years with Camel and Karaf on RaspberyPi without problems.
Last version I used is Karaf 4.0.8 and Camel 2.17.2. I installed my bundle
into Karaf 4.1.0 and there was no reaction - no error messages , but no
reaction on my camelContext (META-INF/spring/camel-context.xml). I did not
found feature spring-dm, but it was not possible to install.

Are there any changes by by deployment or is there something to install
additionaly?
please help



--
View this message in context: 
http://camel.465427.n5.nabble.com/camelContext-not-found-in-karaf-4-1-0-tp5795994.html 
 
>
Sent from the Camel - Users mailing list archive at Nabble.com.



--
Claus Ibsen
-
http://davsclaus.com  > @davsclaus
Camel in Action 2: https://www.manning.com/ibsen2  
>


If you reply to this email, your message will be added to the discussion below:
http://camel.465427.n5.nabble.com/camelContext-not-found-in-karaf-4-1-0-tp5795994p5795996.html 

 
>
To unsubscribe from camelContext not found in karaf 4.1.0, click here <
NAML < 
http://camel.465427.n5.nabble.com/template/NamlServlet.jtp?macro=macro_viewer=instant_html%21nabble%3Aemail.naml=nabble.naml.namespaces.BasicNamespace-nabble.view.web.template.NabbleNamespace-nabble.view.web.template.NodeNamespace=notify_subscribers%21nabble%3Aemail.naml-instant_emails%21nabble%3Aemail.naml-send_instant_email%21nabble%3Aemail.naml
 
>




--
View this message in context: 
http://camel.465427.n5.nabble.com/camelContext-not-found-in-karaf-4-1-0-tp5795994p5795997.html
 

Sent from the Camel - Users mailing list archive at Nabble.com.



--
Claus Ibsen
-
http://davsclaus.com  @davsclaus
Camel in Action 2: https://www.manning.com/ibsen2 



If you reply to this email, your message will 

Re: A simple Web Service consumer and producer using Apache Camel

[Claus Ibsen]

Take a look at the Camel in Action book it has a chapter covering
using SOAP web services.

Also you questions is not so Camel related as its about CXF, so you
can ask on their user forum about those tools about wsdl2java etc.

On Thu, Mar 23, 2017 at 11:17 AM, anirban.gupta4
 wrote:
> Hi,
>
> I am new to JBoss Fuse and Apache Camel. In our project we have twoo WSDL of
> producer and consumer. For one of the WSDL we have generated the
> implementation class and we want to expose the endpoints in POJO dataFormat.
> We have couple of questions here:
>
> 1. In wsdl2java, we find three types of generating Java codes, Client Side
> code, Server side code and Implementation code. What are the differences
> between those?
> 2. can I use some other tool like wsimport (not wsdl2java) and generate the
> java classes and start from there, or we only need to use Apache CXF's
> wsdl2java for generating the implementation classs?
>
> Any other sugessions for this type of project will be helpful.
>
> Regards,
> Anirban.
>
>
>
>
> --
> View this message in context: 
> http://camel.465427.n5.nabble.com/A-simple-Web-Service-consumer-and-producer-using-Apache-Camel-tp5796012.html
> Sent from the Camel - Users mailing list archive at Nabble.com.



-- 
Claus Ibsen
-
http://davsclaus.com @davsclaus
Camel in Action 2: https://www.manning.com/ibsen2

Re: A simple Web Service consumer and producer using Apache Camel

[anirban.gupta4]

I am using Spring boot with Apache Camel and not JBoss Fuse.



--
View this message in context: 
http://camel.465427.n5.nabble.com/A-simple-Web-Service-consumer-and-producer-using-Apache-Camel-tp5796012p5796018.html
Sent from the Camel - Users mailing list archive at Nabble.com.

Re: A simple Web Service consumer and producer using Apache Camel

[anirban.gupta4]

Actually I am not using JBoss Fuse, I am using Spring Boot with Apache Camel,
but even in case of JBoss Fuse, Apache Camel is the same.



--
View this message in context: 
http://camel.465427.n5.nabble.com/A-simple-Web-Service-consumer-and-producer-using-Apache-Camel-tp5796012p5796016.html
Sent from the Camel - Users mailing list archive at Nabble.com.

Re: A simple Web Service consumer and producer using Apache Camel

[Andrea Cosentino]

Once again if you're using JBoss Fuse, please use RH support. --Andrea 
Cosentino --Apache Camel PMC MemberApache Karaf 
CommitterApache Servicemix CommitterEmail: ancosen1985@yahoo.comTwitter: 
@oscerd2Github: oscerd 

On Thursday, March 23, 2017 11:24 AM, anirban.gupta4 
 wrote:
 

 Hi,
 
I am new to JBoss Fuse and Apache Camel. In our project we have twoo WSDL of
producer and consumer. For one of the WSDL we have generated the
implementation class and we want to expose the endpoints in POJO dataFormat.
We have couple of questions here:
 
1. In wsdl2java, we find three types of generating Java codes, Client Side
code, Server side code and Implementation code. What are the differences
between those?
2. can I use some other tool like wsimport (not wsdl2java) and generate the
java classes and start from there, or we only need to use Apache CXF's
wsdl2java for generating the implementation classs?
 
Any other sugessions for this type of project will be helpful.
 
Regards,
Anirban.




--
View this message in context: 
http://camel.465427.n5.nabble.com/A-simple-Web-Service-consumer-and-producer-using-Apache-Camel-tp5796012.html
Sent from the Camel - Users mailing list archive at Nabble.com.


   

A simple Web Service consumer and producer using Apache Camel

[anirban.gupta4]

Hi,
 
I am new to JBoss Fuse and Apache Camel. In our project we have twoo WSDL of
producer and consumer. For one of the WSDL we have generated the
implementation class and we want to expose the endpoints in POJO dataFormat.
We have couple of questions here:
 
1. In wsdl2java, we find three types of generating Java codes, Client Side
code, Server side code and Implementation code. What are the differences
between those?
2. can I use some other tool like wsimport (not wsdl2java) and generate the
java classes and start from there, or we only need to use Apache CXF's
wsdl2java for generating the implementation classs?
 
Any other sugessions for this type of project will be helpful.
 
Regards,
Anirban.




--
View this message in context: 
http://camel.465427.n5.nabble.com/A-simple-Web-Service-consumer-and-producer-using-Apache-Camel-tp5796012.html
Sent from the Camel - Users mailing list archive at Nabble.com.

Re: A simple Web Service consumer and producer using Apache Camel

[souciance]

Hello,

If you are using JBoss Fuse please use the Fuse forum for that.

Best
Souciance

On Thu, Mar 23, 2017 at 11:17 AM, anirban.gupta4 [via Camel] <
ml-node+s465427n5796012...@n5.nabble.com> wrote:

> Hi,
>
> I am new to JBoss Fuse and Apache Camel. In our project we have twoo WSDL
> of producer and consumer. For one of the WSDL we have generated the
> implementation class and we want to expose the endpoints in POJO
> dataFormat. We have couple of questions here:
>
> 1. In wsdl2java, we find three types of generating Java codes, Client Side
> code, Server side code and Implementation code. What are the differences
> between those?
> 2. can I use some other tool like wsimport (not wsdl2java) and generate
> the java classes and start from there, or we only need to use Apache CXF's
> wsdl2java for generating the implementation classs?
>
> Any other sugessions for this type of project will be helpful.
>
> Regards,
> Anirban.
>
>
> --
> If you reply to this email, your message will be added to the discussion
> below:
> http://camel.465427.n5.nabble.com/A-simple-Web-Service-
> consumer-and-producer-using-Apache-Camel-tp5796012.html
> To start a new topic under Camel - Users, email
> ml-node+s465427n465428...@n5.nabble.com
> To unsubscribe from Camel - Users, click here
> 
> .
> NAML
> 
>




--
View this message in context: 
http://camel.465427.n5.nabble.com/A-simple-Web-Service-consumer-and-producer-using-Apache-Camel-tp5796012p5796014.html
Sent from the Camel - Users mailing list archive at Nabble.com.

Re: Unable to update httpclientconfigurer instance on dynamic to endpoint.

[Zoran Regvart]

Hi Abhishek,
try setting the `Exchange.HTTP_PATH` header, something like:

from("direct:a").setHeader(Exchange.HTTP_PATH,
simple("${headers.id}").to("http4://localhost8080/user/?httpClientConfigurer=myHttpConfigClient")

zoran

On Wed, Mar 22, 2017 at 11:23 PM, Abhishek.Jha09  wrote:
> Hi all,
>
> Subject pretty much sums up my query. I have a route like
>
>from("direct:a").routeId("myroute")
>
> .toD("http4://localhost:8080/user/${headers.id}?httpClientConfigurer=myHttpConfigClient")
>
> I have set up "myHttpConfigClient" in SimpleRegistry in camel context. When
> I change the config values of this instance and add the route again to camel
> context, the config parameters don't change. However, if I do the same in a
> route created like below, without dynamic to, it works perfectly fine.
>
>from("direct:a").routeId("myroute")
>
> .to("http4://localhost:8080/user?httpClientConfigurer=myHttpConfigClient")
>
> Can anyone please help me with this?
>
>
>
> --
> View this message in context: 
> http://camel.465427.n5.nabble.com/Unable-to-update-httpclientconfigurer-instance-on-dynamic-to-endpoint-tp5795918.html
> Sent from the Camel - Users mailing list archive at Nabble.com.



-- 
Zoran Regvart

Re: camelContext not found in karaf 4.1.0

[achi1955]

Hi,

now  I get:

Error executing command: Unable to resolve root: missing requirement [root] 
osgi.identity; osgi.identity=camel-spring-dm; type=karaf.feature; 
version="[2.18.3,2.18.3]"; 
filter:="(&(osgi.identity=camel-spring-dm)(type=karaf.feature)(version>=2.18.3)(version<=2.18.3))"
 [caused by: Unable to resolve camel-spring-dm/2.18.3: missing requirement 
[camel-spring-dm/2.18.3] osgi.identity; osgi.identity=spring-dm; 
type=karaf.feature; version="[1.2.0,2.0.0)"]


probably something is missing, I installed feature: spring, camel-spring
but as a tried camel-spring-dm I've got the message from above 


Plamen

> On 23 Mar 2017, at 09:40, Claus Ibsen-2 [via Camel] 
>  wrote:
> 
> That is in Camel 2.18 onwards 
> https://github.com/apache/camel/blob/camel-2.18.x/platforms/karaf/features/src/main/resources/features.xml#L71
>  
> 
> 
> But mind Karaf 4.1.x is not officially supported for Camel. Its a new 
> release and it changed a fair amount of stuff that can break stuff. 
> Use it with caution. 
> 
> On Thu, Mar 23, 2017 at 9:23 AM, achi1955 <[hidden email] 
> > wrote:
> 
> > Hi 
> > 
> > it says: 
> > 
> > Error executing command: No matching features for camel-spring-dm/0.0.0 
> > 
> > achi1955 
> > Plamen Traianov 
> > 
> > 
> >> On 23 Mar 2017, at 09:12, Claus Ibsen-2 [via Camel] <[hidden email] 
> >> > wrote: 
> >> 
> >> Try install camel-spring-dm feature 
> >> 
> >> On Thu, Mar 23, 2017 at 8:35 AM, achi1955 <[hidden email] 
> >> > wrote: 
> >> 
> >> > I am working for years with Camel and Karaf on RaspberyPi without 
> >> > problems. 
> >> > Last version I used is Karaf 4.0.8 and Camel 2.17.2. I installed my 
> >> > bundle 
> >> > into Karaf 4.1.0 and there was no reaction - no error messages , but no 
> >> > reaction on my camelContext (META-INF/spring/camel-context.xml). I did 
> >> > not 
> >> > found feature spring-dm, but it was not possible to install. 
> >> > 
> >> > Are there any changes by by deployment or is there something to install 
> >> > additionaly? 
> >> > please help 
> >> > 
> >> > 
> >> > 
> >> > -- 
> >> > View this message in context: 
> >> > http://camel.465427.n5.nabble.com/camelContext-not-found-in-karaf-4-1-0-tp5795994.html
> >> >  
> >> > 
> >> >  
> >> >  >> >  
> >> > >
> >> >  
> >> > Sent from the Camel - Users mailing list archive at Nabble.com. 
> >> 
> >> 
> >> 
> >> -- 
> >> Claus Ibsen 
> >> - 
> >> http://davsclaus.com   >> > @davsclaus 
> >> Camel in Action 2: https://www.manning.com/ibsen2 
> >>   >> > 
> >> 
> >> 
> >> If you reply to this email, your message will be added to the discussion 
> >> below: 
> >> http://camel.465427.n5.nabble.com/camelContext-not-found-in-karaf-4-1-0-tp5795994p5795996.html
> >>  
> >> 
> >>  
> >>  >>  
> >> >
> >>  
> >> To unsubscribe from camelContext not found in karaf 4.1.0, click here < 
> >> NAML < 
> >> http://camel.465427.n5.nabble.com/template/NamlServlet.jtp?macro=macro_viewer=instant_html%21nabble%3Aemail.naml=nabble.naml.namespaces.BasicNamespace-nabble.view.web.template.NabbleNamespace-nabble.view.web.template.NodeNamespace=notify_subscribers%21nabble%3Aemail.naml-instant_emails%21nabble%3Aemail.naml-send_instant_email%21nabble%3Aemail.naml
> >>  
> >> >
> >>  
> > 
> > 
> > 
> > 
> > -- 
> > View this message in context: 
> > http://camel.465427.n5.nabble.com/camelContext-not-found-in-karaf-4-1-0-tp5795994p5795997.html
> >  
> > 
> > Sent from the Camel - Users mailing list archive at Nabble.com.
> 
> 
> 
> -- 
> Claus Ibsen 
> - 
> http://davsclaus.com  @davsclaus 
> Camel in Action 2: https://www.manning.com/ibsen2 
> 
> 
> 

Re: camelContext not found in karaf 4.1.0

[Claus Ibsen]

That is in Camel 2.18 onwards
https://github.com/apache/camel/blob/camel-2.18.x/platforms/karaf/features/src/main/resources/features.xml#L71

But mind Karaf 4.1.x is not officially supported for Camel. Its a new
release and it changed a fair amount of stuff that can break stuff.
Use it with caution.

On Thu, Mar 23, 2017 at 9:23 AM, achi1955  wrote:
> Hi
>
> it says:
>
> Error executing command: No matching features for camel-spring-dm/0.0.0
>
> achi1955
> Plamen Traianov
>
>
>> On 23 Mar 2017, at 09:12, Claus Ibsen-2 [via Camel] 
>>  wrote:
>>
>> Try install camel-spring-dm feature
>>
>> On Thu, Mar 23, 2017 at 8:35 AM, achi1955 <[hidden email] 
>> > wrote:
>>
>> > I am working for years with Camel and Karaf on RaspberyPi without problems.
>> > Last version I used is Karaf 4.0.8 and Camel 2.17.2. I installed my bundle
>> > into Karaf 4.1.0 and there was no reaction - no error messages , but no
>> > reaction on my camelContext (META-INF/spring/camel-context.xml). I did not
>> > found feature spring-dm, but it was not possible to install.
>> >
>> > Are there any changes by by deployment or is there something to install
>> > additionaly?
>> > please help
>> >
>> >
>> >
>> > --
>> > View this message in context: 
>> > http://camel.465427.n5.nabble.com/camelContext-not-found-in-karaf-4-1-0-tp5795994.html
>> >  
>> > 
>> > Sent from the Camel - Users mailing list archive at Nabble.com.
>>
>>
>>
>> --
>> Claus Ibsen
>> -
>> http://davsclaus.com  @davsclaus
>> Camel in Action 2: https://www.manning.com/ibsen2 
>> 
>>
>>
>> If you reply to this email, your message will be added to the discussion 
>> below:
>> http://camel.465427.n5.nabble.com/camelContext-not-found-in-karaf-4-1-0-tp5795994p5795996.html
>>  
>> 
>> To unsubscribe from camelContext not found in karaf 4.1.0, click here 
>> .
>> NAML 
>> 
>
>
>
>
> --
> View this message in context: 
> http://camel.465427.n5.nabble.com/camelContext-not-found-in-karaf-4-1-0-tp5795994p5795997.html
> Sent from the Camel - Users mailing list archive at Nabble.com.



-- 
Claus Ibsen
-
http://davsclaus.com @davsclaus
Camel in Action 2: https://www.manning.com/ibsen2

Re: Exception handling with Hystrix EIP

[Abhishek.Jha09]

Hi Priyanka,

So, as it happens, the exceptions captured by hystrix are present as a
property of the exchange if fallback is defined otherwise, you can get it
directly from exchange. Try peeking inside exchange.getProperties() and
after you trigger the route and exchange.getException().

FYI, here's the logs generated in my case-


09:39| INFO | CamelLogger.java 159 | Before call to endpoint
09:39| INFO | CamelLogger.java 159 | Slow processing start: hystrix-my-key-1
{CamelMessageHistory=[DefaultMessageHistory[routeId=route1, node=hystrix1],
DefaultMessageHistory[routeId=route1, node=log1],
DefaultMessageHistory[routeId=route1, node=to1],
DefaultMessageHistory[routeId=route2, node=log4],
DefaultMessageHistory[routeId=route2, node=delay1]],
CamelCorrelationId=***, CamelCreatedTimestamp=,
CamelRouteStop=true, CamelToEndpoint=direct://slow}
com.netflix.hystrix.exception.HystrixRuntimeException: hystrix1 timed-out
and no fallback available.




--
View this message in context: 
http://camel.465427.n5.nabble.com/Exception-handling-with-Hystrix-EIP-tp5795811p5795991.html
Sent from the Camel - Users mailing list archive at Nabble.com.

Re: camelContext not found in karaf 4.1.0

[achi1955]

Hi

it says:

Error executing command: No matching features for camel-spring-dm/0.0.0

achi1955
Plamen Traianov


> On 23 Mar 2017, at 09:12, Claus Ibsen-2 [via Camel] 
>  wrote:
> 
> Try install camel-spring-dm feature 
> 
> On Thu, Mar 23, 2017 at 8:35 AM, achi1955 <[hidden email] 
> > wrote:
> 
> > I am working for years with Camel and Karaf on RaspberyPi without problems. 
> > Last version I used is Karaf 4.0.8 and Camel 2.17.2. I installed my bundle 
> > into Karaf 4.1.0 and there was no reaction - no error messages , but no 
> > reaction on my camelContext (META-INF/spring/camel-context.xml). I did not 
> > found feature spring-dm, but it was not possible to install. 
> > 
> > Are there any changes by by deployment or is there something to install 
> > additionaly? 
> > please help 
> > 
> > 
> > 
> > -- 
> > View this message in context: 
> > http://camel.465427.n5.nabble.com/camelContext-not-found-in-karaf-4-1-0-tp5795994.html
> >  
> > 
> > Sent from the Camel - Users mailing list archive at Nabble.com.
> 
> 
> 
> -- 
> Claus Ibsen 
> - 
> http://davsclaus.com  @davsclaus 
> Camel in Action 2: https://www.manning.com/ibsen2 
> 
> 
> 
> If you reply to this email, your message will be added to the discussion 
> below:
> http://camel.465427.n5.nabble.com/camelContext-not-found-in-karaf-4-1-0-tp5795994p5795996.html
>  
> 
> To unsubscribe from camelContext not found in karaf 4.1.0, click here 
> .
> NAML 
> 




--
View this message in context: 
http://camel.465427.n5.nabble.com/camelContext-not-found-in-karaf-4-1-0-tp5795994p5795997.html
Sent from the Camel - Users mailing list archive at Nabble.com.

Re: camelContext not found in karaf 4.1.0

[Claus Ibsen]

Try install camel-spring-dm feature

On Thu, Mar 23, 2017 at 8:35 AM, achi1955  wrote:
> I am working for years with Camel and Karaf on RaspberyPi without problems.
> Last version I used is Karaf 4.0.8 and Camel 2.17.2. I installed my bundle
> into Karaf 4.1.0 and there was no reaction - no error messages , but no
> reaction on my camelContext (META-INF/spring/camel-context.xml). I did not
> found feature spring-dm, but it was not possible to install.
>
> Are there any changes by by deployment or is there something to install
> additionaly?
> please help
>
>
>
> --
> View this message in context: 
> http://camel.465427.n5.nabble.com/camelContext-not-found-in-karaf-4-1-0-tp5795994.html
> Sent from the Camel - Users mailing list archive at Nabble.com.



-- 
Claus Ibsen
-
http://davsclaus.com @davsclaus
Camel in Action 2: https://www.manning.com/ibsen2

Unable to update httpclientconfigurer instance on dynamic to endpoint.

[Abhishek.Jha09]

Hi all,

Subject pretty much sums up my query. I have a route like

   from("direct:a").routeId("myroute")
   
.toD("http4://localhost:8080/user/${headers.id}?httpClientConfigurer=myHttpConfigClient")

I have set up "myHttpConfigClient" in SimpleRegistry in camel context. When
I change the config values of this instance and add the route again to camel
context, the config parameters don't change. However, if I do the same in a
route created like below, without dynamic to, it works perfectly fine.

   from("direct:a").routeId("myroute")
   
.to("http4://localhost:8080/user?httpClientConfigurer=myHttpConfigClient")

Can anyone please help me with this?



--
View this message in context: 
http://camel.465427.n5.nabble.com/Unable-to-update-httpclientconfigurer-instance-on-dynamic-to-endpoint-tp5795918.html
Sent from the Camel - Users mailing list archive at Nabble.com.

camelContext not found in karaf 4.1.0

[achi1955]

I am working for years with Camel and Karaf on RaspberyPi without problems.
Last version I used is Karaf 4.0.8 and Camel 2.17.2. I installed my bundle
into Karaf 4.1.0 and there was no reaction - no error messages , but no
reaction on my camelContext (META-INF/spring/camel-context.xml). I did not
found feature spring-dm, but it was not possible to install.

Are there any changes by by deployment or is there something to install
additionaly?
please help



--
View this message in context: 
http://camel.465427.n5.nabble.com/camelContext-not-found-in-karaf-4-1-0-tp5795994.html
Sent from the Camel - Users mailing list archive at Nabble.com.