[
https://issues.apache.org/jira/browse/SLING-5753?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15308301#comment-15308301
]
Jordan Shurmer commented on SLING-5753:
---------------------------------------
I'm having trouble understanding why this would be a bad idea. They only point
I can see is that a Model which also implements the Use api is less flexible,
but seeing as how this change is specifically in the Sightly scripting bundle I
don't see how that is a problem. If someone wants to have an object which is a
Model and is also ran through the Sightly Use API why shouldn't they?
I see this adding some nice functionality which help two pieces of the Sling
world work better together.
> 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)
