Re: does camel support custom policy for processor level ?

ext2 wrote: Willem wrote: No, you can apply the police per processor. The new added camel-spring-security is based on this camel policy feature. how to configure such policy using spring? Or just dsl? Please check out the camel-spring-security example[1]. or .policy("xxx"). [1]https://cw

Re: does camel support custom policy for processor level ?

Thanks Willem: I got it; and using this feature I could define custom transaction range in a single route(need not separate them in different route just for transaction purpose); >>Willem wrote: >>No, you can apply the police per processor. >>The new added camel-spring-security is based on thi

Re: does camel support custom policy for processor level ?

Willem wrote: >>No, you can apply the police per processor. >>The new added camel-spring-security is based on this camel policy feature. how to configure such policy using spring? Or just dsl? Willem ext2 wrote: > Hi: > Camel policy is very useful to define some custom wrapper features; >

Re: does camel support custom policy for processor level ?

No, you can apply the police per processor. The new added camel-spring-security is based on this camel policy feature. Willem ext2 wrote: Hi: Camel policy is very useful to define some custom wrapper features; But in camel 2.2 , it seems the policy only apply on the whole route; And it

does camel support custom policy for processor level ?

Hi: Camel policy is very useful to define some custom wrapper features; But in camel 2.2 , it seems the policy only apply on the whole route; And it cannot define a policy on a special processor, is this true? And does camel 2.x support some mechanism to support define custom polic

Re: native(dll) to java callback method in Camel

Basically when camel consumer is create, it already has a processor which holds the whole route pipeline, your customer event consumer[1][2] just need to call the processor.process(exchange) when you get the event. If your under layer dll has threads to call the onMessageRecieved callback meth

Re: How to route a message to remote ActiveMQ broker(s) dynamically?

Hi, You need to turn the hashNumber into a String and put it after "activemq" instead of using it directly. I can reproduce the error by setting the component name with "123activemq", and the error is gone when I use "activemq123". Willem mdasari wrote: Thanks for the reply. In summary it wo

Re: How to route a message to remote ActiveMQ broker(s) dynamically?

Thanks for the reply. In summary it works now. I actually tried this approach before and it didn't work then but now it works due to minor change. It appears org.apache.camel.impl.DefaultComponent.createEndpoint(...) doesn't like numeric name, when I tried earlier I used numeric hash off the IP

Handle finite number of remote requests?

My application will send requests to a remote system via XML-RPC, but the remote system does not queue or throttle requests in any way -- it is fairly trivial for my application to overload the remote system and make it crash. I don't think that the throttler pattern will work for my intended usa

Re: Split Body in Spring DSL

I understand the better now, Anyways, this would really be a useful features in our case :) Claus Ibsen-2 wrote: > > Hi > > Yeah I can see the problem now. > > The language was originally designed for creating dynamic > Strings, and hence ${body} is parsed as "" + body, which cause Camel >

Re: Graceful shutdown of Camel-Jetty component. (Camel 2.2.0)

On Wed, Apr 21, 2010 at 6:30 PM, Ilya S wrote: > Hi Claus, > > Thanks again for making this work! > > I tried the latest code from trunk directly, and everything seems to > work fine with my test case/prototype. > Great to hear it works now. > Ilya. > > > > On Wed, Apr 21, 2010 at 8:47 AM, Ilya

Re: Graceful shutdown of Camel-Jetty component. (Camel 2.2.0)

Hi Claus, Thanks again for making this work! I tried the latest code from trunk directly, and everything seems to work fine with my test case/prototype. Ilya. On Wed, Apr 21, 2010 at 8:47 AM, Ilya S wrote: > Hi > > Just refreshed my 2.3-SNAPSHOT, and I'm still getting the exceptions > if I o

Re: Graceful shutdown of Camel-Jetty component. (Camel 2.2.0)

Hi Just refreshed my 2.3-SNAPSHOT, and I'm still getting the exceptions if I omit Defer option in my route. I'm going to wait some time and try again later, perhaps your changes are not in the latest snapshot yet. Thank you. Ilya. On Wed, Apr 21, 2010 at 2:10 AM, Claus Ibsen wrote: > Hi > > I

native(dll) to java callback method in Camel

Hi, I have an old java application that loads dll (native) to connect to third party vendor. This dll will synchronously invoke onMessageRecieved callback method at java side when there is an event and converts bytes to strings. I am trying to investigate if I can write custom Camel Component

Re: How implement customed transaction section in camel?

Hi This requires Camel 2.2 onwards. And check out chapter 9 in the book as it covers using multiple TX demarcations. On Wed, Apr 21, 2010 at 4:41 PM, ext2 wrote: > > Hi: >        Camel 's transaction-policy is applied for all processors in the > route;  but how to use this features to implemen

How implement customed transaction section in camel?

Hi: Camel 's transaction-policy is applied for all processors in the route; but how to use this features to implement a customized transaction section in camel? Etc: if I could assign a transaction-policy to a single pipe-line processor(not the whole route), I could define custom transact

Re: Velocity component

Hello Oliver! I think another possibility could be for you to use JAXB to unmarshal your XML document into a java bean. Then you can use the following expression in your velocity template: $body.username Please have a look on this test: http://svn.apache.org/viewvc/camel/trunk/components/camel-v

Re: Remote broker message behavior

Hi ActiveMQ also has its own error handling mechanism with Dead Letter Queues. On Tue, Apr 20, 2010 at 10:32 PM, jfaath wrote: > > I have a camel application that's using a remote ActiveMQ broker instance. > Messages come in to the application via HTTP and are sent to a "inbound" > queue using

Re: What is the usage for the spring element?

On Wed, Apr 21, 2010 at 2:04 PM, ext2 wrote: > > Hi : > > In camel 1.6x, I must use the to control transaction; but > when camel 2.2x , a new element is introduced. Is the > is just a simplified for or it provide some new > features? > Yeah it makes it simpler to use, as you dont need to mess

What is the usage for the spring element?

Hi : In camel 1.6x, I must use the to control transaction; but when camel 2.2x , a new element is introduced. Is the is just a simplified for or it provide some new features? Thanks for any suggestion

Re: Remote broker message behavior

Hi, Can we have a look at your camel route? Which version of camel are your using? You issue relates to the ErrorHandler[1], you may need to go through the wiki document for it. [1]http://camel.apache.org/error-handler.html Willem jfaath wrote: I have a camel application that's using a rem

Re: Problem with spring / camel integration

Oh, this can explain why the below error. With the camel-osgi bundle, your camel context will have trouble to lookup the type converter with the annotation in OSGi platform to the converter job. Caused by: org.apache.camel.InvalidPayloadException: No body available of type: java.io.InputStream

Re: Graceful shutdown of Camel-Jetty component. (Camel 2.2.0)

Hi I have just committed this to trunk. camel-jetty will now return 503 when shutting down. This allows you to process existing messages while new messages will be denied with 503. You can also suspend/resume the consumer from JMX console with the operations for that. It would be great if you ha