[VELOCITY-82] VM libs will not autoreload if unparseable at Velocity startup

• Type: Bug
• Status: Closed
• Priority: Minor
• Resolution: Later
• Affects Version/s: 1.3-rc1
• Component/s: Engine
• Environment: Operating System: Linux; Platform: All
• Bugzilla Id: 9451
• Assignee: Unassigned
• Reporter: Michael Pearson
• Created: 28/May/02 12:08
• Updated: 07/Jan/18 15:52
• Resolved: 12/Oct/06 14:38

Description

I'm using Velocity 1.3-rc1 (updated from CVS (tag TVEL_1_3_BRANCH) as at 28th of
May, 2002) on a Redhat 7.2 system, combined with velocity-tools/struts and
velocity-tools/view from latest cvs.

When a velocimacro library is loaded at initialisation time, it is normally
added to the libModMap hash in VelocimacroFactory. The libModMap hash is checked
when reloading velocimacro templates. However, if the parsing of the velocimacro
library fails midway through, the macros are added to the namespace but the
Template is not returned to VelocimacroFactory, and thus not added to libModMap.
This means that if a VM library is broken at initialization time, it will never
be reloaded until Velocity is restarted.

I have not tried this under the HEAD tagged CVS sources, as my macros refuse to
parse at all using this branch.