[ tapestry-Feature Requests-645827 ] Dealing with missing super.detach()

[email protected]
Newsgroups gmane.comp.java.tapestry.devel
Message-ID <[email protected]>
Feature Requests item #645827, was opened at 2002-11-29 16:24
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=354754&aid=645827&group_id=4754

Category: framework
Group: None
Status: Open
Resolution: None
Priority: 5
Submitted By: Adam Greene (ccm682)
Assigned to: Nobody/Anonymous (nobody)
Summary: Dealing with missing super.detach()

Initial Comment:
Everyone at one time or another makes the mistake of 
creating a detach method within the java source of a 
page and forgets to include a super.detach() and then 
spends 2 hours trying to figure out what went wrong.

Therefore, we require a way (such as have
Tapestry check to see if the engine or requestCycle 
property is not null, which implies that 
AbstractPage.detach() was not invoked at some
point) and identifying this and either handling it 
gracefully or throwing an exception that says "don't 
forget to call super.detach() or something like that.


----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=354754&aid=645827&group_id=4754


-------------------------------------------------------
This SF.net email is sponsored by: Get the new Palm Tungsten T 
handheld. Power & Color in a compact size! 
http://ads.sourceforge.net/cgi-bin/redirect.pl?palm0002en
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.