[
https://issues.apache.org/jira/browse/ONAMI-46?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13555232#comment-13555232
]
Mikhail Mazursky commented on ONAMI-46:
---------------------------------------
I can imagine that it can be some specific usecase - maybe someone needs a
Disposer that logs registrations or allows to add callbacks to be called on
disposal of specific objects. Crazy examples, but it's just an extension point
to allow to do all kinds of stuff. Also it makes sense to make DefaultDisposer
non-final class to allow for inheritance. Is that reasonable?
> Register objects for disposal from @Provides methods
> ----------------------------------------------------
>
> Key: ONAMI-46
> URL: https://issues.apache.org/jira/browse/ONAMI-46
> Project: Apache Onami
> Issue Type: Improvement
> Components: lifecycle
> Affects Versions: lifecycle-0.2.0
> Reporter: Mikhail Mazursky
> Attachments: ONAMI-46.patch
>
>
> It should be possible to register objects for disposal from @Provides
> methods. See proposed approach in patch in ONAMI-43. Is that ok to change
> classes layout like that?
> Will post a proposed patch when ONAMI-44 and ONAMI-45 applied.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
