Thanks to everyone for the great work on this release, and for the JSF
specification as a whole. It is great to have followed the specification
from its infancy to its current maturity.
I have only briefly reviewed the EDR pdf thus far, but I thought it would
be good to mention that some of the embedded JIRA links are not
functional. I know that all of the JIRA links do work, in fact, if they
are manually added into the browser. However, some of the links that
contain multiple issue numbers separated by a comma are not clickable,
whereas others that contain multiple issue numbers work fine and bring up
the first issue in the list when clicked. It seems that a space is required
after each comma in order for the initial issue link in the list to
function properly.
Again, not a big deal but I thought I'd better point it out.
I will continue to review the document...everything else looks great so
far. Thanks again for putting this together, and to everyone for their
continued work and dedication to JSF.
Josh Juneau
juneau001_at_gmail.com
http://jj-blogger.blogspot.com
https://www.apress.com/index.php/author/author/view/id/1866
On Thu, Oct 8, 2015 at 10:20 AM, Edward Burns <edward.burns_at_oracle.com>
wrote:
> Hello Volunteers,
>
> As I've been saying in recent weeks, we're releasing EDR of JSF 2.3 for
> JavaOne. For EDR we are only obligated to provide the spec, but since
> we have always practiced TDD in JSF and Mojarra we have the
> implementation ready as well! The unfortunate exception is the lack of
> implementation of <f:socket/>. Thanks to Arjan and Zhijun for helping
> resolve the problem with the GlassFish AdminGUI. Breaking that is a
> non-starter. We have to keep that working.
>
> Manfred is working on releasing Mojarra 2.3.0-m04 at this very moment.
> Please share with the group the results when you complete this very
> important task, Manfred.
>
> What is the EDR?
> ================
>
> As you know, our spec has always consisted of two main parts:
>
> * The Prose Document (PDF)
>
> * The Generated Spec (javadoc, RenderKitDoc, VDLDoc, JSDoc)
>
> Where do you get it for review?
> ===============================
>
> Please find the proposed EDR of each at
>
>
> https://java.net/projects/javaserverfaces-spec-public/downloads/download/JSF_2_3/Early%20Draft%20Review/JSF_2_3_EDR.pdf
>
> and
>
>
> https://maven.java.net/service/local/repositories/snapshots/archive/org/glassfish/javax.faces/2.3.0-m04-SNAPSHOT/javax.faces-2.3.0-m04-20151008.070344-184-documentation.jar/!/javadocs/index.html
>
> respectively.
>
> Sorry for the rush review request, but I want to hand this to JCP by
> 16:00 GMT tomorrow, Friday 9 October 2015. It's possible that if
> someone has feedback after that time I may be able to replace the draft
> with a newer revision and have JCP pick that up, but I can't guarantee
> it.
>
> What do you look for in reviewing?
> ==================================
>
> For the Generated Spec, the color coded changebars are super helpful.
> For the Prose Document, look in the "Changes between 2.2 and 2.3"
> section of the preface. It has links to the other parts of the spec.
> If there is something you put in but you don't see it represented in
> that section, let me know and I'll try to add it. Please include the
> JIRA as well.
>
> Thanks for all your hard work on JSF over this spec and over the years.
> Together we have really built a historically unique technology and
> community ecosystem that delivers real value to businesses.
>
> Thanks,
>
> Ed
>
> --
> | edward.burns_at_oracle.com | office: +1 407 458 0017
> | 21 Business days til JavaOne 2015
> | 36 Business days til DOAG 2015
>