[
https://issues.apache.org/jira/browse/OWB-223?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gurkan Erdogdu closed OWB-223.
--
Resolution: Fixed
Done.
> Work on (Section 3.1 - Managed beans) of coverege-cdi.html of RI TCK
> ---
Yes, but for the ViewScoped Context, I cannot use our ContextFactory, because
it is not a standard scope.
I need to go the route via the (almost) normal extension way.
LieGrue,
strub
--- On Sun, 1/10/10, Gurkan Erdogdu wrote:
> From: Gurkan Erdogdu
> Subject: Re: Context.isActive() question
Hi;
VOTE is closed.
This VOTE is passed with the 8 +1, no -1 or 0. I will create a JIRA issue for
INFRA.
+1 VOTES
--
Gurkan Erdogdu (PMC)
Mark Struberg (PMC)
Eric Covener (PMC)
Jean-Louis MONTEIRO
Joseph Bergmark (PMC)
Matthias Wessendorf
Kevan Miller(PMC)
Chris Shayan
Thks;
Gurk
Really do not understand what you want to say! I do not know what is Weld
session context is about or not.
In our case, session context are managed by the SessionContextManager. Session
scope instances are only available while user session is active. Therefore,
each session context is activate
Hi!
Gurkan, I think I know why JBoss guys really need the isActive() and we do not.
It seems that Weld Contexts are more like our ContextManagers (e.g. Welds
SessionContext <-> our SessionContextManager.
So Weld has only one SessionContext in the container and we have n (1 for each
new Session
[
https://issues.apache.org/jira/browse/OWB-223?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12798467#action_12798467
]
Gurkan Erdogdu commented on OWB-223:
3.4- 3.7 has done
> Work on (Section 3.1 - Managed
