Return-Path: Delivered-To: apmail-ws-axis-user-archive@www.apache.org Received: (qmail 58714 invoked from network); 28 Mar 2009 05:15:25 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 28 Mar 2009 05:15:25 -0000 Received: (qmail 7901 invoked by uid 500); 28 Mar 2009 05:15:22 -0000 Delivered-To: apmail-ws-axis-user-archive@ws.apache.org Received: (qmail 7797 invoked by uid 500); 28 Mar 2009 05:15:22 -0000 Mailing-List: contact axis-user-help@ws.apache.org; run by ezmlm Precedence: bulk Reply-To: axis-user@ws.apache.org list-help: list-unsubscribe: List-Post: List-Id: Delivered-To: mailing list axis-user@ws.apache.org Received: (qmail 7786 invoked by uid 99); 28 Mar 2009 05:15:22 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 28 Mar 2009 05:15:22 +0000 X-ASF-Spam-Status: No, hits=3.5 required=10.0 tests=SPF_PASS,URIBL_BLACK X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of sagara.gunathunga@gmail.com designates 209.85.200.174 as permitted sender) Received: from [209.85.200.174] (HELO wf-out-1314.google.com) (209.85.200.174) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 28 Mar 2009 05:15:13 +0000 Received: by wf-out-1314.google.com with SMTP id 29so1547129wff.28 for ; Fri, 27 Mar 2009 22:14:52 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:in-reply-to:references:date :received:message-id:subject:from:to:content-type :content-transfer-encoding; bh=eabJ2XCvQ2dFY6j4yLoPmsLt4B3mD20jZARKh1VJkDo=; b=UsMtCJVrrT1Q0JrUdAlZLI+gW5bcxjbkr/Mt0T7eVWVORK+8QZPXpFP/5hyGE3Bkhf 9wC2YVFYdqkzU5uHlSq1uPM4hp2upWTli3MzaSF+C3YUtMgnFsJrTiBPl8PZDtd/4g7a ACdoivxQ5qwyyT95OfNvRZUCqAcj4/zYiF7hk= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type:content-transfer-encoding; b=AAb5qKU7tDEE1bp3uol0Qg+Q0ETs+Sk+yWUeG15WLHpluI+YkQSxWtfjMkGKEbVqvE eVoPwl0H8vWf4iV7sCOM2bNOavSBiyMSJpCjtXxwRqBYfKTAdgnOljfTA8Qg1WnULPAB DIHfJv4lnzZUNsOV40cd1I1qTYlduE7JmgSzs= MIME-Version: 1.0 In-Reply-To: <23AE0D88485E4B29BC149621EFA296D3@xvargandalf> References: <23AE0D88485E4B29BC149621EFA296D3@xvargandalf> Date: Sat, 28 Mar 2009 10:44:37 +0530 Received: by 10.142.142.14 with SMTP id p14mr1194582wfd.100.1238217292333; Fri, 27 Mar 2009 22:14:52 -0700 (PDT) Message-ID: <474d01b00903272214l24cc95b4w4eb7fd7bf1bc4591@mail.gmail.com> Subject: Re: Axis2 webservice - access to existing application classes outside of axis service/repository tree From: Sagara Gunathunga To: axis-user@ws.apache.org Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org Hi , > It appears that axis2 requires you to place your webservice's source in > addition to ALL libraries or classes that that service interacts with under > > webapps/axis2/WEB-INF/services. What do you mean "webservice's source here ...? > Or is there a way to configure axis so that we do not have to deploy under > the axis2/ tree, but instead tell it where the class files that will act as > the service is located in the existing app? It seems you already running your application as a .WAR format , you can integrate Axis2 under your existing application by editing web.xml and placing required meta data files, not required to bring your existing application under the axis2/ tree. please refer [1] [1] - http://www.developer.com/open/article.php/3777111 Thanks , -- Sagara Gunathunga Blog - http://ssagara.blogspot.com Web - http://sagaras.awardspace.com/