Overview and update Pete Raymond

» Purpose of this presentation » Background » JSR Requirements » Key concepts » Relationship to other standards/approaches » Example API » Demo » Timeline » Q & A

» Raise awareness of JSR-350 State Management » Seek feedback on concepts and usage

» Standard formed through JCP (2.8  2.9) » Oracle lead (Mitch Upton), participation from Red Hat, IBM and independents » Expert group activated April 2012 » Some existing proprietary solutions in WebLogic, Tomcat and JBoss

» “…develop an API that applications and JavaEE containers can use to offload the responsibility of state management into third party providers with different quality of service characteristics” (JSR) » Standardize existing APIs

» Mobile - cross platform state handling » Integration - Transfer of state between platforms » Capability based provider querying » Transient data e.g. session state » Non relational data e.g. JSON, XML, JavaScript

» This slide needs more » JPA ˃Relational ˃Persistent » Proprietary APIs ˃Reuse ˃Ease of use » NoSQL ˃?

» Store and retrieve state independent of mechanism » Modular and consistent implementation » Capability based matching of client and provider » Support innovation and the cloud » Easy to use interfaces – user, provider, platform

JEE Client State Management API JSE Client Built-in Provider 3 rd party Provider Custom Provider

» State (State Container) » State Connection Factory » State Connection » State Container » State Map » Capability

» Unit of data » Uniquely identified within a scope » Persistent for a business period » Used by web apps, web services, JSF, CDI » Currently implemented via in memory, file, database, cluster

» Create one or more State Connections based on required capabilities » Associated to single provider » Typed e.g. Java class (…probably)

» Connection to state management services provided by some provider » Expose capabilities » Contains configuration » Controls the transaction – either local or distributed using JTA » Use directly or to get a StateMap

» Container for a user-defined state value that allows a State Management provider to present and track system-level details about the value » An instance of State contains a single user- specified value

» Exposes only entries with a given key and value type in StateConnection » Convenience interface - clients deal directly with user- specified key and value types, no need to see containing structures such as Key and StateContainer » Contains: ˃globally unique key ˃value of a user-defined type ˃tracking information » Key ˃User defined + GUID » Values ˃Java type (e.g. Person class) ˃Streams? ˃XML?

» Behaviour offered by a provider ˃Durability ˃Transactions ˃Isolation and concurrency control » Supported by configuration » Described by a unique name

State Connection State Map State Connection Factory State Management Registry 0..* State Container 1 0..* 1

State Connection Factory Client Application State Management Registry Find State Connection Factory Get State Connection Create State Connection Create

Key Dog Client Application State Connection new (“fido”, “Sheperd”) createKey(fido.getUniqueName(), String.class, Dog.class) put(fidoKey, fido) fidoKey StateContainer fidoState get(fidoKey) fido copy State Container create Store Retrieve

Dog Client Application State Connection new (“fido”, “Sheperd”) getStateMap(String.class, Dog.class) put(fidoKey, fido) StateMap dogMap get(fidoKey) fido copy State Map createStore Retrieve

Client State Management API (350) Data Grid API (347)

Client State Management API (350) Data Grid API (347)

Client State Management API (350) Data Grid API (347) State Management API (350)

» Provider ˃Implement the specification ˃Innovate with new capabilities » Administrator / Developer ˃Configure the state connection factory ˃Make a State Connection available » Developer ˃Use State Connection and State to accelerate development

» Comparing state persistence: ˃Relational / SQL ˃Object ˃NoSQL » Target products ˃Application Server ˃Android

» Typing ˃Strong versus weak » Is StateMap necessary / desirable?

» Expected milestones » How to provide feedback

» Java State Management Wiki » JavaOne presentation Java-State-Management-v2.ppthttp://java.net/downloads/java-state-managemen/2011-J1- Java-State-Management-v2.ppt » The spec