You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Radu Cotescu (JIRA)" <ji...@apache.org> on 2019/01/09 12:11:00 UTC
[jira] [Assigned] (SLING-8205) Stop using Class.getField() in order
to avoid throwing NoSuchFieldException
[ https://issues.apache.org/jira/browse/SLING-8205?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Radu Cotescu reassigned SLING-8205:
-----------------------------------
Assignee: Radu Cotescu (was: Nicolas Peltier)
> Stop using Class.getField() in order to avoid throwing NoSuchFieldException
> ---------------------------------------------------------------------------
>
> Key: SLING-8205
> URL: https://issues.apache.org/jira/browse/SLING-8205
> Project: Sling
> Issue Type: Improvement
> Components: Scripting
> Affects Versions: Scripting HTL Runtime 1.0.0-1.4.0
> Reporter: Nicolas Peltier
> Assignee: Radu Cotescu
> Priority: Major
> Fix For: Scripting HTL Runtime 1.0.2-1.4.0
>
> Time Spent: 1h 10m
> Remaining Estimate: 0h
>
> According to java mission control, exceptions are bad for performances, and o.a.s.scripting.sightly.compiler.util.ObjectModel uses Class.getField first to check if a use member is a simple field or a method, which generates *lots* of exceptions.
> Switching to simple lookup through getFields (that looks also to super classes fields) _looks_ quicker (this of course would need to be thoroughly tested)
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)