Velocity
  1. Velocity
  2. VELOCITY-82

VM libs will not autoreload if unparseable at Velocity startup

    Details

    • Type: Bug Bug
    • Status: Resolved
    • Priority: Minor Minor
    • Resolution: Later
    • Affects Version/s: 1.3-rc1
    • Fix Version/s: 2.x
    • Component/s: Engine
    • Labels:
      None
    • Environment:
      Operating System: Linux
      Platform: All

      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.

        Activity

        No work has yet been logged on this issue.

          People

          • Assignee:
            Unassigned
            Reporter:
            Michael Pearson
          • Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Development