[
https://issues.apache.org/jira/browse/SLING-5753?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15308322#comment-15308322
]
Jordan Shurmer commented on SLING-5753:
---------------------------------------
I see. So the concern is that developers would assume that the calling of the
init() method is part of the Models stuff in general and try to use their "use"
models in other contexts... I can understand that concern.
However, should that stop sightly from doing this? If a developer understand
the Use API and choose to use it they seem to be keen on using that object in
Sightly only... whether it's a Sling Model or not... the fact that they then
want to use Sling Models as well is separate from that. In other words, I view
this as being about the Use API supporting Sling Models, rather than Sling
Models supporting the Use API...
> 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)
