I tried something that should throw an exception IMO.
public class Foo implements Serializable {}
public Index extends WebPage {
private Foo foo = null;
public Index() {
Form form = new Form("form");
form.add(new TextField("foo", new PropertyModel(this, "foo")));
}
}
I think that depending on the catch all for spring is probably the
best for Wicket. If you really want to depend on the individual
modules, it is merely a matter of adding excludes to your
wicket-spring dependency and including those you do want.
The reason being: most people (at least those that
Currently the 1.3.0-beta2 version of wicket-parent and wicket-spring depend
on the large single "spring" jar. Can this be changed to just depend on the
org.springframework artifacts spring-context and spring-web?
--
View this message in context:
http://www.nabble.com/Can-wicket-spring-just-de
