Mailing-List: contact ace-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: ace-dev@incubator.apache.org
Date: Thu, 25 Aug 2011 13:34:29 +0000 (UTC)
From: "Bram de Kruijff (JIRA)" <jira@apache.org>
To: ace-dev@incubator.apache.org
Message-ID: 
 <359729610.13539.1314279269178.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Created] (ACE-174) Configuration artifacts can not be
 updated due to infinite cache
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

Configuration artifacts can not be updated due to infinite cache
----------------------------------------------------------------

                 Key: ACE-174
                 URL: https://issues.apache.org/jira/browse/ACE-174
             Project: Ace
          Issue Type: Bug
    Affects Versions: 0.8.0
            Reporter: Bram de Kruijff


updating (or even drop/create) configuration artifacts is not being propagated to targets. This is caused by the fact that the VelocityArtifactPreprocessor internally caches the bytes indefinitely (at least  tight to the  onfiguration helper service lifecycle) using the configuration artifact's url as the key. As a result checks on "needsNewVersion"will typically result in false. Furthermore, please note that the cache implementation is a  threat to memory resources as no weak references are being used.

http://www.mail-archive.com/ace-dev@incubator.apache.org/msg01345.html

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira