[
https://issues.apache.org/jira/browse/VELOCITY-731?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12745446#action_12745446
]
Byron Foster commented on VELOCITY-731:
---------------------------------------
There was a discussion about this in VELOCITY-656
In my case it comes up when using data objects where properties on the data
object are intended to be rendered, but never the object itself. In these
cases I use the toString() to dump a ton of information about the object, and
maybe any related graph of objects, which is convenient for debugging.
>From what I know this behavior is only used by velocity tools, but I don't
>know of any other use cases for it. I also run with a patched version of
>Velocity with this behavior removed.
> Velocity 1.6 performance is degraded by introduced toString() calls
> -------------------------------------------------------------------
>
> Key: VELOCITY-731
> URL: https://issues.apache.org/jira/browse/VELOCITY-731
> Project: Velocity
> Issue Type: Bug
> Components: Engine
> Affects Versions: 1.6
> Environment: Apache Velocity 1.6.2
> Reporter: Jörgen Rydenius
>
> As part of VELOCITY-531, r686428 introduced frequent calls to toString() just
> to check if toString() != null. If toString() implementations are slightly
> complex, and very frequently executed, these calls will degrade the site
> performance. Are they at all necessary? What kind of object would use null as
> a return value for toString()? Is it possible to remove these toString()
> calls from the velocity code again?
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
