On 3/10/06, Phil Zoio <[EMAIL PROTECTED]> wrote: > I have looked Beehive although I'm not really familiar with it at all. > However, it does seem that Beehive is at a higher level of abstraction > that the Struts extensions, and also broader in scope. For example, it > has its own tag library as well as some quite new abstractions (such as > PageFlowController).
I worked on page flow idea before. Dropped the idea. My current opinion that page flow is a wrong concept. A dead end. The whole idea of working with pages (aka views) instead of working with actions/forms (aka model) seems wrong to me now. Why would you want to define flow between the views? Views depend on the state of the web resource. If you solidify your view relationship, you would have to patch the model state depending on the view which seems totally upside down to me. I have my own flow implementation, in the form of model state updates, where each state have a corresponding view. I navigate between model states, not between views that depend on model state. See the difference? Michael. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
