Thanks Claus, the double comma works well.
--
View this message in context:
http://camel.465427.n5.nabble.com/Simple-IN-with-empty-value-in-list-tp5790907p5790960.html
Sent from the Camel - Users mailing list archive at Nabble.com.
In the end I just used .process() before the choice, got body.stringValue in
the Java code, tested and set an exchange header "isValid" to "true" if so,
and then subsequently tested for this in simple.
I didn't use something like .choice.when.simple("${body.stringValue.isEmpty}
||
Sorry, to be clear, body.stringValue could be "", "gold", "silver", "bronze",
"platinum", etc.
I am trying to test so that only "", "gold" or "silver" are allowed before
moving forward, which is why I have the comma at the start, to allow for a
blank (not null) value:
Hi,
I'm trying to use simple to test for an empty value in a list, so something
like:
simple("${body.stringValue} in ',gold,silver'")
It doesn't seem to work though, if body.stringValue is '' this fails.
--
View this message in context:
In case anyone needs it, we used grok to achieve this:
if [path] =~ "Tracer" {
grok {
patterns_dir => ["./extra_patterns"]
match => {
"message" => "^\n%{USERNAME:id} >>>
\(%{USERNAME:routeId}\) %{GREEDYDATA:source} -->
Hi
I have the following message I'd like to unmarshal into a POJO with Bindy :
KeyABC=value1:KeyDEF=value2:
It looks like the key (i.e. tag) needs to be an int. Is there any way with
Bindy to handle this kind of format?
Thanks
--
View this message in context:
Has anyone managed to integrate Camel logs with Logstash/Elasticsearch?
I've got tracer and MDC logging enabled in my CamelContext and am sending
logs to Logstash via log4j TCP appender. This is working great (especially
MDC fields), but I'm trying to further parse and filter the message to
Hi,
When an exception is thrown and the Message History is dumped, each of the
columns appears to be truncated beyond a certain length:
Message History
---
RouteId
I believe you can just set .threads(1)
--
View this message in context:
http://camel.465427.n5.nabble.com/Disabling-concurrency-in-camel-route-tp5786531p5786535.html
Sent from the Camel - Users mailing list archive at Nabble.com.
Hi,
I have tracing enabled with http://camel.465427.n5.nabble.com/Tracer-multiline-tp5785600.html
Sent from the Camel - Users mailing list archive at Nabble.com.
I have the same issue with sql server, but it seems to be related to alias +
named param rather than a joined query.
The following works fine:
.setHeader("ExternalRef", simple("1234"))
.to("sql:select event from events where id= :#ExternalRef")
But if I alias the table :
It is possible to set up command line ssh to not require a password or file.
I can currently do this with:
uname1@server1:~$ ssh -q uname2@server2
But I can't get this to work with Camel (being run as uname1 on server1). If
I do:
.to("ssh://uname2@server2")
I get a
FYI as a workaround to this issue, I put the securityHandler in the
restConfiguration and simply added an empty route with the other handler to
my camel context:
http://localhost:8080?handlers=jettyRequestLog"/>
--
View this message in context:
Hi,
When I have my restConfiguration as follows:
When the app is starting, I'm finding the logs are as
This seems similar to https://issues.jboss.org/browse/ENTESB-2619
Also for brevity, below are the two handler beans:
Hi,
On 2.16.0, I am getting a StackOverflowError when I have multiple handlers
defined for my restConfiguration jetty component. It works with single
handlers.
This causes the following exception on startup:
2015-10-21 21:29:59,543 [main ]
Thank you! I can confirm it works very well
--
View this message in context:
http://camel.465427.n5.nabble.com/Camel-tracer-logs-in-hawtio-tp5772869p5772917.html
Sent from the Camel - Users mailing list archive at Nabble.com.
Would it work if we run Camel as a standalone app with hawtio embedded? It
should be possible for us to switch to this.
--
View this message in context:
http://camel.465427.n5.nabble.com/Camel-tracer-logs-in-hawtio-tp5772869p5772910.html
Sent from the Camel - Users mailing list archive at
Hi,
I have Camel deployed as a war in a Jetty container, along with hawtio as a
war as well.
Everything works well and as expected, but I am wondering if I can see the
Camel tracer interceptor logs in the Logs tab of hawtio.
I have tracing enabled with the usual:
Confirmed this is working fine now on Camel 2.16. Thanks!
--
View this message in context:
http://camel.465427.n5.nabble.com/Stream-Cache-spool-file-deletion-when-marshaling-to-JSON-with-Jackson-tp5769699p5772690.html
Sent from the Camel - Users mailing list archive at Nabble.com.
Our restConfiguration is as follows:
And we have Restlet simply as:
The war file sits in a Jetty 9 container.
Thanks
--
View this message in context:
Hi,
We just upgraded to Camel 2.15.3 but this issue still remains unfortunately.
Stack trace from 2.15.3 is below:
java.io.FileNotFoundException:
/tmp/camel/camel-tmp-3b981524-ca86-4989-b74e-1f5655381add/cos8487311535309884732.tmp
(No such file or directory)
at
Hi,
Using Camel version 2.15.2, I'm trying to get the Map key as the header in
the CSV file.
Consider the following body:
ListMaplt;String,String body = new ArrayListMaplt;String,String();
MapString,String map1 = new LinkedHashMapString,String();
map1.put(food, pizza);
map1.put(drink, coke);
Hi,
We're using Camel 2.15.2/Rest DSL/Restlet deployed as a war in a Jetty 9
container. Stream caching is enabled.
For one of our routes, we retrieve and transform XML to an
ArrayListMaplt;String, String and then marshal to JSON. A cleaned up
sample route is as follows:
public void configure()
Hi,
In my Rest DSL route, I use the Validate DSL and mvel to validate data as it
goes through the pipeline. If there's a validation exception, I would like
to return back to the client both an HTTP_RESPONSE_CODE 400 as well as the
reason for the error in the body. I'm able to set the HTTP
This is useful, but can we do rest dsl route level authentication with
embedded jetty?
I was only able to do this with restlet in a jetty container, following the
spring security example.
--
View this message in context:
Thanks, I have created JIRA CAMEL-8830
--
View this message in context:
http://camel.465427.n5.nabble.com/Camel-XQuery-3-0-tp5767434p5767843.html
Sent from the Camel - Users mailing list archive at Nabble.com.
In fact it looks like XQuery 3.0 isn't supported in Saxon HE 9.5. It is the
default on 9.6 but that doesn't seem compatible with the current
implementation of XQueryBuilder:
Caused by: java.lang.NoSuchMethodError:
net.sf.saxon.Configuration.setHostLanguage(I)V
at
Hi,
I would like to use the group by functionality provided with XQuery 3.0,
along with some other features.
Even though Camel 2.15.2 seems to be using Saxon 9.5.1-5 HE which supports
XQuery 3.0, I'm getting this exception:
Caused by: net.sf.saxon.trans.XPathException: 'group by' is not
29 matches
Mail list logo