message-id in STOMP RECEIPT FRAME

[Raoul Bhatia]

hi!

can you please shed a light on why there is no specification for
having the message-id sent back to the client in a RECEIPT FRAME?

background information:
i would like to implement a two-way-communication using the JMS
correlation-id (which is, for example, available in with apache's
activemq).

instead of generating the correlation-id in my application, the reply
message could have its correlation-id set to the last message's id.
but therefore, i would need the message-id in the RECEIPT frame that i
receive after sending my message using SEND.

maybe this could be incorporated into STOMP 1.2?

thanks,
raoul

[Peter Vojtek]

Hi all,

I have similar problem - I would like to determine message-id assigned
to the sent message. To incorporate message-id into RECEIPT frame
header would be useful.

Best,
Peter

On Dec 9 2011, 4:36 pm, Raoul Bhatia <ra...@bhatia.at> wrote:
> hi!
>
> can you please shed a light on why there is no specification for

> having themessage-idsent back to the client in aRECEIPTFRAME?

>
> background information:
> i would like to implement a two-way-communication using the JMS
> correlation-id (which is, for example, available in with apache's
> activemq).
>
> instead of generating the correlation-id in my application, the reply

> message could have its correlation-id set to the lastmessage's id.
> but therefore, i would need themessage-idin theRECEIPTframe that i

[Brian McCallister]

On Fri, Mar 9, 2012 at 7:29 AM, Peter Vojtek <peter....@gmail.com> wrote:
> Hi all,
>
> I have similar problem - I would like to determine message-id assigned
> to the sent message. To incorporate message-id into RECEIPT frame
> header would be useful.

Implementations are welcome to do this.

-Brian

[buchi]

In a relative context, why cannot we set the message-id while
publishing the message from STOMP? This is doable in ActiveMQ Java
API, though.

On Mar 9, 2:10 pm, Brian McCallister <bri...@skife.org> wrote:

[Brian McCallister]

On Sat, Mar 10, 2012 at 4:10 AM, buchi <buchi....@gmail.com> wrote:
> In a relative context, why cannot we set the message-id while
> publishing the message from STOMP? This is doable in ActiveMQ Java
> API, though.

If it makes sense to allow specifying the message id against a JMS
broker, then the JMS broker is welcome to expose that functionality. I
know there has a been a lot of discussion about standardizing
JMS-centric extensions to stomp, but I don't know of anything formal
that has occured. I know ActiveMQ exposes various JMS bits through
headers as documented at http://activemq.apache.org/stomp.html

-Brian