[Wicket-develop] Wicket IModel questions

[Jan Blok]

Title: Message

Hi,   I'm investigating Wicket for possible use in Servoy (Servoy.com is a database development/deployment tool ala M$-access/filemaker/4d/etc) while going trough the JavaAPI to investigate how the databinding is done and how wicket is working internally I have some questions.   As we are doing some serious databinding between models and components in Servoy I really wonder why your IModel is so high-level? , it seems to me you need many models which are not very useful.   I noted some is already done to overcome this like: -defined:Component(String name,Serializable object,String _expression_) -used:new MyComponent(name, new PropertyModel(new Model(model), _expression_));   But to give you an idea how we handle databinding inside Servoy we give all Components a "dataProviderID" so all components have get/setDataProviderID(...) methods and our model have getValue(dataProviderID) and setValue(dataProviderID,newValue), by doing so a model is always something like a row/record/non primitive object/map, instead of just a value wrapper.   Would it be an idea to do something similar? to overcome model in model constructs...just a thought   So far it seems to me wicket is a very cool framework!   Regards Jan Blok Servoy