Return-Path: Delivered-To: apmail-ws-axis-user-archive@www.apache.org Received: (qmail 46896 invoked from network); 15 Aug 2006 09:05:00 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 15 Aug 2006 09:05:00 -0000 Received: (qmail 38158 invoked by uid 500); 15 Aug 2006 09:04:54 -0000 Delivered-To: apmail-ws-axis-user-archive@ws.apache.org Received: (qmail 37132 invoked by uid 500); 15 Aug 2006 09:04:51 -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 37120 invoked by uid 99); 15 Aug 2006 09:04:51 -0000 Received: from asf.osuosl.org (HELO asf.osuosl.org) (140.211.166.49) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 15 Aug 2006 02:04:51 -0700 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests=HTML_MESSAGE X-Spam-Check-By: apache.org Received-SPF: pass (asf.osuosl.org: local policy) Received: from [193.26.193.89] (HELO server3.software-ag.de) (193.26.193.89) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 15 Aug 2006 02:04:50 -0700 Received: from server3.software-ag.de (localhost [127.0.0.1]) by localhost.software-ag.de (Postfix) with ESMTP id 4CDC46AAD2 for ; Tue, 15 Aug 2006 11:04:26 +0200 (CEST) Received: from DAEMSG03.eur.ad.sag (unknown [10.20.160.62]) by server3.software-ag.de (Postfix) with ESMTP id F24C76AAE2 for ; Tue, 15 Aug 2006 11:04:25 +0200 (CEST) X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C6C049.5AB6C999" Subject: [Axis2] - Bug in deployment Date: Tue, 15 Aug 2006 11:01:10 +0200 Message-ID: X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: [Axis2] - Bug in deployment thread-index: AcbASVpt1DXJ50jiQIilIATKHBPX2A== From: "Kedar, Shahar" To: X-Virus-Checked: Checked by ClamAV on apache.org X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N ------_=_NextPart_001_01C6C049.5AB6C999 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: quoted-printable Hi, =20 I think I found a bug in the Axis2 deployment mechanism. Looking at the code of org.apache.axis2.deployment.RepositoryListener, it seems that if there are no files under the services folder then Axis will not check whether existing services were removed. =20 This is what I think is happening: 1. The method that checks whether certain services were removed is checkForUndeployedServices() under the WSInfoList class. This method will check for changes only if the check boolean is set to TRUE. 2. The check boolean is set to TRUE only by the addWSInfoItem() method under the WSInfoList class. This method will be called by the RepsitoryListener only if the file list of the services directory is not empty. This means, that if I already have some service deployed, and I decide the delete all the content of the services folder, those services will remain deployed until Axis2 is restarted. =20 Any ideas how to bypass this bug (other than maintaining a dummy file under the services folder)? Should I report this bug to the Axis2 team? =20 Thanks, Shahar Kedar Software AG Israel =20 ------_=_NextPart_001_01C6C049.5AB6C999 Content-Type: text/html; charset="US-ASCII" Content-Transfer-Encoding: quoted-printable

Hi,=

 

I think I found a bug in the Axis2 deployment mechanism. Looking at the = code of org.apache.axis2.deployment.RepositoryListener, it seems that if there are no files under the services folder then Axis will not = check whether existing services were removed.

 

This is what I think is happening:

  1. The method that checks whether certain services were removed is = checkForUndeployedServices() under the WSInfoList = class. This method will check for changes only if the check boolean is set to TRUE.
  2. The check boolean is set to TRUE only by the addWSInfoItem() method under the WSInfoList class. This method will be called by the RepsitoryListener only if the file list of the services directory is not empty. This = means, that if I already have some service deployed, and I decide the delete = all the content of the services folder, those services will remain deployed = until Axis2 is restarted.

 

Any ideas how to bypass this bug (other than maintaining a dummy file under = the services folder)? Should I report this bug to the Axis2 = team?

 

Thanks,

Shahar Kedar

Software AG Israel

 

------_=_NextPart_001_01C6C049.5AB6C999--