axis-java-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Rich Scheuerle (JIRA)" <j...@apache.org>
Subject [jira] Resolved: (AXIS2-3169) JAX-WS: Fix to AsyncResponse to ensure that the returned object is unmarshalled before reporting it as available
Date Wed, 05 Sep 2007 21:11:34 GMT

     [ https://issues.apache.org/jira/browse/AXIS2-3169?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Rich Scheuerle resolved AXIS2-3169.
-----------------------------------

    Resolution: Fixed

Committed changes: 573057

> JAX-WS: Fix to AsyncResponse to ensure that the returned object is unmarshalled before
reporting it as available
> ----------------------------------------------------------------------------------------------------------------
>
>                 Key: AXIS2-3169
>                 URL: https://issues.apache.org/jira/browse/AXIS2-3169
>             Project: Axis 2.0 (Axis2)
>          Issue Type: Bug
>            Reporter: Rich Scheuerle
>            Assignee: Rich Scheuerle
>
> This issue was discovered by Nicholas Gallardo. I am checking in his fix.
> Problem:
> The calls to CountdownLatch.countdown() within AsyncResponse are happening a little prematurely,
> such that they report the response is available before it is actually there.
> Solution:
> Wait until the unmarshalling of the object is done before reporting the response as available.
 This is done 
> by moving the countdown() calls after the unmarshalling code.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


---------------------------------------------------------------------
To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org


Mime
View raw message