You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@deltaspike.apache.org by "Karl Kildén (JIRA)" <ji...@apache.org> on 2013/10/09 09:24:42 UTC
[jira] [Comment Edited] (DELTASPIKE-398) BeanProvider handling for
@Dependent scoped beans
[ https://issues.apache.org/jira/browse/DELTASPIKE-398?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13790115#comment-13790115 ]
Karl Kildén edited comment on DELTASPIKE-398 at 10/9/13 7:24 AM:
-----------------------------------------------------------------
How did the syntax for this turn out?
Nevermind it was very easy to deduct from the source ;)
was (Author: karlkilden):
How did the syntax for this turn out?
> BeanProvider handling for @Dependent scoped beans
> -------------------------------------------------
>
> Key: DELTASPIKE-398
> URL: https://issues.apache.org/jira/browse/DELTASPIKE-398
> Project: DeltaSpike
> Issue Type: New Feature
> Components: Core
> Affects Versions: 0.4
> Reporter: Mark Struberg
> Assignee: Mark Struberg
> Fix For: 0.5
>
>
> BeanProvider#getContextualReference complains if you create a @Dependent scoped bean. The reason for this is that those beans shall get destroyed manually to provide proper clean up.
> We should provide methods which return a helper class which internally keep the contextual instance and the CreationalContext for it and a get() plus a release() method.
--
This message was sent by Atlassian JIRA
(v6.1#6144)