Thanks for the information, I do appreciate it. I saw that plugin, and will plan to try it, as it seems it may be my only option. My problem is that the existing application has a lot of VirtualHosts, all defined in perl. This plugin only works inside the proper VHost. Since one may not know which VHost is being invoked (especially new developers ramping up), just means one would have to edit as many hashes to put the config in for the CompDebug; a bit too empirical. I was hoping for a more systemic way of handling this.
Thanks again, - Jeff ----- Original Message ---- From: Marius Feraru <[EMAIL PROTECTED]> To: mason-users@lists.sourceforge.net Sent: Monday, October 6, 2008 1:54:00 PM Subject: Re: [Mason] Having trouble getting preprocess to work On Fri, Oct 3, 2008 at 06:10, Jeff Nokes <[EMAIL PROTECTED]> wrote: > I'm trying to create a way for developers on our Mason app, to be able to > dump to our apache error_log, the full component execution chain for any > request that Mason handles. > > # Take the component passed in, and add an <%init> block to the > beginning of it, that will print out the following component information Sorry, but IMHO this sounds like a really twisted way to achieve your goal. :) You might find the attached plugin useful. ;-) -- altblue ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ _______________________________________________ Mason-users mailing list Mason-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/mason-users
