Largely this depends on the plans for Sailfin, which I don't think
have been determined yet. Without Sailfin, we would probably not
add JSR 319 support. My take on JSR 319 is that it's useful if you
already have some existing infrastructure or tools that are managing
the availability of applications. This was sometimes the case in the
telco space, but rarely the case in the general app server space.
Either way, this is unlikely to be something that will appear in 3.1.
Dies Koper wrote on 03/23/2010 05:51 PM:
> Are you aware of JSR 319: Availability Management for Java, which is
> probably going to be approved next week?
>
> http://jcp.org/en/jsr/detail?id=319
>
> This JSR attempts to "standardize supervision and control of Java
> runtime entities in order to achieve high availability."
>
> Section 9 of the spec has images that include topics we're discussing at
> the weekly admin meetings (clusters with nodes, server instances and
> configs).
>
> Will GFv3.1 implement it?
>
> I found the following documents (by Nandini, Hong and Kedar) that seem
> to indicate this has been considered for SailFin and GlassFish, but I
> don't know what the current state is.
>
> http://wiki.glassfish.java.net/attach/FunctionalSpecsOnePagers/SAF-AMF-One-Pager.htm
>
> http://fisheye5.cenqua.com/browse/~raw,r=1.3/sailfin/www/documents/saf-glassfish-fs-phase-1.html
>
> Thanks,
> Dies
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: admin-unsubscribe_at_glassfish.dev.java.net
> For additional commands, e-mail: admin-help_at_glassfish.dev.java.net
>