Async client not receiving method return values properly because of URI
conflict in AbstractTransport
-----------------------------------------------------------------------------------------------------
Key: XFIRE-830
URL: http://jira.codehaus.org/browse/XFIRE-830
Project: XFire
Issue Type: Bug
Components: Core
Affects Versions: 1.2.2
Environment: Not applicable.
Reporter: Daniel Tremblay
Assigned To: Dan Diephouse
When building a XFire service that is also a XFire client, the results returned
to the client were always cast to string (instead of the proper return type).
The problem lies in the AbstractTransport class, which maintains a map of
channels by URI. If the client and service URIs are the same, then there is no
way to differentiate between the two channels (actually, one gets overwritten):
the Client.mode property of the context needs to be set to TRUE for clients, in
order to read the returned value properly.
--
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
