If that is correct, would it be possible to implement JSF within Struts chain? Could a JSF implementation be decomposed into chain commands, and therefore allow the user to mix and match?
I guess where I'm going with this is one of the huge advantages of an event-based view framework like JSF is the ability to have self-contained, complex components. On the other hand, I think event-based approaches are poor at handling complex workflows as code has to be split up into different event methods. It seems like a perfect marriage would be event-based framework for the components, but continuations-based framework for application events and actions.
By decomposing JSF into commands, JSF could handle events from its components, but application processes would be handled on a request basis with Action's, continuation-capable flows, or whatever. I suppose this would not be a real JSF implementation since JSF concepts like navigation wouldn't be used.
Perhaps this is what Shale is trying to, or it is just flatout impossible, I just thought I'd throw the idea out there. I like the chain-based request processing model of Struts, but want to take advantage of JSF components. Does this make any sense?
Don
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
