You are viewing a plain text version of this content. The canonical link for it is here.
Posted to java-dev@axis.apache.org by "Andreas Veithen (JIRA)" <ji...@apache.org> on 2009/06/18 16:21:07 UTC

[jira] Updated: (AXIS2-4395) JAX-WS: Consistent code across the invoke apis

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

Andreas Veithen updated AXIS2-4395:
-----------------------------------

    Fix Version/s: 1.6

> JAX-WS: Consistent code across the invoke apis
> ----------------------------------------------
>
>                 Key: AXIS2-4395
>                 URL: https://issues.apache.org/jira/browse/AXIS2-4395
>             Project: Axis 2.0 (Axis2)
>          Issue Type: Bug
>          Components: jaxws
>            Reporter: Rich Scheuerle
>            Assignee: Rich Scheuerle
>             Fix For: 1.6
>
>   Original Estimate: 2h
>  Remaining Estimate: 2h
>
> Problem:
> There are five different client invoke entry points into the web service engine.  
> Four are in BaseDispatch:
>   - synchronous invoke
>   - invokeOneWay
>   - invokeAsync (Future)
>   - invokeAsync (Callback)
> And one in JAXWSProxyhanderl
>   -invokeSEIMethod
> There have been several bug fixes/improvements over the past year where developers have added code to one or more of these methods
> and neglected the same change in the other methods.  The most recent example is some session managrment (changes).
> Solution:
> Scrub the code to look for any other obvious mistakes.  Add comments to assist developers when changing the code.  Add debug statements as necessary.
> Next Actions:
> Paul Mariduena has completed this work in his sandbox.  I am working on committing the code to Apache.

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