[
https://issues.apache.org/jira/browse/ACE-174?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13095180#comment-13095180
]
Marcel Offermans commented on ACE-174:
--------------------------------------
Artifacts, once created, are assumed to be immutable. If something changes,
you're supposed to create a new URL for it. For bundles this means you should
probably create file names based on its symbolic name + version, for other
types of artifacts, you should use some kind of unique name + some kind of
version number.
That does not invalidate your comment about the cache not using weak references
though, so that's something we need to look into.
> 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
