Mailing-List: contact axis-c-dev-help@ws.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Apache AXIS C Developers List" <axis-c-dev@ws.apache.org>
Message-ID: <398961282.1117019751743.JavaMail.jira@ajax.apache.org>
Date: Wed, 25 May 2005 13:15:51 +0200 (CEST)
From: "Samisa Abeysinghe (JIRA)" <axis-c-dev@ws.apache.org>
To: axis-c-dev@ws.apache.org
Subject: [jira] Commented: (AXISCPP-659) Move connection opening out of
 flushOutput method
In-Reply-To: <1561522159.1116999231437.JavaMail.jira@ajax.apache.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

     [ http://issues.apache.org/jira/browse/AXISCPP-659?page=comments#action_66257 ]
     
Samisa Abeysinghe commented on AXISCPP-659:
-------------------------------------------

I think the best place where we could call Transport::openConnection is in ClientAxisEngine::invoke() method. I tried including it like the following inside invoke:

        if (AXIS_SUCCESS != (Status = m_pSZ->setOutputStream (m_pSoap)))
            break;
        
        m_pSoap->openConnection();

        m_pSZ->markEndOfStream();

So before calling markEndOfStream whuch calls Transport::flushOutput(), I open the connection. flushOutput will only other about writing to the stream, and not open the connection.


> Move connection opening out of flushOutput method
> -------------------------------------------------
>
>          Key: AXISCPP-659
>          URL: http://issues.apache.org/jira/browse/AXISCPP-659
>      Project: Axis-C++
>         Type: Improvement
>   Components: Transport (axis3)
>     Versions: 1.5 Final
>     Reporter: Samisa Abeysinghe
>     Assignee: Samisa Abeysinghe
>      Fix For: 1.6 Alpha

>
> Connection opening should not be the responsibility of the flushOutput method. Rather it has to be an independent act.
> When connection opening is within the flushOutput, it becomes harder to debug. Hence it is ideal to move this to out of flushOutput.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira