See the WebSphere eXtreme Scale Wiki for links to eXtreme Scale Version 7.0 documentation.
If you log in
with your developerWorks ID, you can leave comments and feedback for the development team.
Spring is a popular framework for developing Java applications. WebSphere eXtreme Scale provides support to allow Spring to manage transactions and configure eXtreme Scale clients and servers.
Spring managed native transactions with eXtreme Scale
Spring provides container-managed transactions along the style of a J2EE application server but has the advantage that the Spring mechanism can have different implementations plugged in. So eXtreme Scale provides the transaction manager integration to allow Spring to manage transaction lifecycles. Refer to Spring managed native transactions with eXtreme Scale for details.
Spring managed extension beans and namespace support
Also, eXtreme Scale integrates with Spring to allow Spring-style beans defined for eXtreme Scale extension points or plug-ins. This feature provides more sophisticated configurations and more flexibility on configuring the extension points.
In addition to Spring managed extension beans, eXtreme Scale also provides a spring namespace called "objectgrid" with beans and built-in implementations predefined in this namespace, making it easier for users to configure eXtreme Scale.
Refer to Spring managed extension beans and namespace support for more details on these topics and a sample on how to start an eXtreme Scale container server using Spring configurations.
Shard scope support
With the traditional style Spring configuration, an eXtreme Scale bean can either be a singleton type or prototype type. Additionally, eXtreme Scale supports a new scope called "shard" scope. If a bean is defined as shard scope, then only one bean will be created per shard. All requests for beans with an id or ids matching that bean definition in the same shard will result in that one specific bean instance being returned by the Spring container.
The following example shows that a com.ibm.ws.objectgrid.jpa.plugins.JPAPropFactoryImpl bean is defined with scope set to shard. Therefore, only one instance of JPAPropFactoryImpl will be created per shard.
<bean id="jpaPropFactory" class="com.ibm.ws.objectgrid.jpa.plugins.JPAPropFactoryImpl" scope="shard" />
Spring Webflow
Spring WebFlow stores its session state in the HTTP Session by default. If a Web application is configured to use eXtreme Scale for session management, then it will be used automatically by Spring to store this state and it will be made fault tolerant in the same manner as the session.
Spring packaging
The eXtreme Scale Spring extensions are in the ogspring.jar file. This jar file must be on the classpath for spring support to work due. If a JavaEE application running in an XD augmented ND then the application should place the spring.jar file and its associated files in the EAR modules. The ogspring.jar must also be placed in the same location.
© Copyright IBM Corporation 2007,2009. All Rights Reserved.
