You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@sling.apache.org by "Vlad Bailescu (JIRA)" <ji...@apache.org> on 2015/01/15 17:06:37 UTC

[jira] [Updated] (SLING-4314) The implementation of RenderContext#resolveProperty can be slow for certain cases

     [ https://issues.apache.org/jira/browse/SLING-4314?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Vlad Bailescu updated SLING-4314:
---------------------------------
    Attachment: SLING-4314_-_The_implementation_of_RenderContext_resolveProperty_can_be_slow_for_certain.patch

Added NoSuchMethodException throw in RenderContextImpl#getObjectNoArgMethod to differentiate the case when a method is not found from the one where the actual return is null.

> The implementation of RenderContext#resolveProperty can be slow for certain cases
> ---------------------------------------------------------------------------------
>
>                 Key: SLING-4314
>                 URL: https://issues.apache.org/jira/browse/SLING-4314
>             Project: Sling
>          Issue Type: Bug
>          Components: Scripting
>            Reporter: Radu Cotescu
>             Fix For: Scripting Sightly Engine 1.0.0
>
>         Attachments: SLING-4314_-_The_implementation_of_RenderContext_resolveProperty_can_be_slow_for_certain.patch
>
>
> The current implementation of {{org.apache.sling.scripting.sightly.impl.engine.runtime.RenderContextImpl#resolveProperty}} is slow when the resolved methods of an object return {{null}} due to the fact that {{getField}} is called without a real reason.
> Instead, {{getField}} should be called only when a method is not found.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)