On 11 October 2017 at 09:46, Matthias Hanisch
wrote:
> Hi,
>
> let me explain a similar use case what we would use to show that there is a
> demand for modification of application properties:
>
> We would like to enrich an AMQP message with additional application
>
That's weird. I tried the link from your previous email too and it gave me
a 404 as well. However, it's working now. It must have been a GitHub
hiccup or something.
Justin
On Wed, Oct 11, 2017 at 11:14 AM, Clebert Suconic wrote:
> Just opened and it works for me
Just opened and it works for me
https://github.com/apache/activemq-artemis/pull/1584
On Wed, Oct 11, 2017 at 12:02 PM Harrison Tarr
wrote:
> Clebert,
>
> That PR URL gives me a 404.
>
> Harrison
>
> -Original Message-
> From: Clebert Suconic
Clebert,
That PR URL gives me a 404.
Harrison
-Original Message-
From: Clebert Suconic [mailto:clebert.suco...@gmail.com]
Sent: Wednesday, October 11, 2017 9:00 AM
To: users@activemq.apache.org
Subject: Re: How to put "properties" on a message so they are accessible later
What
What Harryson said matches my PR.. you you would need to call the
method reencode. .otherwise you won't receive the messages.. and it
wouldn't be persisted.
On Wed, Oct 11, 2017 at 11:58 AM, Clebert Suconic
wrote:
> Please look at the pull request.. I believe it would
Please look at the pull request.. I believe it would fix help you:
https://github.com/apache/activemq-artemis/pull/1584
On Wed, Oct 11, 2017 at 11:58 AM, Clebert Suconic
wrote:
> You would be able to call reencode on the message.
>
> there was an issue that if you
Hi Matthias,
I ended up coming up with a "solution". It does prevent me from consuming using
AMQP. What I do is send the message to the broker using AMQP but then I
retrieve the message using the Core protocol. I'll include my snippet of code
that does the modification to the AMQP message.
You would be able to call reencode on the message.
there was an issue that if you didn't have a property, the
applicationProperties wouldn't be set..
I added an example, and fixed that issue here:
https://github.com/apache/activemq-artemis/pull/1584
Notice you would need to do the else part
Hi,
let me explain a similar use case what we would use to show that there is a
demand for modification of application properties:
We would like to enrich an AMQP message with additional application
properties for better filtering and message routing.
As far as I understood from the discussion
We could add a new method call to the plugin... something like replaceMessage.
With that on hand you could then convert the AMQPMessage to a Core
Message using message.toCore().. and return the transformed message.
The message wouldn't be an AMQP message any longer from that point
on.. it would
On 10/10/2017 05:20 PM, Harrison Tarr wrote:
Thanks for the quick reply. Is there any way to change something on the message
that my consumer could then access? Maybe not ApplicationProperties but
something else?
Nothing that would be accessible via the JMS client API.
Harrison
Thanks for the quick reply. Is there any way to change something on the message
that my consumer could then access? Maybe not ApplicationProperties but
something else?
Harrison
-Original Message-
From: Timothy Bish [mailto:tabish...@gmail.com]
Sent: Tuesday, October 10, 2017 2:11 PM
On 10/10/2017 05:06 PM, Harrison Tarr wrote:
Hello again,
I wanted to follow up on this as I've done some more experimenting. I've found that when I use the
Core protocol or Openwire protocol, everything works as expected. I am able to use the
"setStringProperty" in my ActiveMQServerPlugin
Hello again,
I wanted to follow up on this as I've done some more experimenting. I've found
that when I use the Core protocol or Openwire protocol, everything works as
expected. I am able to use the "setStringProperty" in my ActiveMQServerPlugin
and it adds a header that I can then access in
I'm not terribly familiar with the ActiveMQServerPlugin functionality in
this regard, but I do know that you can make such modifications to messages
using remoting interceptors. Have you explored that possibility?
Justin
On Tue, Sep 12, 2017 at 3:45 PM, Harrison Tarr
Right now I'm using Artemis 2.2.0.
I've done a bit more research and experimentation. It seems that I can set a
header in Camel, send the message to a queue/topic hosted on Artemis and read
the header as a "stringProperty". The header keys also show up when I do a
"getProperties" call.
To be clear, you're asking about doing this in Artemis, not ActiveMQ 5.x,
right? What version of Artemis?
On Sep 11, 2017 2:48 PM, "Harrison Tarr" wrote:
> I just wanted to follow up: Does anyone know how to put an
> attribute/property on a message in an
I just wanted to follow up: Does anyone know how to put an attribute/property
on a message in an ActiveMQServerPlugin that I can then pull out of the message
in Camel?
Regards,
Harrison Tarr
-Original Message-
From: Harrison Tarr [mailto:harrison.t...@connexta.com]
Sent: Wednesday,
Hi,
I'm trying to put a StringProperty on a Message in an ActiveMQServerPlugin. As
far as I can tell, the property gets set correctly. Later, I'm trying to
retrieve the property from a Camel Exchange. I don't see my property anywhere
on the Exchange. I did notice that it looks like the
19 matches
Mail list logo