You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@click.apache.org by "Bob Schellink (JIRA)" <ji...@apache.org> on 2009/11/25 05:16:39 UTC

[jira] Created: (CLK-597) Update to unreleased Velocity 1.6.3 to fix performance issue

Update to unreleased Velocity 1.6.3 to fix performance issue
------------------------------------------------------------

                 Key: CLK-597
                 URL: https://issues.apache.org/jira/browse/CLK-597
             Project: Click
          Issue Type: Bug
          Components: core
    Affects Versions: 2.1.0 RC1
            Reporter: Bob Schellink
            Assignee: Bob Schellink
             Fix For: 2.1.0


A recent issue was raised against Velocity 1.6.2 which invokes the variable toString method when checking if a variable exists or not.

Thus the following snippet would invoke the Table's toString method twice:

  #if ($table)
    $table
  #end

This can have quite a large impact on performance. This issue[1] was recently solved in Velocity by introducing a runtime property that sets behavior back to the old default.

However Velocity 1.6.2 is not released yet but we can switch to the unreleased 1.6.3 in the meantime.

[1]:https://issues.apache.org/jira/browse/VELOCITY-731

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Updated: (CLK-597) Update to Velocity 1.6.3 to fix performance issue

Posted by "Bob Schellink (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/CLK-597?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Bob Schellink updated CLK-597:
------------------------------

    Summary: Update to Velocity 1.6.3 to fix performance issue  (was: Update to unreleased Velocity 1.6.3 to fix performance issue)

Velocity 1.6.3 has been released.

> Update to Velocity 1.6.3 to fix performance issue
> -------------------------------------------------
>
>                 Key: CLK-597
>                 URL: https://issues.apache.org/jira/browse/CLK-597
>             Project: Click
>          Issue Type: Bug
>          Components: core
>    Affects Versions: 2.1.0 RC1
>            Reporter: Bob Schellink
>            Assignee: Bob Schellink
>             Fix For: 2.1.0
>
>
> A recent issue was raised against Velocity 1.6.2 which invokes the variable toString method when checking if a variable exists or not.
> Thus the following snippet would invoke the Table's toString method twice:
>   #if ($table)
>     $table
>   #end
> This can have quite a large impact on performance. This issue[1] was recently solved in Velocity by introducing a runtime property that sets behavior back to the old default.
> However Velocity 1.6.2 is not released yet but we can switch to the unreleased 1.6.3 in the meantime.
> [1]:https://issues.apache.org/jira/browse/VELOCITY-731

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Closed: (CLK-597) Update to Velocity 1.6.3 to fix performance issue

Posted by "Bob Schellink (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/CLK-597?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Bob Schellink closed CLK-597.
-----------------------------

    Resolution: Fixed

fixed in trunk

> Update to Velocity 1.6.3 to fix performance issue
> -------------------------------------------------
>
>                 Key: CLK-597
>                 URL: https://issues.apache.org/jira/browse/CLK-597
>             Project: Click
>          Issue Type: Bug
>          Components: core
>    Affects Versions: 2.1.0 RC1
>            Reporter: Bob Schellink
>            Assignee: Bob Schellink
>             Fix For: 2.1.0
>
>
> A recent issue was raised against Velocity 1.6.2 which invokes the variable toString method when checking if a variable exists or not.
> Thus the following snippet would invoke the Table's toString method twice:
>   #if ($table)
>     $table
>   #end
> This can have quite a large impact on performance. This issue[1] was recently solved in Velocity by introducing a runtime property that sets behavior back to the old default.
> However Velocity 1.6.2 is not released yet but we can switch to the unreleased 1.6.3 in the meantime.
> [1]:https://issues.apache.org/jira/browse/VELOCITY-731

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Commented: (CLK-597) Update to unreleased Velocity 1.6.3 to fix performance issue

Posted by "Bob Schellink (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/CLK-597?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12789052#action_12789052 ] 

Bob Schellink commented on CLK-597:
-----------------------------------

Just tested with the Velocity 1.6.3 snapshot[1] and its working great.

[1]: http://people.apache.org/~nbubna/velocity/engine/1.6.3/

> Update to unreleased Velocity 1.6.3 to fix performance issue
> ------------------------------------------------------------
>
>                 Key: CLK-597
>                 URL: https://issues.apache.org/jira/browse/CLK-597
>             Project: Click
>          Issue Type: Bug
>          Components: core
>    Affects Versions: 2.1.0 RC1
>            Reporter: Bob Schellink
>            Assignee: Bob Schellink
>             Fix For: 2.1.0
>
>
> A recent issue was raised against Velocity 1.6.2 which invokes the variable toString method when checking if a variable exists or not.
> Thus the following snippet would invoke the Table's toString method twice:
>   #if ($table)
>     $table
>   #end
> This can have quite a large impact on performance. This issue[1] was recently solved in Velocity by introducing a runtime property that sets behavior back to the old default.
> However Velocity 1.6.2 is not released yet but we can switch to the unreleased 1.6.3 in the meantime.
> [1]:https://issues.apache.org/jira/browse/VELOCITY-731

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.