At the moment, unless you are using a 3rd party/custom solution, all of
your flows are crammed into single massive faces-config.xml with no
reuse/modularilty. We want a name for a small/lighweight, reusable
application fragment that contains bits of these navigation flows.
How about: a "flowlet".
I like the the parallel with "Facelets".
2.0 big spec feature: Facelets
2.2 big spec feature: Flowlets!
I'll probably hate it by tomorrow, but figured it was worth a shot.
Andy
On 3/13/12 5:53 PM, Werner Keil wrote:
> - Content Flow
>
> Just playing with word, or trying to find something more generic than
> "Page".
>
> On Tue, Mar 13, 2012 at 9:41 PM, David Schneider
> <david.schneider_at_oracle.com <mailto:david.schneider_at_oracle.com>> wrote:
>
>
> I don't know about the other people in the EG but I'm open to new
> names. Existing ADF users are familiar with the term "task flow"
> but I don't think we (the EG) should feel bound to that name. My
> hope is whatever we standardize will be based on the best of all
> the existing flow concepts, not just ADF, plus anything useful we
> find we need to add. Having a new name is probably a good way to
> indicate to users that what ends up in JavaEE maybe similar to
> something they've seen before but not 100% identical. I suspect
> having the JavaEE flow concept called something other than a "task
> flow" will make my ADF life easier down the road :-) .
>
> Some random thoughts:
>
> - Faces Flow
> - Enterprise Flow
> - Application Flow
> - Page Flow (although not all the nodes are pages)
>
> Dave
>