Hi Jeff - there are a lot of variables here, such as your use of  
virtual hosts and Perl-based configuration. You need to eliminate the  
variables, perhaps on a test server. Try a super-simple static  
configuration without virtual hosts and see if you can get  
MasonPreprocess to be honored in your object files. Then add things  
back one at a time.

Jon

On Oct 14, 2008, at 2:48 PM, Jeff Nokes wrote:

> Hi Jon,
> Sorry this took so long ...
>
> No, the code is not getting added to the object files, with my  
> preprocess config in the main apache config scope, or inside the  
> VirtualHosts.  Apache is not complaining about anything either.
>
> Also, I tried using the profile plugin, inside the VHosts, still, I  
> see nothing in the logs from this.
>
> Here is what is in my httpd.conf:
> -----------------------------
> PerlModule LO::Debug
> PerlSetVar MasonPreprocess "\&LO::Debug::trace_mason_request2"
>
> PerlModule MasonX::Profiler
> #PerlSetVar MasonPreamble "my $p = MasonX::Profiler->new($m, $r);"
>
>
> Here's what I have in my VirtualHosts (done in perl):
> -----------------------------
>    # http virtual host settings
>    $VirtualHost{"*:" . $self->http_port} =
>      [
>       {
>         DocumentRoot => $DocumentRoot,
>         ErrorLog => $ErrorLog,
>         CustomLog => $CustomLog,
>
>         # Nokes
>         ##PerlModule => ['MasonX::Profiler'],    #can't do this here  
> interestingly, can't even start up
>         PerlSetVar => [
>            [MasonPreprocess => '\&LO::Debug::trace_mason_request2'],
>            [MasonPreamble   => 'my $p = MasonX::Profiler->new($m,  
> $r);'],
>         ],
>       }
>      ];
>
>
>    # https virtual host settings
>    $VirtualHost{"*:" . $self->https_port} =[
>       {
>        SSLEngine => "on",
>        SSLCertificateFile => $self->ssl_cert,
>        SSLCertificateKeyFile => $self->ssl_key,
>        SetEnvIf => $self->ssl_setenvif,
>        SSLCipherSuite => $self->ssl_ciphersuite,
>        DocumentRoot => $DocumentRoot,
>        ErrorLog => $ErrorLog,
>        CustomLog => $self->ssl_custom_log,
>
>        # Nokes
>        ##PerlModule => ['MasonX::Profiler'],  # apache does not like  
> this
>        PerlSetVar => [
>           [MasonPreprocess => '\&LO::Debug::trace_mason_request2'],
>           [MasonPreamble   => 'my $p = MasonX::Profiler->new($m,  
> $r);'],
>        ],
>       }
>    ];
>
>
> I'm not an expert with the Perl based apache config, so this may be  
> the issue.  But, apache seems to be happy with what I have above.   
> Any assistance you can offer would be greatly appreciated.
>
> Thanks,
> - Jeff
>
>
>
>
>
> ----- Original Message ----
> From: Jonathan Swartz <[EMAIL PROTECTED]>
> To: Jeff Nokes <[EMAIL PROTECTED]>
> Cc: Marius Feraru <[EMAIL PROTECTED]>; mason-users@lists.sourceforge.net
> Sent: Monday, October 6, 2008 7:31:12 PM
> Subject: Re: [Mason] Having trouble getting preprocess to work
>
> Hi Jeff,
>
> Take a look at the object files of your components to see if the line
> is actually being added.
>
> Jon
>
> On Oct 6, 2008, at 4:02 PM, Jeff Nokes wrote:
>
>> 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
>>
>


-------------------------------------------------------------------------
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

Reply via email to