Hey Sergey, As far as I know it should create only a single instance for each spring bean (if they are singletons that is). Thus always the same bean should be injected into your wicket classes. Does this problem occur with the @SpringBean or using the proxy approach? I've been using @SpringBean and never encountered this particular issue before. Perhaps theress something wrong with the proxy approach or its not configured properly. Could you try using @SpringBean, see Patricks reply on how to enable this.
Martijn --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
