Fair point :) I was surprised because it was happening for the HomePage i have, which is only ever referenced by class (in my app), and comes out of the page factory - which you do control.
I think you're probably doing the right thing - it would be a nightmare to handle it differently depending on teh component. I was passing an authenticated users variable to the super of my home page - which of course would throw an exception because the user in the session didnt exist when the page was being instantiated - instead of going to the signin page. I've got a fix, but was just curious. On Thu, May 1, 2008 at 4:41 PM, Igor Vaynberg <[EMAIL PROTECTED]> wrote: > how about because of the fact we cant magically intercept > instantiation before it happens without using some magic like managed > aop container or load time/compile time bytecode instrumentation > > -igor > >
