pID: \IBM\MQ\bin64\MQExplorer.exe
> JMSXDeliveryCount: 1
> JMSXUserID: Test
> JMS_IBM_Character_Set: UTF-8
> JMS_IBM_Encoding: 546
> JMS_IBM_Format: MQSTR
> JMS_IBM_MsgType: 8
> JMS_IBM_PutApplType: 11
> JMS_IBM_PutDate: 20200107
> JMS_IBM_PutTi
Hi Claus,
Thank for the input, i manage to resolve it by adding namespace after the xpath.
Namespaces test = new Namespaces("com", "http://test.com/test";);
from("direct:...").setProperty(xpath("//com:param1/text()").namespaces(test))
Thanks and Regards,
Chio Chuan
On Tue, Jan 7, 20
Gotcha.
The Velocity template like ..
name=${body.lastName}
did the trick.
When the JSON changes like
[{"lastName": "Doo"}]
(normally jsonpath wraps the output into an array)
then the Velocity template needs to look like ..
name=${body[0].lastName}
Thanks for any help.
Best
- Gerald
>
Thanks Mantas.
I tried it out, my route is ..
..
{"lastName": "Doo"}
My Velocity template is ..
name=${lastName}
But I'm still missing the glue between the Java Map and the reference within
the Velocity template. Tried something but nothing was successful yet.
Any hints are appre
What do you mean by CiA1 or 2 book ?
Camel in Action ?
On Sat, Dec 7, 2019 at 8:56 PM Claus Ibsen wrote:
> Hi
>
> If you have the CiA1 or 2 book then the algorithm is covered there in
> much details.
>
> But you also provided a link to the docs that kinda explains it.
> The bean has 1 public me
Thanks.
On Sat, Dec 7, 2019 at 8:56 PM Claus Ibsen wrote:
> Hi
>
> If you have the CiA1 or 2 book then the algorithm is covered there in
> much details.
>
> But you also provided a link to the docs that kinda explains it.
> The bean has 1 public method so it will be used.
>
>
> On Sat, Dec 7, 20
Test
JMS_IBM_Character_Set: UTF-8
JMS_IBM_Encoding: 546
JMS_IBM_Format: MQSTR
JMS_IBM_MsgType: 8
JMS_IBM_PutApplType: 11
JMS_IBM_PutDate: 20200107
JMS_IBM_PutTime: 14241063
Test Message
In fact the body content should print only "Test Message"
Appreciate any input on the same.
Thanks
Ravi
Not necessarily. Unmarshal EIP can be configured to unmarshal into a map.
Check out https://camel.apache.org/manual/latest/json.html as well as the
signature of DataFormatClause#json
On Tue, Jan 7, 2020, 15:09 Gerald Kallas wrote:
> Tx, Mantas.
>
> Neverthless that still means to transfer the JS
Tx, Mantas.
Neverthless that still means to transfer the JSON into a (pre-defined) POJO in
front of Velocity processing. I wonder if there is any other way to access a
JSON object directly from the Velocity engine.
Best
- Gerald
> Mantas Gridinas hat am 7. Januar 2020 um 12:51
> geschrieben:
Might want to read up on Velocity user guide, then
https://velocity.apache.org/engine/2.1/user-guide.html#property-lookup-rules
On Tue, Jan 7, 2020 at 1:48 PM Gerald Kallas - mailbox.org
wrote:
>
> Tx for the reply. I tried this already, but the question still remains how to
> access the single
Tx for the reply. I tried this already, but the question still remains how to
access the single attributes of the JSON tree inside Velocity component.
Best
- Gerald
Am 07.01.2020 um 12:45 schrieb Mantas Gridinas :
>
> Why not use unmarshall EIP before passing the body to velocity
> template? T
Why not use unmarshall EIP before passing the body to velocity
template? Then, as per the velocity component, you would access your
body via $body variable.
On Mon, Jan 6, 2020 at 3:19 PM Alex Dettinger wrote:
>
> Hi Gerald,
>
> The example below shows how to use a pojo from a velocity context:
Thats is the hard method. And I am shy to use plain programming in a framework.
Regarding split:
the problem is that is not a simple spilt.
1. Zip is splitted to XML, TIFF0, TIFF1,
2. XML is splitted to DATA0, DATA1,
And TIFF0 and DATA0, (TIFF1, DATA1), ... is combined then. So aggr
Hi
You can set it to noop=true, and then delete/move it from after
aggregator in a custom bean/processor
On Tue, Jan 7, 2020 at 10:04 AM wrote:
>
> >The aggregator is a 2 phased EIP so what comes out of the aggregator is not
> >tied to the input. That is by design.
>
> Is there a way to prevent
>The aggregator is a 2 phased EIP so what comes out of the aggregator is not
>tied to the input. That is by design.
Is there a way to prevent or control the transation, when original input (file)
is deleted/moved?
-Ursprüngliche Nachricht-
Von: Claus Ibsen
Gesendet: Montag, 6. Janua
15 matches
Mail list logo
