I think a key piece on information on that page is this sentence "Properties that are not listed below, such as those that control the lifecycle and services, should remain at the default value for the application server."
In other words you should not overwrite the FailOverService or ContextService that are integrated into the application server run time. On Wed, Nov 27, 2013 at 2:14 AM, Lars-Fredrik Smedberg <[email protected]>wrote: > Hi Mark > > We run WebSphere 8.5, if I understand the WebSphere documentation the > bundled OWB does use the default configuration for most of the parameters > (except for the ones specified on > http://pic.dhe.ibm.com/infocenter/wasinfo/v8r0/index.jsp?topic=%2Fcom.ibm.websphere.nd.multiplatform.doc%2Finfo%2Fae%2Fae%2Frweb_cdi_customprops.html > ). > > So the default implementation will move all context information to the > HttpSession and let the container (WebSphere in our case) decide how/where > to store the context? > > When using the FailOverService I assume you cannot hold the contexts in > memory or? How does that work? > > Is there any other implementation of the ContextService or examples on how > to modify/implement our own (most for learning I would assume....) > > Regards > Lars-Fredrik > > > > > On Wed, Nov 27, 2013 at 7:04 AM, Mark Struberg <[email protected]> wrote: > >> >> >> 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. >> > >> > >> > > > > -- > 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. >
