shale was concipied as the next struts, but built on jsf (logic -> the standard).
my questions: 1. why it was so long a underproject -> i see really less commons (because built on jsf) 2. clay as view - model and controller (where is the direct boarderline? - was more easier to see in struts) 3. as i reviewed clay -> it supports 2 really modes -> the jsf mode and the tapestry (all other like xml are extras) 4. :-( there is no remoting docs on the side -> everyone talks about ajax support 5. the tiger support will be implemented in such a way import org.apache.shale.tiger.managed.Bean; import org.apache.shale.tiger.managed.Scope; import org.apache.shale.tiger.managed.Value; // Define a managed bean named "mybean" to be put in session scope @Bean(name="mybean" scope=Scope.SESSION) what are the really advantages of using tiger support? 6. what are the advantages of using the dialog manager -> couldn't it also realized by using faces-config.xml? answers will be great to understand the whole relation stephan
