Hi Bill/Jeff/All,
Thanks a lot for the update. Glad to see some of the stuff you presented
e.g. at EclipseCon 2010 is finally getting into the JCP, Jeff.
Although that has been withdrawn and was only supported by a few Individual
Members including myself, there was a JSR proposal about management and
transfer of application state:
http://jcp.org/en/jsr/detail?id=323
"movement of code, data and execution state from one location to another."
sounds a lot like something for the Cloud, but I guess it was a bit too soon
and too visionary back then. Assuming some of the original EG members plus
Spec Lead Hiroki are still around, I would consider some input where it fits
in with what 350 aims to do.
Cheers,
Werner
On Wed, Aug 3, 2011 at 11:42 PM, Bill Shannon <bill.shannon_at_oracle.com>wrote:
> Assuming this is approved, we'd like to consider this for Java EE 7.
>
> -------- Original Message -------- Subject: Announcing jsr-350 - Java
> State Management Date: Wed, 3 Aug 2011 09:14:10 -0400 From: Jeff Trent
> <trentjeff_at_gmail.com> <trentjeff_at_gmail.com> To: jsr107_at_googlegroups.com
>
> Hi All,
>
> I am pleased to announce JSR-350.
>
> The purpose of this JSR will be to develop an api/spi that applications and
> JavaEE containers can use to offload the responsibility of state management
> into third party providers where each registered provider can "advertise"
> varying degrees of QoS characteristics.
>
> The primary concept is that the eventual jsr-350 ri will be used (a)
> register state providers, and to (b) formulate queries that are used to
> obtain state providers previously registered. JavaEE and SE will be
> targeted.
>
> The acquisition of these providers will be made flexible, supporting wide
> and varying styles of query from "give me provider X", to "give me the
> provider that the servlet container is using for application Y", to "give me
> a provider that is capable of supporting transactions and listeners" for
> example.
>
> As I hope you can see here, jsr-350 should compliment jsr-107 (and 347)
> nicely. The thought is that jsr-107 (and 347) implementations would become
> providers capable of "caching", etc. Other state-management providers might
> be registered simultaneously that are, or are not jsr-107 (or 347)
> compliant. All being made available to containers (and applications) on
> equal ground, accessible to callers having the right security
> permissions/privileges to access them.
>
> Your support of this new jsr is very much appreciated. Please let me know
> if you have any questions.
>
> I also welcome interested individuals who can dedicate their time to join
> this jsr eg @ http://jcp.org/en/jsr/egnom.
>
> Thank you,
> Jeff
>
> ps. For those attending JavaOne this year, there will be a presentation
> scheduled regarding this topic (motivations, concepts, new possibilities a
> decoupled state-management system will provide, etc.) - look for the "State
> Management for Java" session in the guide.
>
>
--
Werner Keil | UOMo Lead | Eclipse Foundation | Agile Coach, Principal
Consultant | *emergn* limited
590 Madison Avenue. New York. NY 10022 | 68 Lombard Street. London EC3V 9LJ
UK
US Toll Free: +1-877.964.1981 | Worldwide Toll Free: +800.225.53482
Twitter @wernerkeil | Skype: werner.keil | www.emergn.com | Reshaping IT
* Java 7 Launch: July 17 2011, Bangalore, India. Werner Keil, Executive
Committee Member (SE/EE), will represent "Java Community Process"