Re: camel-cxfrs with custom http headers...

Willem, one more question. Does the same issue exist for SOAP requests as well? My team is telling me that it doesn't work for SOAP requests either. Let me know if a change is necessary there as well...thanks again - Ben O'Day IT Consultant (subcontractor for Progress) -- View this messa

Re: Camel webconsole in Karaf

I was working on adding this features, but have been unable to get it deployed properly (https://issues.apache.org/jira/browse/CAMEL-3519). If anyone has the steps to get this to work, let me know... - Ben O'Day IT Consultant -http://benoday.blogspot.com -- View this message in context: h

Re: Object routing

a few comments... from(...) is for defining camel routes (executed once on context startup from a RouteBuilder's configure() method) ProducerTemplate.sendBody(...) is for sending messages to routes already defined It appears that you are sending to a queue w/o any consumers, correct? I'm not su

Re: Using camel with xstream

I've used xstream w/o the need to define any mappings (like Jaxb requires, etc). Basically, just use xstream's fromXML()/toXML() methods to marshal from String/Java bean in your processor methods as needed. You can also define your own custom type converter classes using the convertBodyTo(MyConve

Re: Object routing

for sendBody()...you are correct in that some endpoints can be lazily created (activemq is one of them)...so this works to create an on-the-fly JMS endpoint/queue... See this unit test for basic usage of the component... https://svn.apache.org/repos/asf/camel/trunk/components/camel-jms/src/test/j

Re: processor generating multiple messages

as suggested...multiple exchanges are necessary. just use a timer to periodically kickoff the route to check the database, add results to the exchange, split the results (if desired) and send them along...something along these lines from("timer://processResults?fixedRate=true&period=1")

Re: Low Latency

I had similar concerns from a client in the past and wrote this simple unit test to get a feel for how quickly Camel can add/remove from a queue. This should give you a ballpark latency estimate (~5ms for my setup). You can also get some great AMQ performance stats via http://activemq.apache.org

Re: Camel context shutdown after route (with smpp) initialization failure

you should be able to set noAutoStartup() on the routes and then use a separate process to try to start them later peter.argalas wrote: > > Is there any option how to ignore routes (remove them from context), that > could not be started and start camel without them? > - Ben O'Day IT Consu

Re: Default Behavior for aggregate

Currently, an expression and strategy are required (or you get a DSL compilation error). Your best bet is to simply use the "constant(true)" expression to match all exchanges and the groupExchanges() strategy to simply store them all in an exchange property... from() .aggregate(constant(true)

Re: Exceptions thrown by sub-routes and their processing in main route's onException

for common exception handling, just declare it outside of route definitions to allow them to be shared by all routes/subroutes. onException(Exception.class) .handled(true) .to("direct:Z"); from("A")...to("B")...to("C"); from("B")...; from("C")...; gregoire wrote: > > So don't know if a

Re: Default Behavior for aggregate

added https://issues.apache.org/jira/browse/CAMEL-3855 CAMEL-3855 to explore this further... - Ben O'Day IT Consultant -http://benoday.blogspot.com -- View this message in context: http://camel.465427.n5.nabble.com/Default-Behavior-for-aggregate-tp4296790p4299254.html Sent from the Camel

Re: Default Behavior for aggregate

I just wanted to use an out-of-the-box strategy for a quick example. I generally create my own strategy and use the body instead. I created the JIRA issue because I think this should be a standard strategy (if not the default mode as you suggested). Here is a simple strategy to build up a List

Re: How to write a singleton producer

I don't think you want to cache the Producer or you'll loose the configuration for subsequent routes (as well as causing other issues I imagine). Instead, I'd try to use a static (thread-safe) reference to your datasource in your custom Producer class that can be shared across instances. andrew.

Re: how can i modify variable bases xpath in configure() method

use http://camel.apache.org/recipient-list.html something like this should allow you to dynamically determine the next endpoint based on the map and xpath result... replace you inline Processor and to(rcvQSRmttr) with this recipientList().method(MessageRouter.class, "routeTo") ... public class

Re: how can i get bean map property in camel

if you are using Spring to initialize the bean, you should use the bean ref/annotation approach to implement recipient list...see this example http://camel.apache.org/recipientlist-annotation.html aronftd wrote: > > i define MessageRouter in spring xml ,when i be in debug mode ,i find the > apc

Re: Using xpath in setHeader with spring DSL

hmmm, you aren't using xpath in the Java DSL, so the spring DSL should be something like this... {{cmisURL}}/p/${in.header.folderPath}children antoine.julienne wrote: > > Here is my code : > > .setHeader(Exchange.HTTP_URI, simple(cmisURL + "/p/${headers.folderPath}children")) > >

Re: xpath 2.0 function bean binding camel xpath annotation

I get the same error when running the API directly (from 2.8-SNAPSHOT)...either way, I'll look into it a bit... XPathBuilder upperCaseBuilder = XPathBuilder.xpath("upper-case(/order/status/text())"); String result = upperCaseBuilder.evaluate(context, "in progress"); org.apache.camel.builder.xml.I

Re: xpath 2.0 function bean binding camel xpath annotation

The issue is that @XPath defaults the resultType to NodeList.class. But I think you need to use String.class instead... So, try setting the resultType explicitly, like this... public void updateStatus(@XPath("/order/@customerId") Integer customerId, @XPath("orde

Re: xpath 2.0 function bean binding camel xpath annotation

added https://issues.apache.org/jira/browse/CAMEL-3911 to explore this further Claus Ibsen-2 wrote: > > Ah we should maybe try in the @XPath situation to check the parameter > type, and if possible configure the XPathBuilder to use that same > type. Then it knows when evaluating the xpath expres