On 10/22/07, Glendon Solsberry <[EMAIL PROTECTED]> wrote:
>
>
> Is there any way to see that call-chain?
I'm not sure. Maybe a Mason guru can chime in here. I don't think
$m->callers() reveals the component inheritance tree, just the components
that are running.
> The biggest problem that I'm having, is that the output works correctly on
> the
> first page (/), and on a subfolder (/Camera Import). When I hit an offset
> page
> (/offset/1 or /Camera Import/offset/1), the problem arises. I'm just
> trying to
> debug what's actually happening, so that I can try to put things in the
> right
> places.
That sounds like you have a dhandler handling the "offset" urls, is that the
case? I think that component inheritance ends at the dhandler in that case
(the dhandler is the request_comp()), so components called by your dhandler
code do not get the chance to be SELF. In that case, any SELF:method would
need to be declared in the dhandler (or autohandler).
Question to the list: is there a way for the dhandler to alter the
inheritance chain so that components called by the dhandler can be SELF? Or
am I way off the mark here?
-Vince
-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
Mason-users mailing list
Mason-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mason-users
