Controller-Model separation

The current design of Makumba BL API (page-based BL lookup, on_new, on_edit, etc) is simple but it has bad model-controller separation. Some parts of this code should be closer to the data types (MDDs) and some other parts (specific to the form details) should be kept near the form. One idea is to actually make these parts static methods in the JSP like so:

<mak:form id="blabla" ...>
        <mak:input name="gluglu" />
</mak:form>

<%! 
public void validateBlabla(Dictionary data){
   etc
}

public void validateBlablaGluglu ( String Object){

}
%>

Brief:

connsider versions for how "BL code near MDD" would look like
consider some concrete business logic cases, and how would they be written in this new framework
look at Struts and see what other techniques can be learned from there.