> -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On Behalf Of Gareth > Kirwan > Sent: 22 December 2006 12:07 > To: mason-users@lists.sourceforge.net > Subject: [Mason] chain_append feature > > > I've got a situation where my dhandler comps an action: > /items/10/view > > /items/10 decides to call a component 'view'. > > In my autohandlers throughout I want to be able to call methods and > attributes on this component. > I could store it in a global, or do something else with it, but that didn't > seem fitting. > I wanted to do: > $m->request_comp->scall_method('title') and the such like. > > Not only this, but I wanted dhandler to stay in the chain, since I feel it's > fitting. > The chain should look like: > /autohandler -> /items/autohandler -> /items/dhandler -> /items/view
I'm not quite sure what you're trying to achieve here. It sounds like you want your dhandler to act like an autohandler sometimes, but not others? If you want this behaviour, why not get your final component to inherit from the dhandler; that way the code for deciding if the dhandler is used is in the final component. You would, however, have to get your dhandler to determine whether it should do $m->call_next or not. But still, I'm not sure I really understand what you're trying to do. Let me know if this advice is anywhere near the mark. -Oli
signature.asc
Description: OpenPGP digital signature
------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________ Mason-users mailing list Mason-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/mason-users
