[
http://jira.codehaus.org/browse/XFIRE-943?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_101317
]
Walter Seymore commented on XFIRE-943:
--------------------------------------
I came across the same NPE and just used "this" instance's XFire instead and I
couldn't get it to break with an http transport (The JMS transport fails as the
timeout is too short when firing tens of messages in multiple threads). What is
the purpose of using context.getClient()?
> 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
