[
https://issues.apache.org/jira/browse/OWB-671?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13417241#comment-13417241
]
Mark Struberg commented on OWB-671:
-----------------------------------
it's not easy to add this as we would need this information before we startup
the OWB. We cannot use the OWB configuration mechanism as this might get
switched during boot. Kind of a chicken-egg problem.
Thus -> 1.2.0
> Automatically register FailOverFilter if failover is activated
> --------------------------------------------------------------
>
> Key: OWB-671
> URL: https://issues.apache.org/jira/browse/OWB-671
> Project: OpenWebBeans
> Issue Type: New Feature
> Components: Java EE Integration
> Affects Versions: 1.1.4
> Reporter: Mark Struberg
> Assignee: Mark Struberg
> Fix For: 1.2.0
>
>
> Currently a user needs to activate OWB failover in an
> META-INF/openwebbeans/openwebbeans.properties file with the following content:
> {code}
> org.apache.webbeans.web.failover.issupportfailover=true
> {code}
> This is suboptimal as the decision to use failover is usually a deployment
> question. Thus we should switch to enabling this feature in the container via
> a JNDI property.
> The openwebbeans-tomcat6 and openwebbeans-tomcat7 (and also TomEE)
> ContextLifecycleListener could then add the required FailOverFilter
> automatically.
> This can be done via context.addFilterDef and context.addFilterMap. The
> Filter should get added on the first position, probably by getting the
> existing filters with context.findFilterDefs() and do a
> context.addFilterMapBefore();
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
