Igor Vaynberg wrote:
i thought the component is the view.
no, the component is the mvc not just the view. it handles its own
events and responds to them.
so, no separation
about the controllers. i thought something like: go over all components,
collect the controllers, filter the duplicates and then call each controller's
validate(), convert() and updateModel(). if several components share the same
controller, then it will collect the raw data from all of them, combine it, and
set the combined value in the model
hmmm,
class Component {
....
protected IController getController() {
return new TrivialController(this, this.getModel());
}
}
yes, but what would the IController look like? it would have the same
two getObject/setObject that the IModel has? so whats the point?
-Igor
--
===================================
Ittay Dror,
Chief architect, openQRM TL,
R&D, Qlusters Inc.
[EMAIL PROTECTED]
+972-3-6081994 Fax: +972-3-6081841
http://www.openQRM.org
- Keeps your Data-Center Up and Running
-------------------------------------------------------
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&kid=120709&bid=263057&dat=121642
_______________________________________________
Wicket-user mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/wicket-user
