Return-Path: Delivered-To: apmail-ws-axis-dev-archive@www.apache.org Received: (qmail 24397 invoked from network); 16 Jan 2006 03:04:46 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 16 Jan 2006 03:04:46 -0000 Received: (qmail 1992 invoked by uid 500); 16 Jan 2006 03:04:45 -0000 Delivered-To: apmail-ws-axis-dev-archive@ws.apache.org Received: (qmail 1376 invoked by uid 500); 16 Jan 2006 03:04:44 -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 1365 invoked by uid 99); 16 Jan 2006 03:04:44 -0000 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests= X-Spam-Check-By: apache.org Received: from [192.87.106.226] (HELO ajax.apache.org) (192.87.106.226) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 15 Jan 2006 19:04:41 -0800 Received: from ajax.apache.org (ajax.apache.org [127.0.0.1]) by ajax.apache.org (Postfix) with ESMTP id 48B2AE1 for ; Mon, 16 Jan 2006 04:04:20 +0100 (CET) Message-ID: <1864633428.1137380660295.JavaMail.jira@ajax.apache.org> Date: Mon, 16 Jan 2006 04:04:20 +0100 (CET) From: "Juanda Zeng (JIRA)" To: axis-dev@ws.apache.org Subject: [jira] Created: (AXIS2-392) Hotupdate does not work on directories (for services deployed as directories instead of .aar files). 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 Hotupdate does not work on directories (for services deployed as directories instead of .aar files). ---------------------------------------------------------------------------------------------------- Key: AXIS2-392 URL: http://issues.apache.org/jira/browse/AXIS2-392 Project: Apache Axis 2.0 (Axis2) Type: Bug Components: deployment Versions: 0.94 Environment: Windows XP Pro, JBoss Reporter: Juanda Zeng Priority: Minor This appears to be by design. The deployment engine only checks for the lastModified() value of the directory, which may not always be updated. For example: / services/ MyService/ META-INF/ services.xml services.wsdl When services.wsdl is ADDED, the lastModified value of META-INF is updated accordingly. But the lastModified value of MyService does not change. When services.xml is updated, the lastModified values of both META-INF and MyService do not change. SUGGESTED WORKAROUND FOR USERS: ------------------------------------------------------------- After a service is updated, perform the following: File file = new File(myServiceDirectory); // eg. "services/MyService" file.setLastModified(System.currentTimeMillis()); This will force the directory to appear as having been modified. -- 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