Velocity
  1. Velocity
  2. VELOCITY-277

macros in #parsed files are not refreshed when including page is refreshed

    Details

    • Type: Improvement Improvement
    • Status: Resolved
    • Priority: Critical Critical
    • Resolution: Fixed
    • Affects Version/s: 1.4
    • Fix Version/s: 1.6
    • Component/s: Engine
    • Labels:
      None
    • Environment:
      Operating System: other
      Platform: Other

      Description

      If a template #parses a file containing velocimacros, changes those macros do
      not make it into the including template. This is true whether the file is
      included via the library property or via #parse.

      Although there is the velocimacro.library.autoreload property, it is "not for
      use in production" according to the documentation - and cannot be used with
      template caching.

      Also, often, macros included via #parse do not pick up their macros the first
      time they are compiiled. And with template caching they are only ever called
      once, this leads to situations where changes in templates that include macros
      and are cached do not function in production.

        Issue Links

          Activity

          Tim White created issue -
          Jeff Turner made changes -
          Field Original Value New Value
          issue.field.bugzillaimportkey 29959 12315147
          Will Glass-Husain made changes -
          Fix Version/s 1.5 [ 12310253 ]
          Bugzilla Id 29959
          Assignee Velocity-Dev List [ velocity-dev@jakarta.apache.org ]
          Environment Operating System: other
          Platform: Other
          Operating System: other
          Platform: Other
          Description If a template #parses a file containing velocimacros, changes those macros do
          not make it into the including template. This is true whether the file is
          included via the library property or via #parse.

          Although there is the velocimacro.library.autoreload property, it is "not for
          use in production" according to the documentation - and cannot be used with
          template caching.

          Also, often, macros included via #parse do not pick up their macros the first
          time they are compiiled. And with template caching they are only ever called
          once, this leads to situations where changes in templates that include macros
          and are cached do not function in production.
          If a template #parses a file containing velocimacros, changes those macros do
          not make it into the including template. This is true whether the file is
          included via the library property or via #parse.

          Although there is the velocimacro.library.autoreload property, it is "not for
          use in production" according to the documentation - and cannot be used with
          template caching.

          Also, often, macros included via #parse do not pick up their macros the first
          time they are compiiled. And with template caching they are only ever called
          once, this leads to situations where changes in templates that include macros
          and are cached do not function in production.
          Will Glass-Husain made changes -
          Link This issue duplicates VELOCITY-362 [ VELOCITY-362 ]
          Will Glass-Husain made changes -
          Fix Version/s 1.6 [ 12310290 ]
          Bugzilla Id 29959
          Type Bug [ 1 ] Improvement [ 4 ]
          Fix Version/s 1.5 [ 12310253 ]
          Henning Schmiedehausen made changes -
          Component/s Engine [ 12311337 ]
          Component/s Build [ 12310212 ]
          Bugzilla Id 29959
          Henning Schmiedehausen made changes -
          Resolution Duplicate [ 3 ]
          Status Open [ 1 ] Resolved [ 5 ]
          Will Glass-Husain made changes -
          Resolution Duplicate [ 3 ]
          Status Resolved [ 5 ] Reopened [ 4 ]
          Will Glass-Husain made changes -
          Status Reopened [ 4 ] Resolved [ 5 ]
          Resolution Fixed [ 1 ]
          Mark Thomas made changes -
          Workflow jira [ 12325152 ] Default workflow, editable Closed status [ 12551792 ]
          Mark Thomas made changes -
          Workflow Default workflow, editable Closed status [ 12551792 ] jira [ 12552615 ]

            People

            • Assignee:
              Unassigned
              Reporter:
              Tim White
            • Votes:
              2 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved:

                Development