On 6/16/06, Igor Vaynberg <[EMAIL PROTECTED]> wrote: > no, there are no problems with wicket-spring poject other then some people > dont think its a "true" way to integrate with spring. sigh.
I have some more concrete issues with the current spring integration code. First, it is intrusive. Instead of using hooks or interceptors it requires a new class hierarchy. This is generally not a big deal but it makes it difficult to pick 'extensions' and put them together. As a concrete example; we have two great extensions available: wicket-spring-annot and wicket-auth-roles. However since these are both implemented in the Spring class hierarchy as subclasses of WebApplication there is no way to put these together in one project. You end up copy/pasting code to merge them in your own implementation. This is rather silly. The second problem I have with the current Spring code is that it just works in a subset of Wicket objects. For example, I have just merged auth-roles and spring-annot together for my current app and I discovered that the @SpringBean annotation does not work inside my subclass of the AuthenticatedWebSession. This is of course rather silly because that is *the* place to talk to Spring and retrieve user info through a DAO of some sort. This is something that AOP could solve pretty well without the need of a whole Injector infrastructure in the Wicket code. What I really hope is that 2.0 will include strong support for AOP and some kind of interceptor chain in the right place so that we can add functionality like Spring and Authentication annotations more easily. As I understand it the 2.0 release will be JSE 5 only, so a lot more interesting things will be possible then. S. _______________________________________________ Wicket-user mailing list Wicket-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wicket-user
