[
https://issues.apache.org/jira/browse/VELOCITY-850?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claude Brisson resolved VELOCITY-850.
-------------------------------------
Resolution: Fixed
Assignee: Claude Brisson
Fix Version/s: 2.1
Fixed by commit 1843883:
- Velocity now supports non-string values in the initial Properties - even if
it is strongly discouraged to put something else than strings in Properties, if
the calling code did so, better support it than fail on an NPE
- the internal ExpProperties object (cloned from ExtendedProperties) now tries
to do a better job at converting numbers
> modificationCheckInterval defaults to zero
> ------------------------------------------
>
> Key: VELOCITY-850
> URL: https://issues.apache.org/jira/browse/VELOCITY-850
> Project: Velocity
> Issue Type: Bug
> Components: Engine
> Affects Versions: 1.7
> Environment: all
> Reporter: Beat Durrer
> Assignee: Claude Brisson
> Priority: Minor
> Labels: documentation, easyfix
> Fix For: 2.1
>
>
> The base class ResourceLoader handles the loading of the
> modificationCheckInterval property. However, if the property is not present,
> or not of the correct type (long), it changes the default to zero.
> This issue is amplified by the fact, that
> ExtendedProperties#getLong(name,default) does not cast Integers to Long (But
> it accepts a String property).
> The type requirements should either be documented or the code should be
> improved to support casts from Integer to Long. Neglecting this actually
> disables cache refreshing and is hard to find for users.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@velocity.apache.org
For additional commands, e-mail: dev-h...@velocity.apache.org
