Why is there such a tie to the markup and the code, meaning can you describe the situations that cause this tie, such as you described with wicket 2.0 why does a component need to read attributes off of the markup upon initialization.
It is Wicket's mission to provide a framework for: 'enabling component-oriented, programmatic manipulation of markup' (see http://wicketframework.org/Vision.html). The separation of concerns lies in the fact that one is for processing logic (the Java side) and the other is for display/ layout (markup side). But tbh, 'separation of concerns' is always something that will be debatable; it just depends on what level you look at. Eelco
