Return-Path: 
 <axis-c-user-return-644-apmail-ws-axis-c-user-archive=ws.apache.org@ws.apache.org>
Delivered-To: apmail-ws-axis-c-user-archive@www.apache.org
Received: (qmail 39166 invoked from network); 8 Jul 2004 22:00:08 -0000
Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199)
  by minotaur-2.apache.org with SMTP; 8 Jul 2004 22:00:08 -0000
Received: (qmail 89369 invoked by uid 500); 8 Jul 2004 22:00:08 -0000
Delivered-To: apmail-ws-axis-c-user-archive@ws.apache.org
Received: (qmail 89213 invoked by uid 500); 8 Jul 2004 22:00:06 -0000
Mailing-List: contact axis-c-user-help@ws.apache.org; run by ezmlm
Precedence: bulk
list-help: <mailto:axis-c-user-help@ws.apache.org>
list-unsubscribe: <mailto:axis-c-user-unsubscribe@ws.apache.org>
list-post: <mailto:axis-c-user@ws.apache.org>
List-Id: "Apache AXIS C User List" <axis-c-user.ws.apache.org>
Reply-To: "Apache AXIS C User List" <axis-c-user@ws.apache.org>
Delivered-To: mailing list axis-c-user@ws.apache.org
Received: (qmail 89198 invoked by uid 99); 8 Jul 2004 22:00:06 -0000
X-ASF-Spam-Status: No, hits=0.0 required=10.0
	tests=
X-Spam-Check-By: apache.org
Received: from [12.39.189.66] (HELO orrtax_exchg3.orrtax.com) (12.39.189.66)
  by apache.org (qpsmtpd/0.27.1) with ESMTP; Thu, 08 Jul 2004 15:00:01 -0700
Received: by orrtax_exchg3.nls.nlsholdings.com with Internet Mail Service
 (5.5.2653.19)
	id <MRLMTQH1>; Thu, 8 Jul 2004 17:04:09 -0500
Message-ID: 
 <8343824939973D4FAC4AD93C1CF35944BCAF2B@orrtax_exchg3.nls.nlsholdings.com>
From: Robert Sanford <rsanford@trefs.com>
To: Apache AXIS C User List <axis-c-user@ws.apache.org>
Subject: RE: Odd Win32 COM Issue...
Date: Thu, 8 Jul 2004 17:04:04 -0500 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain
X-Virus-Checked: Checked
X-Spam-Rating: minotaur-2.apache.org 1.6.2 0/1000/N

And even more debugging shows me that the HTTP headers are being properly
sent over the same socket number that the SOAP message is being sent to.
That means that *something* is going over the wire but not everything is.

Once again, this works from a command-line client just not from the COM
client.

rjsjr

> -----Original Message-----
> From: Robert Sanford [mailto:rsanford@trefs.com] 
> Sent: Thursday, July 08, 2004 3:02 PM
> To: Apache AXIS C User List
> Subject: RE: Odd Win32 COM Issue...
> 
> 
> More debugging leads me to think that the "issue" with 
> m_Secure is not a code issue but is instead code readability 
> issue. When Call::Initialize is invoked the transport refers 
> to variables by name (SECURE or UNSECURE) but the checks when 
> preparing to send use the numeric representations as boolean 
> values. A value of 1 for m_Secure matches the UNSECURE enum value. 
> 
> Please accept my apologies for my confusion on this part of 
> the equation.
> 
> The rest of my confusion still remains. The call to send is 
> still failing.
> 
> rjsjr
> 
> > -----Original Message-----
> > From: Robert Sanford [mailto:rsanford@trefs.com]
> > Sent: Thursday, July 08, 2004 2:44 PM
> > To: axis-c-user@ws.apache.org
> > Subject: Odd Win32 COM Issue...
> > 
> > 
> > Okay, I have a teeny-tiny command-line app that uses the
> > AxisClient_D.dll to transmit a document to my server. It 
> > works great. So I copied the simple, simple code into a new 
> > project that instead of being a simple command-line app is a 
> > COM control. I created another simple little dialog app that 
> > will load up the COM control and invoke the functionality to 
> > transmit a document. And it fails.
> > 
> > Running through the debugger everything works up to the point that
> >    const Channel& Channel::operator << (const char* msg)
> > 
> > Is called. The msg that is being called matches what I am
> > expecting so all of the buffer information is appropriate. It 
> > is failing on the call to 
> >    if((nByteSent = send(m_Sock, msg, size, MSG_DONTROUTE )) 
> > == SOCKET_ERROR)
> > 
> > Which is failing and I don't understand why or what I should
> > be looking at in order to go further.
> > 
> > One oddity that I noted during the debug session is that the
> > HTTPTransport::m_Secure is set to 1 even though I specified 
> > HTTP and not HTTPS when initializing the protocol. I don't 
> > know where that came from. When I invoke Call:Initialize the 
> > secure flag is set to 0. I manually change m_Secure to 0 and 
> > that makes no difference in the behaviour even though the 
> > code path through the Bind is different.
> > 
> > Help?!?!
> > 
> > Many thanks!
> > 
> > rjsjr
> > 
>