[
http://jira.codehaus.org/browse/XFIRE-943?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_101473
]
Walter Seymore commented on XFIRE-943:
--------------------------------------
I fixed this by replacing the line:
Client contextClient = context.getClient();
with
Client contextClient = correlator.correlate(context,
invocations).getContext().getClient();
in Client. This does not seem to do any harm, but it works just as well for me
if I use
Client contextClient = this;
but since it must have been changed for a reason, I guess the first option is
the better one.
Could somebody please review this and make it (or a better fix) available in
the next release since the JMS transport does not work at all without it.
Thanks
Walter
> Client does not work with JMS in 1.2.5
> --------------------------------------
>
> Key: XFIRE-943
> URL: http://jira.codehaus.org/browse/XFIRE-943
> Project: XFire
> Issue Type: Sub-task
> Affects Versions: 1.2.5
> Reporter: Tom Lambrechts
> Assignee: Dan Diephouse
>
> The fix of XFIRE-270 breaks the use of the Client with asynchrone channels. A
> nullpointer is throw when recieving a reply.
> When using an asynchrone channel a new messageContext is created and the
> client is not set on the messageContext because at that moment the client is
> not know yet.
> It is only after the CorrolatorHandler that the client is known. (Warning: at
> the moment the CorrolatorHandler does not copy the client from old to new
> context)
--
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
