Mailing-List: contact axis-dev-help@ws.apache.org; run by ezmlm
Precedence: bulk
Reply-To: axis-dev@ws.apache.org
Message-ID: <1981976189.1252428958598.JavaMail.jira@brutus>
Date: Tue, 8 Sep 2009 09:55:58 -0700 (PDT)
From: "Rich Scheuerle (JIRA)" <jira@apache.org>
To: axis-dev@ws.apache.org
Subject: [jira] Closed: (AXIS2-3773) Dispatch Sync with Async Transport is
 not working
In-Reply-To: <1319465815.1209515576950.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Rich Scheuerle closed AXIS2-3773.
---------------------------------

    Resolution: Fixed

> Dispatch Sync with Async Transport is not working
> -------------------------------------------------
>
>                 Key: AXIS2-3773
>                 URL: https://issues.apache.org/jira/browse/AXIS2-3773
>             Project: Axis 2.0 (Axis2)
>          Issue Type: Bug
>          Components: jaxws
>            Reporter: Rich Scheuerle
>            Assignee: Rich Scheuerle
>
> The JAXWS Dispatch.invoke() (synchronous) api with an Async MEP is not being honored.  A synchronous MEP is being used instead.
> This issue was discovered by Martin Adams (IBM).

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