Return-Path: Delivered-To: apmail-xml-axis-dev-archive@xml.apache.org Received: (qmail 69422 invoked by uid 500); 4 Jan 2002 20:40:26 -0000 Mailing-List: contact axis-dev-help@xml.apache.org; run by ezmlm Precedence: bulk Reply-To: axis-dev@xml.apache.org list-help: list-unsubscribe: list-post: Delivered-To: mailing list axis-dev@xml.apache.org Received: (qmail 69413 invoked from network); 4 Jan 2002 20:40:25 -0000 Message-ID: <4BC270C6AB8AD411AD0B00B0D0493DF0010C4CDF@RIKER> From: Tom Boulos To: "'axis-dev@xml.apache.org'" Subject: wsdl generation problems. Date: Fri, 4 Jan 2002 12:37:49 -0800 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-Type: text/plain; charset="iso-8859-1" X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N I have a couple of issues on the wsdl generated stubs: 1. I am using wsdl generated stubs on the client end, with http basic authorization on the server. It appears that the generated ...SoapBindingStub has a hashtable for properties, but it is never set into the call properties when a call is made. When I do it by hand in the code, setting MessageContext.USERID and MessageContext.PASSWORD in the call properties, the authorization header is generated fine, but if I use the _setProperty method on the generated stub class, it is not passed through. (As a sidenote, is it anticipated that I must always cast the interface to the implementation class in order to pass authentication data into the call?) 2. When I bind message parts to soap headers in the wsdl file, the generated code continues to look for (in the case of output) or place (in the case of input) those parts in the soap body. What is the plan in fixing these issues? Thank you, Tom Boulos Grand Central Communications http://www.grandcentral.com