Hi
Will do, thanks again for the quick help!
Cheers,
- Joery
On 19 Feb 2018 15:39 +0100, Claus Ibsen , wrote:
> Hi
>
> Thanks so what we can see its that you end up with camel-jms thread
> attempting to load the class which it cannot do
>
> I logged a ticket
> https://issues.apache.org/jira/bro
Hi
Thanks so what we can see its that you end up with camel-jms thread
attempting to load the class which it cannot do
I logged a ticket
https://issues.apache.org/jira/browse/CAMEL-12278
You are welcome to test the SNAPSHOT build for either master or the
2.20.x branch (you can build it yourself,
Hi,
These loggings showed up on installation:
15:03:49.890 INFO [Blueprint Event Dispatcher: 1] Attempting to start Camel
Context ID_5a86a27cc6d58e7b5e01
15:03:49.891 INFO [Blueprint Event Dispatcher: 1] Apache Camel 2.20.1
(CamelContext: ID_5a86a27cc6d58e7b5e01) is starting
15:03:49.92
Hi
Maybe OSGi classloading is wonderful
Can you turn on DEBUG/TRACE logging at org.apache.camel.jsonpath.JsonPathEngine
And see what the logs say
On Mon, Feb 19, 2018 at 2:41 PM, Joery Vreijsen wrote:
> Hi Claus,
>
> After successfully creating my flow in the Java DSL i was now moving it
> a
Hi Claus,
After successfully creating my flow in the Java DSL i was now moving it across
to the Spring DSL running in Karaf.
However i kept running into the issue that the JacksonJsonAdapter wasn’t found
on my class path.
When i manually exported the
org.apache.camel.jsonpath.jackson.JacksonJs
Hi
Thanks for sharing its a jackson issue. Maybe you could try with
2.9.10 version and see how it works there.
On Sun, Feb 18, 2018 at 11:50 PM, Joery Vreijsen wrote:
> Hi,
>
> Just posting my final findings to this.
> My issue was caused by the fact i was using Jackson 2.9.4 which logged:
> Ca
Hi,
Just posting my final findings to this.
My issue was caused by the fact i was using Jackson 2.9.4 which logged: Cannot
writeAsString as adapter cannot be initialized.
When downgrading to 2.8.10 the writeAsString option worked perfectly,
outputting a valid Json string, rather than the Map toS
Hi
It looks like your json is invalid / not structured well. You inner
map uses duplicate ids, eg document.
If possible use a array instead, eg [ ]
See the unit test from the source code - JsonPathSplitWriteAsStringTest
On Fri, Feb 16, 2018 at 10:44 AM, Joery Vreijsen wrote:
> That indeed was m
That indeed was my thought aswell, i tried the following route:
from("file:src/data")
.split().jsonpathWriteAsString("$..document")
.setHeader(Exchange.FILE_NAME, new
SimpleExpression("${exchangeId}.json"))
.to("file:target/messages/others”);
But t
Ah okay yeah that can make sense to try to tell it to output as
String. See the writeAsString option you would need to use
https://github.com/apache/camel/blob/master/components/camel-jsonpath/src/main/docs/jsonpath-language.adoc
On Fri, Feb 16, 2018 at 10:30 AM, Joery Vreijsen wrote:
> Hi Clau
Hi Clause,
Thanks for the quick response!
When removing the String.class i get the following exception:
No body available of type: java.io.InputStream but has value: {name=document 2,
type=pdf} of type: java.util.LinkedHashMap on: Message[]. Caused by: No type
converter available to convert fr
Try without the String.class in the jsonpath
On Fri, Feb 16, 2018 at 10:22 AM, Joery Vreijsen wrote:
> Hi,
>
> I’m trying to split my following Json file with the Camel Splitter & JsonPath
> components.
>
> [
> {
> "document": {
> "name": "document 1",
> "type": "pdf"
> }
>
12 matches
Mail list logo
