Well the point is that in WebSphere all those settings and modules should already be set up correctly. Of course this is if you use a WebSphere edition (enterprise) which supports clustering at all. Is this the case Lars-Fredrik? Or are you using e.g. the dev edition or even liberty-profile?
We did all the SPI stuff for allowing container integrators and extension builders for going the most flexible route. And to allow to build a container yourself (e.g. by just taking tomcat + tweaking stuff yourself). Otoh if you use a Container like WebSphere or TomEE, then you usually don't need to tweak anything! LieGrue, strub >________________________________ > From: Thomas Andraschko <[email protected]> >To: [email protected] >Sent: Wednesday, 27 November 2013, 21:41 >Subject: Re: @SessionScoped and @ConversionScoped > > > >Since 1.2.0, you actually only need the clustering module + registering the >FailOverFilter in the web.xml. > >Sorry but i don't know about WebSphere, you should ask the WebSphere developer. > > > > > > >2013/11/27 Lars-Fredrik Smedberg <[email protected]> > >@Thomas >> >> >>So if I understand it correct, if I want to use the distributed session >>management in WebSphere I would need to configure the FailOverService and set >>issupportfailover to true ? >> >> >>Is that how it is configured in WebSphere out-of-the-box? If not how can I do >>that and how can I verify the setup? Is it logged at startup? >> >> >>Regards >>Lars-Fredrik >> >> >> >>On Wed, Nov 27, 2013 at 9:30 PM, Thomas Andraschko >><[email protected]> wrote: >> >>We have 2 flags in OWB: issupportfailover and issupportpassivation >>> >>>issupportpassivation only stores the beans in the session on passivation. >>>issupportfailover stores the beans after each request. >>> >> >> >> >> >>-- >>Med vänlig hälsning / Best regards >> >>Lars-Fredrik Smedberg >> >>STATEMENT OF CONFIDENTIALITY: >>The information contained in this electronic message and any >>attachments to this message are intended for the exclusive use of the >>address(es) and may contain confidential or privileged information. If >>you are not the intended recipient, please notify Lars-Fredrik Smedberg >>immediately at [email protected], and destroy all copies of this >>message and any attachments. > > >
