it will be the mediator between the components and the model (like the Controller in MVC)
Currently the component is the controller, so it would be an extra indirection.
if the framework interacts with the manager, rather than directly with the components, for the purpose of updating the model, then one manager can be associated with two components. thus, when its 'updateModel()' method is called, it will interact with the two components, query their raw value and set it in the model.
Could you give some dummy code on how that would look like from a client's perspective? Eelco ------------------------------------------------------- Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid0709&bid&3057&dat1642 _______________________________________________ Wicket-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/wicket-user
