[
https://issues.apache.org/jira/browse/OWB-1072?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14545093#comment-14545093
]
Mark Struberg commented on OWB-1072:
------------------------------------
I've added a {{WebConversationFilter}} but this is _not_ activated by default.
We might add this to the StandardContext as FilterDef in the webbeans-tomcat7
module (the same way I did it for TomEE). But we cannot just use a @WebFilter
as this bombs up if we do not define a FilterMapping.
So for now people who need this feature (which I really think will _rarely_
happen) will need to define the <filter> + the <filter-mapping> in their web.xml
> CDI 1.2 spec requires a "CDI Conversation Filter" which eagerly touches the
> Conversation
> ----------------------------------------------------------------------------------------
>
> Key: OWB-1072
> URL: https://issues.apache.org/jira/browse/OWB-1072
> Project: OpenWebBeans
> Issue Type: New Feature
> Components: Context and Scopes
> Affects Versions: 1.5.0
> Reporter: Mark Struberg
> Assignee: Mark Struberg
> Fix For: 1.6.0
>
>
> CDI 1.2 spec requires a "CDI Conversation Filter" which eagerly touches the
> Conversation.
> Our OwbConversationFilter will just touch the ConversationContext() and thus
> 'attaching it'.
> Please note that we will not implement the full spec wording as it requires
> to force the Conversation attachment to be associated before any
> Servlet#service() method gets invoked if this Filter is not manually mapped
> in web.xml. And this sentence is perfectly backward incompatible with CDI-1.0
> because this would totally blast all JSF ViewRoot conversation propagation,
> etc.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
