I use 3 too, though I've sometimes added a "self.setup()" to my SitePage, and allowed servlets to override that instead of awake. It's more consistent because it has no trans argument, and I
Agreed. We like that pattern, too. It's just basically adding a "postAwake" into the lifecycle.
Another problem is that I don't think you can fire more than one action on one servlet, so they end up being "meta-methods" sometimes, and therefore look more like event handlers.
I think I'm losing you here. IMHO, anything more complicated than actions (i.e., specified in a field; one action per request) should be coded explicitly.
No surprising ;-). What I mean is that rather than actions simply firing "deleteRecord()" on a database, they probably have to do several items of "application logic". Which means they aren't very atomic in nature. SO, they tend to be more along the lines of "submit()" or "search()" or "login()", which may group together several tasks into one action call.
It's a moot point, really.
------------------------------------------------------- This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click _______________________________________________ Webware-discuss mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/webware-discuss
