Return-Path: Delivered-To: apmail-ws-axis-dev-archive@www.apache.org Received: (qmail 5052 invoked from network); 6 Aug 2004 14:54:14 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur-2.apache.org with SMTP; 6 Aug 2004 14:54:14 -0000 Received: (qmail 16157 invoked by uid 500); 6 Aug 2004 14:54:08 -0000 Delivered-To: apmail-ws-axis-dev-archive@ws.apache.org Received: (qmail 16006 invoked by uid 500); 6 Aug 2004 14:54:05 -0000 Mailing-List: contact axis-dev-help@ws.apache.org; run by ezmlm Precedence: bulk Reply-To: axis-dev@ws.apache.org list-help: list-unsubscribe: list-post: Delivered-To: mailing list axis-dev@ws.apache.org Received: (qmail 15995 invoked by uid 99); 6 Aug 2004 14:54:05 -0000 X-ASF-Spam-Status: No, hits=1.5 required=10.0 tests=DNS_FROM_RFC_POST X-Spam-Check-By: apache.org Received: from [64.4.35.185] (HELO hotmail.com) (64.4.35.185) by apache.org (qpsmtpd/0.27.1) with ESMTP; Fri, 06 Aug 2004 07:54:03 -0700 Received: from mail pickup service by hotmail.com with Microsoft SMTPSVC; Fri, 6 Aug 2004 07:53:03 -0700 Received: from 128.240.229.65 by bay12-dav11.bay12.hotmail.com with DAV; Fri, 06 Aug 2004 14:53:03 +0000 X-Originating-IP: [128.240.229.65] X-Originating-Email: [iasandcb@hotmail.com] X-Sender: iasandcb@hotmail.com From: "Ias" To: Subject: An approach to publishing your WSDL Date: Fri, 6 Aug 2004 15:53:01 +0100 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Mailer: Microsoft Office Outlook, Build 11.0.5510 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1441 Thread-Index: AcR7xRIAoUW0PxqmR4m/9s2bblngGQ== Message-ID: X-OriginalArrivalTime: 06 Aug 2004 14:53:03.0332 (UTC) FILETIME=[13271A40:01C47BC5] X-Virus-Checked: Checked X-Spam-Rating: minotaur-2.apache.org 1.6.2 0/1000/N There have been issues on publishing WSDLs, especially, in case that you start your service from a given WSDL and then WSDL2Java. The main problem is when you attempt to access the WSDL through the URL of the service with "?WSDL" suffix, the dynamic auto-generation of the WSDL based on its Java code may fail. Here I'd like to recommend "one" way to avoid the trouble. If you have a WSDL file, you can just simply use explained at http://ws.apache.org/axis/java/reference.html within your WSDD description. Probably you need to override binding and service part of the WSDL file to keep up with the actual deployment environment. This way can also help you to interoperate between Axis and .NET because your original WSDL is uniformly exported from Axis without worrying about roundtrippability of WSDL->Java->WSDL. One more thing: it's just my personal opinion, but if you really want to be free from many holes of standalone JAX-RPC 1.1, think about using J2EE 1.4 web services empowered by EWS (JSR-109), in particular, regarding assembling and deploying your services. You don't need to use EJBs for that, just common Java classes are OK. (They are considered as another kind of servlets :-) Regards, Ias