Jetspeed 2
  1. Jetspeed 2
  2. JS2-1093

To use #parse() velocity macro can cause unexpected behavior with Velocity 1.5


    • Type: Bug Bug
    • Status: Closed
    • Priority: Major Major
    • Resolution: Fixed
    • Affects Version/s: 2.2.0
    • Fix Version/s: 2.2.1
    • Component/s: Admin Portlets, Layout
    • Labels:


      I think it hasn't been a good practice to use "#parse" macro in header.vm to use velocity macros with Velocity 1.5.
      In the documentation of Velocity 1.5, it says, "because the #parse() happens at runtime, and the parser decides if a VM-looking element in the template is a VM at parsetime, #parse()-ing a set of VM declarations won't work as expected. To get around this, simply use the velocimacro.library facility to have Velocity load your VMs at startup." [1] By the way, we cannot use velocitymacro.library facility because each layout decorator should be able to have each own macros.
      Luckily, by the way, Velocity 1.6 seems to have already resolved this problem!
      It says, "Yes! This became possible in Velocity 1.6." in the same section. [2]

      Therefore, I'd like to try to upgrade the velocity version to 1.6.3.



        Woonsan Ko created issue -
        Woonsan Ko made changes -
        Field Original Value New Value
        Status Open [ 1 ] Resolved [ 5 ]
        Resolution Fixed [ 1 ]
        Ate Douma made changes -
        Status Resolved [ 5 ] Closed [ 6 ]
        Transition Time In Source Status Execution Times Last Executer Last Execution Date
        Open Open Resolved Resolved
        19h 36m 1 Woonsan Ko 06/Jan/10 14:18
        Resolved Resolved Closed Closed
        636d 6h 45m 1 Ate Douma 04/Oct/11 21:04


          • Assignee:
            Woonsan Ko
            Woonsan Ko
          • Votes:
            0 Vote for this issue
            0 Start watching this issue


            • Created: