Hi Lars!
Our storages can be changed easily. It depends on the ContextsService SPI implementation which is being used. By default in native OWB we hold all the contexts in memory for better performance. Of course we do observe session passivation and on willPassivate store the context over into the session. If you mean to create a clustered environment, then there is also an own FailOverService which you can activate by simply adding the openwebbeans-clustering module. What is your exact operation environment? TomEE, Geronimo, WebSphere, Tomcat, Jetty, standalone, ...? OWB is already used in quite a few containers and this topic is also depending on the owb version + the integration scenario in the container. LieGrue, strub >________________________________ > From: Lars-Fredrik Smedberg <[email protected]> >To: [email protected] >Sent: Tuesday, 26 November 2013, 23:41 >Subject: @SessionScoped and @ConversionScoped > > > >Hi! > > >I assume that both @SesionScoped and @ConversationScoped beans store their >data in the HttpSession? If not how is this handled? >Is there any (preferred) way of changing where data is stored? E.g. under >certain circumstances store data in a DB rather than in the HttpSession (to >make it available to other containers). > > >Regards >Lars-Fredrik > > > >-- >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. > >
