Hi Igor,
>here is something i threw together that solves the deserialization >andability
>to use the new operator to create pages.
thanks for your work on this.
Regretfully it's still a solution I wouldn't like to use:
IMHO dependency injection should not be done by the object which has the
d
>and you have to have the pages defined as beans in the application >context?
>with their properties specified?
Yes, I configure most wicket stuff in a separate context, which is bootstrapped
by a custom application factory:
>but how does the above handle deserealization of pages?
>
>>An EditUserPage for example cannot be bookmarkable
>>because it needs to know which user to edit.
IMHO an EditUserPage parameterized with a userId is a perfect match for a
bookmarkable URL.
I didn't say, I'd never use setResponsePage(..).
If I have large transactional state to be transferred t
