[ https://issues.apache.org/jira/browse/SLING-5753?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15366344#comment-15366344 ]
Radu Cotescu commented on SLING-5753: ------------------------------------- I have to agree with Justin's comment \[0\]: implementing this enhancement will lead to inconsistency regarding Sling Models instantiation depending on the consumer. Since anything that can be performed in {{Use#init(javax.script.Bindings)}} can be accomplished through injection annotations and / or {{@PostConstruct}} I don't see a compelling reason for applying the attached patch. \[0\] - https://issues.apache.org/jira/browse/SLING-5753?focusedCommentId=15308307&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-15308307 > Use.init() not invoked for Java Use object which is also a Sling Model > ---------------------------------------------------------------------- > > Key: SLING-5753 > URL: https://issues.apache.org/jira/browse/SLING-5753 > Project: Sling > Issue Type: Bug > Components: Scripting > Affects Versions: Scripting Sightly Models Use Provider 1.0.0 > Reporter: Levente Santha > Priority: Minor > Attachments: SLING_5753.patch > > > [~kwin], > In the situation where I start with a Java Use object and later decide to use > some convenient features of Sling Models, I have the surprise to experience > that as soon as my Java Use object gets the @Model annotation its init() > method is not invoked any more. > I can see no good reason for this, so I created a patch to fix it. > Please let me know what you think. > Thank you, Levente -- This message was sent by Atlassian JIRA (v6.3.4#6332)