[jboss-jira] [JBoss JIRA] (WFLY-81) CDI beans with SET replication trigger are not replicating

[Paul Ferraro (JIRA)]

     [ https://issues.jboss.org/browse/WFLY-81?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Paul Ferraro closed WFLY-81.
----------------------------

    Fix Version/s: 8.0.0.Alpha2
                       (was: 8.0.0.Beta1)
       Resolution: Out of Date


This is out-of-date.  SET replication trigger was deprecated as of 8.0.0.Alpha2.
                
> CDI beans with SET replication trigger are not replicating
> ----------------------------------------------------------
>
>                 Key: WFLY-81
>                 URL: https://issues.jboss.org/browse/WFLY-81
>             Project: WildFly
>          Issue Type: Bug
>          Components: CDI / Weld, Clustering
>            Reporter: Radoslav Husar
>            Assignee: Stuart Douglas
>             Fix For: 8.0.0.Alpha2
>
>
> Please check if the use case is correct:
> https://github.com/rhusar/clusterbench/blob/master/clusterbench-ee6-web/src/main/java/org/jboss/test/clusterbench/web/cdi/CdiServlet.java
> https://github.com/rhusar/clusterbench/blob/master/clusterbench-ee6-web/src/main/java/org/jboss/test/clusterbench/web/cdi/SessionScopedCdiSerialBean.java
> The methods are only called on the CDI-mananged bean, there is no interaction with the HTTP session itself. Should the replication trigger on the bean itself or is anything else required?
> https://hudson.qa.jboss.com/hudson/job/eap-6x-failover-http-cdi-shutdown-repl-sync/2/

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira