Return-Path: Delivered-To: apmail-ws-axis-dev-archive@www.apache.org Received: (qmail 95081 invoked from network); 4 May 2006 13:38:04 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 4 May 2006 13:38:04 -0000 Received: (qmail 54180 invoked by uid 500); 4 May 2006 13:37:52 -0000 Delivered-To: apmail-ws-axis-dev-archive@ws.apache.org Received: (qmail 54142 invoked by uid 500); 4 May 2006 13:37:52 -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: List-Id: Delivered-To: mailing list axis-dev@ws.apache.org Received: (qmail 54131 invoked by uid 99); 4 May 2006 13:37:52 -0000 Received: from asf.osuosl.org (HELO asf.osuosl.org) (140.211.166.49) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 04 May 2006 06:37:52 -0700 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests= X-Spam-Check-By: apache.org Received: from [209.237.227.198] (HELO brutus.apache.org) (209.237.227.198) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 04 May 2006 06:37:51 -0700 Received: from brutus (localhost [127.0.0.1]) by brutus.apache.org (Postfix) with ESMTP id ADFBA7142AE for ; Thu, 4 May 2006 13:37:17 +0000 (GMT) Message-ID: <6921182.1146749837710.JavaMail.jira@brutus> Date: Thu, 4 May 2006 13:37:17 +0000 (GMT+00:00) From: "Thilo Frotscher (JIRA)" To: axis-dev@ws.apache.org Subject: [jira] Commented: (AXIS2-663) WSDL2Java: allow user to specify separate destination folders for src and resources In-Reply-To: <23073338.1146708497052.JavaMail.jira@brutus> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N [ http://issues.apache.org/jira/browse/AXIS2-663?page=comments#action_12377806 ] Thilo Frotscher commented on AXIS2-663: --------------------------------------- Exactly that's the problem...that WSDL2Java generates code with only a single service in mind. The problem arises, when you have to use WSDL2Java more than once in the same project. It happens quite often that you want to implement more than one service in the same project (or clients for more than one service in the same project). In this case, you would run WSDL2Java several times, and then the generated files overwrite each other. That's why it would be great to have the ability to separate the results of multiple WSDL2Java calls from each other. > WSDL2Java: allow user to specify separate destination folders for src and resources > ----------------------------------------------------------------------------------- > > Key: AXIS2-663 > URL: http://issues.apache.org/jira/browse/AXIS2-663 > Project: Apache Axis 2.0 (Axis2) > Type: Improvement > Components: Tools > Versions: 1.0 > Environment: Axis2 1.0 RC5 > Reporter: Thilo Frotscher > > WSDL2Java generates source code, resources (service.xml, wsdl, xsd) and a build.xml file. > The user can specify a destination folder for all of these files, but they all go into the same folder. > When generating code for more than one service, you'll generally want to have the source code for all services in the same src-folder. > That's why you would specify the same destination folder for all services. However, in this causes the problem that the build.xml files > and the resources for all the services go into the same folder as well and interfere with each other, or a overwritten respectively. > Therefore, it would be great if the user could specify two separate destination folders: one for the source code and the second one for > the build file and the resources. Of course, the build files would have to reflect the new folder structure. > Alternative suggestion: WSDL2Java could do this automatically by introducing a service-specific folder > under resouces: > /resources/MyService1/service.xml > /resources/MyService1/MyService.wsdl > /resources/MyService1/MyService.xsd > /resources/MyService2/service.xml > /resources/MyService2/MyService.wsdl > /resources/MyService2/MyService.xsd > For the build files a similar solution could be used. -- 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