Does tapestry fire the wrong page event listener?

[Alan Chandler <al...@chandlerfamily.org.uk>]

In a thread I started a couple of messages back I asked about the ordering of 
the Page Event listeners with respect to reloading data from within a form.

In order to try and find out more for myself, I created a page with a 
pageAttach, pageValidate and pageBeginRender methods and declared the page as 
implementing all of the appropriate Listener interfaces.

I have a calling page which has a form listener, then then gets the test page 
via an @InjectPage routine, sets some parameters and returns with this test 
page as the return value.

I then put a breakpoint on all three routines and the calling page

Firstly, none of the listeners are fired until after the calling page's form 
listener returns - nothing appears to fire when the page is first obtained

[This leads me to ask the question what the differing purpose of each page 
event is - there does not seem to be any real difference]

Secondly, and more importantly

The breakpoint in my pageValidate routine was never hit.  Instead I noticed 
that under the eclipse debugger I hit a breakpoint in the pageAttach 
listener, but that the calling routine seemed to be trying to call the 
pageValidate listener (a quick peak at the calling code was no help - it 
seems a bit obscure how it does it - I couldn't see how it was 
differenciating one listener from another - which of course may be the 
problem).

Is this an Eclipse debugger problem or a tapestry one?
-- 
Alan Chandler
http://www.chandlerfamily.org.uk
Open Source. It's the difference between trust and antitrust.

---------------------------------------------------------------------
To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tapestry-user-help@jakarta.apache.org