[
https://issues.apache.org/jira/browse/OWB-1109?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15093476#comment-15093476
]
Mark Struberg commented on OWB-1109:
------------------------------------
Well, it is implicit. I think the wording in the spec is a bit too narrow.
Note that the spec only defines situations where the conversation MUST be
available, but doesn't forbid additional use cases.
By default if you don't make a conversation long-running it has the same
lifecycle as @RequestScoped, right?
As the @RequestScoped is basically always enabled we don't need much further
checks imo.
We could add a simple check to the ContextsService if the ConversationContext
isActive() but I doubt it will be of much benefit. This might imo only happen
if the container setup is not proper.
What is the exact use case?
> Conversation scope check is not happening when calling methods on Conversation
> ------------------------------------------------------------------------------
>
> Key: OWB-1109
> URL: https://issues.apache.org/jira/browse/OWB-1109
> Project: OpenWebBeans
> Issue Type: Bug
> Components: Context and Scopes
> Affects Versions: 1.0.0
> Environment: n/a
> Reporter: Emily Jiang
>
> CDI spec states:
> If any method of Conversation is called when the conversation scope is not
> active, a ContextNotActiveException is thrown.
> In the OWB ConversationImpl.java, when calling the methods of Conversation,
> there is no scope active check performed at all. In the OWB 1.1.6, there is
> no such check. I checked the latest version of the ConversationImpl.java, I
> cannot see any scope check either.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
