[
http://jira.codehaus.org/browse/XFIRE-441?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_86893
]
Christian Schneider commented on XFIRE-441:
-------------------------------------------
We had an issue with the correlation id when xfire is the client and tibco bw
is the server in soap/jms.
Xfire generates a correlation id and sends it to the server. Tibco processes
the request but then sets the correlation id for the reply to the message id of
the request. Xfire will then ignore the reply as it wants its own correlation
id back.
As we cannot change the behavior of tibco bw I would like to have a property in
xfire to make it behave compatible to tibco. What do you think? Is there an
easy fix for that?
> Support JMS correlation IDs in JMSChannel
> -----------------------------------------
>
> Key: XFIRE-441
> URL: http://jira.codehaus.org/browse/XFIRE-441
> Project: XFire
> Issue Type: New Feature
> Reporter: Brice Ruth
> Assigned To: Adam Kramer
>
> Here's a patch to JMSChannel to support JMS correlation Ids, if present. A
> correlation Id is used to tie a request to a response, which is important for
> what XFire is using JMS to do.
> Index: JMSChannel.java
> ===================================================================
> RCS file: /src/org/codehaus/xfire/transport/jms/JMSChannel.java,v
> retrieving revision 1.1
> diff -r1.1 JMSChannel.java
> 34a35
> > public static final String CORRELATION_ID = "jms.correlationId";
> 102a104,105
> > byte[] correlationId = (byte[])
> > context.getProperty(CORRELATION_ID);
> >
> 105a109
> > jmsMessage.setJMSCorrelationIDAsBytes(correlationId);
> 128a133
> > context.setProperty(CORRELATION_ID,
> > message.getJMSCorrelationIDAsBytes());
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe from this list please visit:
http://xircles.codehaus.org/manage_email
