Bill, Linda, here are some news from Greg Luck about JCache :
*"Antonio*
*
*
*As to status we submitted our draft to the JCP in February. We have been
in legal stuff since then which should be wrapping up this week now that
Software AG and Oracle are finally in agreement. *
*
*
*You should see the spec come out in draft in the next week or so.*
*
*
*It is still planned to be in EE7. Since we got delayed by legal stuff but
EE7 is also delayed we are still Ok.*
*
*
*In terms of the web profile I think it makes sense. You could include a
web caching filter or similar capability. Ehcache has ehcache-web for
example, OsCache had a cache taglet and most web frameworks these days
include caching."*
So I think it makes sense to hava JCache in EE 7 and hopefully see it
integrated more in EE 8 with the other specs (e.g. default JPA second level
cache, or web cache...). So I'm in favour to add it to EE 7 as well as the
web profile.
Which brings up the same related question "Is the Web Profile getting too
big ?". If we make war packaging a first class citizen (see a previous
thread), then there is less and less distinction between full and web
profile.
Antonio
On Mon, Sep 17, 2012 at 10:34 PM, Jeff Genender <jgenender_at_savoirtech.com>wrote:
> Linda,
>
> I am fine for all 3, but the JSON and Websockets are more priority for me.
> Batch is of a lesser priority in my book. But if it made it in, its
> certainly not a bad thing.
>
> Jeff
>
>
> On Sep 17, 2012, at 2:27 PM, Linda DeMichiel wrote:
>
> > Hi Jeff,
> >
> > Just to be sure -- all 3 in the Web Profile?
> >
> > thanks,
> >
> > -Linda
> >
> >
> > On 9/17/2012 1:25 PM, Jeff Genender wrote:
> >> I indeed support those in the profile. I think they belong there at
> this stage.
> >>
> >> Jeff
> >>
> >> On Sep 17, 2012, at 2:23 PM, Linda DeMichiel wrote:
> >>
> >>> I'd like to get input from the rest of you on this item.
> >>>
> >>> Please???
> >>>
> >>> thanks,
> >>>
> >>> -Linda
> >>>
> >>>
> >>> On 9/10/2012 5:04 PM, Linda DeMichiel wrote:
> >>>>
> >>>> We have a number of new JSRs in flight that we expect to complete
> >>>> within the Java EE 7 time frame and that we believe are appropriate
> >>>> for inclusion in the Java EE Platform -- namely:
> >>>> * Java API for JSON Processing 1.0 (JSR 353)
> >>>> * Java API for Web Socket 1.0 (JSR 356)
> >>>> * Batch Applications for the Java Platform 1.0 (JSR 352)
> >>>>
> >>>> JSON-P 1.0 and Web Socket 1.0 are also both logically candidates
> >>>> for inclusion in the Web Profile.
> >>>>
> >>>> Please let us know if you support adding these technologies to the
> >>>> full Java EE 7 Platform and Web Profile.
> >>>>
> >>>> JSR full Platform Web Profile
> >>>> ---- ------------- ----------
> >>>> JSON-P [ ] [ ]
> >>>> Web Socket [ ] [ ]
> >>>> Batch [ ] [ ]
> >>>>
> >>>>
> >>>> Note that we certainly would also like to include JCACHE (JSR 107),
> >>>> Concurrency Utilities for Java EE (JSR 236), and Java State Management
> >>>> (JSR 350), but at this time we are less certain about their readiness
> >>>> in the Java EE 7 timeframe. Hopefully, however, we will be able to
> >>>> ask you about their inclusion in the coming months.
> >>>>
> >>>> thanks,
> >>>>
> >>>> -Linda
> >>
>
>
--
Antonio Goncalves
Software architect and Java Champion
Web site <http://www.antoniogoncalves.org> |
Twitter<http://twitter.com/agoncal>|
LinkedIn <http://www.linkedin.com/in/agoncal> | Paris
JUG<http://www.parisjug.org> |
Devoxx France <http://www.devoxx.fr>