Hello Volunteers,
>>>>> On Mon, 18 Mar 2013 14:59:32 -0700, Edward Burns <edward.burns_at_oracle.com> said:
EB> At this point the only design changes I can accept are serious flaws
EB> that you absolutely cannot agree to shipping the spec without first
EB> seeing fixed.
Our QA engineer, Sreekanth Manga, found one [2], and I've fixed it.
Here is the resolution.
8<-----------------------
M usingFacesInWebapps.fm
New text for 11.4.3.3 Packaging Flows in Directories:
[...]
The following conventions apply to flows defined in this manner. Any
flow definition in the corresponding -flow.xml file will override any
of the conventions in the case of a conflict.
Every vdl file in that directory is a view node of that flow.
The start node of the flow is the view whose name is the same as the
name of the flow.
Navigation among any of the views in the directory is considered to be
within the flow.
The flow defining document id is the empty string.
In the case of a zero length flow definition file, the following also applies:
There is one return node in the flow, whose id is the id of the flow
with the string "-return" (without the quotes) appended to
it. For example, if flowId is shopping, the return node id is
shopping-return.
8<-----------------------
I have uploaded the Release Candidate 2 of the JSF 2.2 Final Spec to
[1]. This has the changes in 11.4.3.3.
I can still accept editorial improvements.
I plan to hand the final spec to JCP on Friday 22 March 2013.
Please rest assured that we will have follow-up releases of JSF to
address concerns that we didn't address in JSF 2.2.
Ed
--
[1] http://java.net/projects/javaserverfaces-spec-public/downloads/download/JSF_2_2/spec_snapshots/javax.faces-api-2.2-FINAL_RC1.zip
[2] http://java.net/jira/browse/GLASSFISH-19937
--