Discussion:
[openjms-developer] [ openjms-Bugs-667586 ] Non-number message ID
SourceForge.net
2005-12-02 13:20:00 UTC
Permalink
Bugs item #667586, was opened at 2003-01-14 16:42
Message generated for change (Comment added) made by tanderson
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=474136&aid=667586&group_id=54559

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: specification
Group: v0.7.3.2
Status: Closed
Resolution: Fixed
Priority: 5
Submitted By: Oh Jiung (ohju)
Assigned to: Tim Anderson (tanderson)
Summary: Non-number message ID

Initial Comment:
Openjms accepts only number-format message IDs,
and throws JMSException otherwise.
This breaks JORAM test testJMSMessageID_1:

setJMSMessageID("ID:foo")


----------------------------------------------------------------------
Comment By: Tim Anderson (tanderson)
Date: 2005-12-03 00:19

Message:
Logged In: YES
user_id=557161

Fixed some time ago, for release 0.7.5.

----------------------------------------------------------------------

Comment By: Tim Anderson (tanderson)
Date: 2003-01-14 23:23

Message:
Logged In: YES
user_id=557161

Strictly speaking, OpenJMS can reject this as
JMSMessageIDs are provider specific, and ID:foo is not a
valid OpenJMS message identifier.

It is however not compliant in that it doesn't conform to
section 3.4 of the specification:
" When a message is sent, JMSMessageID is ignored.
When the send method returns it contains a provider-
assigned value."


----------------------------------------------------------------------

You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=474136&aid=667586&group_id=54559
Loading...