What do you want in Spring Web Flow 1.1?

[ronwheeler]

the point is that these new things should be explain it in detail in documentation(pdf) but furthermore of a specification, something with more details(reason of all, why use this, when,other options, consequences etc etc) and examples of course

if these information is already in the web, pls share the link, SWF in a first glance can be complicated,

Consider this an investment in building the community.

Specific requests:
1) Add more commas to the documentation - Bug request filed.
2) Move 1.3 and 1.4 to an appendix. What do they have to do with my application? May be nice to know someday but only makes the introduction more complicated at the start and does not really add to the initial experience or understanding of how to design a Webflow application.
3) In place of 1.3 and 1.4, put in an architectural overview of "my test application". Start with a description of a simple sample. It could be any one of the existing samples but simplify it to just show a simple set of transitions rather than the more advanced or application specific stuff in the existing samples.
Keep the discussion at th introductory level with forward references to where the particular concept will be discussed in detail.
4) You might want to consider using some of the graphs from the SpringEclipse plug-in. They are fairly attractive.
5) More commentary in the sample applications is always helpful.
6) Additional samples always appreciated.

The documentation is a much bigger problem in getting Spring and Spring WebFlow accepted than any deficiency in the functionality.
From my limited experience and the discussion of the enhancements requested, very few of them are show stoppers that are preventing people from getting their applications working. The documentation is.

Ron

[Tom Hicks]

Intermediate End States

I really hate the term but I haven't yet thought of a better one. "Checkpoint" bears some similarity but even thats not right.

In pattern-matching and backtracking languages (which implemented
flow-like control of execution) these states used to be called "fences";
once you went over/past the fence you couldn't go back.

Similarly, we could call such a thing a "fence-state".
cheers,
-tom

[Tom Hicks]

Keith, I'd like SWF to be much more sparing on the size and number of request parameters.

[snip]...

Here is why: I am implementing an web UI to a chess game. Each of the 64 fields (much more in certain chess variants) is potentially clickable, which means I really have to keep URL sizes down for the links (64 * 100 chars is already 7 kB just for the links!). Currently (without SWF), I just use the URL "?id=a4" for field a4 (6 bytes). This has kept me from introducing SWF to my project.

Couldn't you use a small bit of Javascript to implement this?

For example:

  <script type="text/javascript">
    function clickSquare(whichSquare) {
      location.href="${pageContext.request.contextPath}/chessMove.spr?_flowExecutionKey=${flowExecutionKey}&_eventId=clicked&square=" + whichSquare;
    }

then, within the page body create "links" for each square which just
call the javascript function:

<a href="javascript:clickSquare(a4)"/>
...
<a href="javascript:clickSquare(b2)"/>
...etc....

Something like this should be doable. Good luck,
-tom

[rakesh.ranjan]

Hi,

I have Oralce D2K application and after login application i am opening the java application.

I did the scripting in VUgen 9.52 (Load Runner) after reply script executed successfully but BD is not getting updated and no error shown.

Kindly give solution for the same.

Regards,
rakesh