7:56 a.m.
JMS correlation ID should not be in the message body
----------------------------------------------------
Key: JBESB-658
URL: http://jira.jboss.com/jira/browse/JBESB-658
Project: JBoss ESB
Issue Type: Task
Security Level: Public (Everyone can see)
Components: Transports
Affects Versions: 4.2 Milestone Release 2
Reporter: Mark Little
Assigned To: Mark Little
Why is it not in the context or header element?
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
6:35 a.m.
New subject: [JBoss JIRA] Assigned: (JBESB-658) JMS correlation ID should not be in the message body
[ http://jira.jboss.com/jira/browse/JBESB-658?page=all ]
Mark Little reassigned JBESB-658:
---------------------------------
Assignee: Daniel Bevenius (was: Mark Little)
I think this is now related to the work you've been doing. If not, assign it back to
me.
JMS correlation ID should not be in the message body
----------------------------------------------------
Key: JBESB-658
URL: http://jira.jboss.com/jira/browse/JBESB-658
Project: JBoss ESB
Issue Type: Task
Security Level: Public(Everyone can see)
Components: Transports
Affects Versions: 4.2 Milestone Release 2
Reporter: Mark Little
Assigned To: Daniel Bevenius
Why is it not in the context or header element?
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
9:44 a.m.
New subject: [JBoss JIRA] Commented: (JBESB-658) JMS correlation ID should not be in the message body
[ http://jira.jboss.com/jira/browse/JBESB-658?page=comments#action_12368972 ]
Mark Little commented on JBESB-658:
-----------------------------------
Just remember that RelatesTo is a URI.
JMS correlation ID should not be in the message body
----------------------------------------------------
Key: JBESB-658
URL: http://jira.jboss.com/jira/browse/JBESB-658
Project: JBoss ESB
Issue Type: Task
Security Level: Public(Everyone can see)
Components: Transports
Affects Versions: 4.2 Milestone Release 2
Reporter: Mark Little
Assigned To: Daniel Bevenius
Why is it not in the context or header element?
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
1:39 a.m.
New subject: [JBoss JIRA] Commented: (JBESB-658) JMS correlation ID should not be in the message body
[ http://jira.jboss.com/jira/browse/JBESB-658?page=comments#action_12369046 ]
Daniel Bevenius commented on JBESB-658:
---------------------------------------
Maybe the JMS expiration value should also be carried with the Message object. This might
make sence if one there is no point in delivering the message after the expiration time
has expired. In the current impl the JMS Message would be save for ever is it is
persistent.
Mark, do you have any suggestions as to where this infomation should be stored within the
Message object?
/Daniel
JMS correlation ID should not be in the message body
----------------------------------------------------
Key: JBESB-658
URL: http://jira.jboss.com/jira/browse/JBESB-658
Project: JBoss ESB
Issue Type: Task
Security Level: Public(Everyone can see)
Components: Transports
Affects Versions: 4.2 Milestone Release 2
Reporter: Mark Little
Assigned To: Daniel Bevenius
Why is it not in the context or header element?
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
8:34 a.m.
New subject: [JBoss JIRA] Commented: (JBESB-658) JMS correlation ID should not be in the message body
[ http://jira.jboss.com/jira/browse/JBESB-658?page=comments#action_12369436 ]
Mark Little commented on JBESB-658:
-----------------------------------
WS-A doesn't really have a notion of expires because that's not an attribute of
the EPR. So I'd suggest adding it within the Body (or maybe a Property)?
JMS correlation ID should not be in the message body
----------------------------------------------------
Key: JBESB-658
URL: http://jira.jboss.com/jira/browse/JBESB-658
Project: JBoss ESB
Issue Type: Task
Security Level: Public(Everyone can see)
Components: Transports
Affects Versions: 4.2 Milestone Release 2
Reporter: Mark Little
Assigned To: Daniel Bevenius
Why is it not in the context or header element?
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
3:21 p.m.
New subject: [JBoss JIRA] Work started: (JBESB-658) JMS correlation ID should not be in the message body
[ http://jira.jboss.com/jira/browse/JBESB-658?page=all ]
Work on JBESB-658 started by Daniel Bevenius.
JMS correlation ID should not be in the message body
----------------------------------------------------
Key: JBESB-658
URL: http://jira.jboss.com/jira/browse/JBESB-658
Project: JBoss ESB
Issue Type: Task
Security Level: Public(Everyone can see)
Components: Transports
Affects Versions: 4.2 Milestone Release 2
Reporter: Mark Little
Assigned To: Daniel Bevenius
Why is it not in the context or header element?
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
2:53 a.m.
New subject: [JBoss JIRA] Commented: (JBESB-658) JMS correlation ID should not be in the message body
[ http://jira.jboss.com/jira/browse/JBESB-658?page=comments#action_12370654 ]
Daniel Bevenius commented on JBESB-658:
---------------------------------------
Mark, we discussed this ealier about the URI for RelatesTo and I want to make sure I get
this right.
This is how I'm creating the URI for the correlationID :
URI correlationURI = new URI( JMSEpr.JMS_PROTOCOL, "correlationID" ,
from.getJMSCorrelationID() );
which produces an uri like this:
jms:correlationID#YYXX-123456780-GG
JMSCorrelationID is set as a fragment on the URI and can be retrieved like this:
correlationURI.getFragment();
This correlation id is not used in the ESB code base as the default behaviour is to set
outgoing JMSCorrelationID's to the ESB MessageID. But users can override this and
could then set the outgoing correlation id to the original correlation id.
And this is how the JMSMessageID is being set on the Call object instance:
to.getHeader().getCall().setMessageID( new URI( from.getJMSMessageID() ));
Does this look right to you?
Also I'm setting the JMSExpiration as a property on the ESB Message.
Thanks,
Daniel
JMS correlation ID should not be in the message body
----------------------------------------------------
Key: JBESB-658
URL: http://jira.jboss.com/jira/browse/JBESB-658
Project: JBoss ESB
Issue Type: Task
Security Level: Public(Everyone can see)
Components: Transports
Affects Versions: 4.2 Milestone Release 2
Reporter: Mark Little
Assigned To: Daniel Bevenius
Why is it not in the context or header element?
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
4 p.m.
New subject: [JBoss JIRA] Closed: (JBESB-658) JMS correlation ID should not be in the message body
[ http://jira.jboss.com/jira/browse/JBESB-658?page=all ]
Daniel Bevenius closed JBESB-658.
---------------------------------
Resolution: Done
Committed with revision 13941.
JMS correlation ID should not be in the message body
----------------------------------------------------
Key: JBESB-658
URL: http://jira.jboss.com/jira/browse/JBESB-658
Project: JBoss ESB
Issue Type: Task
Security Level: Public(Everyone can see)
Components: Transports
Affects Versions: 4.2 Milestone Release 2
Reporter: Mark Little
Assigned To: Daniel Bevenius
Why is it not in the context or header element?
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
6432
days inactive
6459
days old
7 comments
2 participants
participants (2)
-
Daniel Bevenius (JIRA) -
Mark Little (JIRA)