UPDATE: I solved the problem. It was definately user error on my part.
For anyone interested's edification. The thing that prompted me to roll out the apache was enabling ssl. When I put added the SSL stuff to my Sage.pm, I accidently had two __PACKAGE__->setup calls. Wacky Hijinks Ensued.


I have searched everywhere (including super search) for an answer to my issue, but I'm coming up blank.
I have a Catalyst application (under Active State). I am using DBIC::Schema for my Model. All is well under the built-in webserver, but when I try to run it under Apache, it fails on startup with:
Can't locate Sage/Model/SageDB/Roles.pm in @INC
Apparently, it is trying to load the Schema classes from actual files, when they are built automagically at run-time by DBIC::Schema.
I am not sure what parts of my configuration are needed to track this down, but I will be happy to attach any of it. I was just wondering if anyone had run accross this issue before.

Pete


Here is my httpd.conf setup:

<Perl>
use lib qw(c:/Sage/lib/);
</Perl>

PerlConfigRequire c:/Sage/lib/ApacheConfig.pm 
PerlModule Sage

<VirtualHost *>
        ServerName   Sage.localhost.com
        DocumentRoot c:/Sage/root
        
        <Location />
            SetHandler       perl-script
            PerlHandler      Sage
        </Location>
        
        <Location /static>
            SetHandler      default-handler
        </Location>
</VirtualHost>
[download]

The rest of my configuration is straight out of the tutorials.