Thanks Martin for the work-around.
Jira added: https://issues.apache.org/jira/browse/WICKET-3936
Thanks
Mike
Am 28.07.2011 09:26, schrieb Martin Grigorov:
i would like to decouple the page dependencies. My page flow is
implemented by using bookmarkable page links.
As we all know they take a pa
It is quite easy to extend SpringComponentInjector so that it will
look for another annotation, e.g. @SpringBean2 which wont be proxy-ed.
Yet another one is to create a ticket to add an additional attribute
to original @SpringBean (proxy = false).
On Thu, Jul 28, 2011 at 10:18 AM, Mike Mander wro
Found a solution, but would be great if i could get some tips about the
consequences.
I was wrapping the beans in proxies by setting the flag in
SpringComponentInjector to true.
Now it's set to false and it's working. But i'm a bit in doubt that i
opened pandoras box
with this.
It was
addCompo
Hi,
i would like to decouple the page dependencies. My page flow is
implemented by using bookmarkable page links.
As we all know they take a page class as parameter. This couples both pages.
So i thought it's a good idea to give the page class a name in my Spring
application context and refer
