apachemaopdacpheerlm-o1d01p.e1r~l2U-:s1:e0mr1o.dC1o~pn2et:rr:lim-bo2ud.t0ep.de2r:Pl:e-dr2ol.c0sD.:o2:c:au:pmdieo:nc:tsAa:pt:aiacophnie:2::A:ppaocrhtei2n:g:(p3o)rting(3)

NAME
       Apache2::porting - a helper module for modperl 1.0 to modperl 2.0
       porting

SSyynnooppssiiss
         # either add at the very beginning of startup.pl
         use Apache2::porting;

         # or httpd.conf
         PerlModule Apache2::porting

         # now issue requests and look at the errorlog file for hints

DDeessccrriippttiioonn
       "Apache2::porting" helps to port modperl 1.0 code to run under
       modperl 2.0. It doesn't provide any back-compatibility functionality,
       however it knows to trap methods calls that are no longer in the
       modperl 2.0 API and tell what should be used instead if at all. If you
       attempts to use modperl 2.0 methods without first loading the modules
       that contain them, it will tell you which modules you need to load.
       Finally if your code tries to load modules that no longer exist in
       modperl 2.0 it'll also tell you what are the modules that should be
       used instead.

       "Apache2::porting" communicates with users via the errorlog file.
       Everytime it traps a problem, it logs the solution (if it finds one) to
       the error log file. If you use this module coupled with
       "Apache2::Reload" you will be able to port your applications quickly
       without needing to restart the server on every modification.

       It starts to work only when child process start and doesn't work for
       the code that gets loaded at the server startup. This limitation is
       explained in the Culprits section.

       It relies heavily on "ModPerl::MethodLookup".  which can also be used
       manually to lookup things.

CCuullpprriittss
       "Apache2::porting" uses the "UNIVERSAL::AUTOLOAD" function to provide
       its functionality. However it seems to be impossible to create
       "UNIVERSAL::AUTOLOAD" at the server startup, Apache segfaults on
       restart. Therefore it performs the setting of "UNIVERSAL::AUTOLOAD"
       only during the childinit phase, when child processes start. As a
       result it can't help you with things that get preloaded at the server
       startup.

       If you know how to resolve this problem, please let us know. To
       reproduce the problem try to use an earlier phase, e.g.
       "PerlPostConfigHandler":

         Apache2::ServerUtil->server->pushhandlers(PerlPostConfigHandler => \&portingautoload);

       META: Though there is a better solution at work, which assigns AUTOLOAD
       for each class separately, instead of using UNIVERSAL. See the
       discussion on the dev list (hint: search the archive for EazyLife)

SSeeee AAllssoo
       modperl 2.0 documentation.

CCooppyyrriigghhtt
       modperl 2.0 and its core modules are copyrighted under The Apache
       Software License, Version 2.0.

AAuutthhoorrss
       The modperl development team and numerous contributors.



perl v5.a8p.a8chemodperl-101.1~2::mo2d00p5e-r1l0-22.00.2::docs::api::Apache2::porting(3)