New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Cdi 457 #289

Closed
wants to merge 2 commits into
base: 2.0.Aplha4
from

Conversation

Projects
None yet
3 participants
@johnament
Member

johnament commented May 4, 2016

No description provided.

@johnament

This comment has been minimized.

Show comment
Hide comment
@johnament

johnament May 4, 2016

Member

I'm undecided if this should change or if section 5.6.1 should be updated.

I'm also not sure which branch to target.

Member

johnament commented May 4, 2016

I'm undecided if this should change or if section 5.6.1 should be updated.

I'm also not sure which branch to target.

@mkouba

This comment has been minimized.

Show comment
Hide comment
@mkouba

mkouba May 4, 2016

Contributor

@johnament See also #286 - it's related.

Contributor

mkouba commented May 4, 2016

@johnament See also #286 - it's related.

@mkouba

This comment has been minimized.

Show comment
Hide comment
@mkouba

mkouba May 4, 2016

Contributor

By the way, I think it is defined even now:

6.4.1. Dependent objects:
An instance of a bean with scope @dependent obtained by direct invocation of an Instance is a dependent object of the instance of Instance.

5.6.1. The Instance interface:
The method destroy() instructs the container to destroy the instance. The bean instance passed to destroy() should be a dependent scoped bean instance, or a client proxy for a normal scoped bean. Applications are encouraged to always call destroy() when they no longer require an instance obtained from Instance.

The only questionable part is this {{javax.enterprise.inject.spi.CDI}} whose scope is not well-defined.

Contributor

mkouba commented May 4, 2016

By the way, I think it is defined even now:

6.4.1. Dependent objects:
An instance of a bean with scope @dependent obtained by direct invocation of an Instance is a dependent object of the instance of Instance.

5.6.1. The Instance interface:
The method destroy() instructs the container to destroy the instance. The bean instance passed to destroy() should be a dependent scoped bean instance, or a client proxy for a normal scoped bean. Applications are encouraged to always call destroy() when they no longer require an instance obtained from Instance.

The only questionable part is this {{javax.enterprise.inject.spi.CDI}} whose scope is not well-defined.

@johnament

This comment has been minimized.

Show comment
Hide comment
@johnament

johnament May 4, 2016

Member

While it may be defined, its not clear how or why you would use the methods currently which is really my aim here. If you recall, this originally came up as a way to manage dependent objects that had no bounds.

It seems like we may be looking at the same problem, so lets bring it up on the mailing list. I'll close this out for now.

Member

johnament commented May 4, 2016

While it may be defined, its not clear how or why you would use the methods currently which is really my aim here. If you recall, this originally came up as a way to manage dependent objects that had no bounds.

It seems like we may be looking at the same problem, so lets bring it up on the mailing list. I'll close this out for now.

@johnament johnament closed this May 4, 2016

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment