[jira] [Updated] (SLING-8205) Stop using Class.getField() in order to avoid throwing NoSuchFieldException

["Radu Cotescu (JIRA)" <ji...@apache.org>]

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

Radu Cotescu updated SLING-8205:
--------------------------------
    Summary: Stop using Class.getField() in order to avoid throwing NoSuchFieldException  (was: stop using Class.getField() to stop spitting out NoSuchFieldException)

> 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
>            Reporter: Nicolas Peltier
>            Assignee: Nicolas Peltier
>            Priority: Major
>          Time Spent: 1h
>  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)