Return-Path: Delivered-To: apmail-xml-axis-dev-archive@xml.apache.org Received: (qmail 20450 invoked by uid 500); 10 Apr 2002 18:08:05 -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 20403 invoked from network); 10 Apr 2002 18:08:05 -0000 Importance: Normal Sensitivity: Subject: Skeleton vs deploy.wsdd for metadata To: axis-dev@xml.apache.org X-Mailer: Lotus Notes Release 5.0.7 March 21, 2001 Message-ID: From: "Russell Butek" Date: Wed, 10 Apr 2002 13:01:17 -0500 X-MIMETrack: Serialize by Router on D04NM203/04/M/IBM(Release 5.0.9a |January 7, 2002) at 04/10/2002 02:08:08 PM MIME-Version: 1.0 Content-type: text/plain; charset=us-ascii X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N Hey, Glen! I THOUGHT we agreed that: 1. If we don't generate the skel, the metadata is in deploy.wsdd 2. If we generate the skel, the metadata is in the skel and NOT in the deploy.wsdd. Take a look at build/working/test/wsdl/sequence. This test follows #2. It has a skeleton which has metadata which you can get by calling getOperationDescByName. But the deploy.wsdd ALSO has the metadata. What's worse, there is NO CODE in the runtime that calls getOperationDescByName!!! So the metadata ALWAYS comes from the deploy.wsdd. Russell Butek butek@us.ibm.com