On Mon, 2005-08-22 at 12:31 +0200, Martin Fey wrote:
> The serializable-thing is one reason why there is a integration contribution
> in form of a pull model: SpringBeanModel
>
> I'm not yet convinced that Spring-managing Wicket-components (or parts of
> them) is a really good idea, because of all the issues discussed earlier in
> this mailing list (e.g. unavailability of Spring in the constructor). I think
> the Model-interface is the best extension point for integrating other tools
> and frameworks.
>
> But I'm curious about the other ideas.
Does Wicket require one to add components on constructor? In Spring we
often do initialization by implementing InitializingBean interface.
Spring bean factory ensures that all properties are injected before
calling the interface method:
public class MyForm extends Form implements InitializingBean {
private transient MyDao myDao;
public void afterPropertiesSet() {
Assert.notNull(myDao);
...
add(new MyOtherComponent());
...
}
public void setMyDao(MyDao myDao) {
this.myDao = myDao;
}
}
--
Joni Suominen <[EMAIL PROTECTED]>
-------------------------------------------------------
SF.Net email is Sponsored by the Better Software Conference & EXPO
September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices
Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA
Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf
_______________________________________________
Wicket-user mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/wicket-user
