X-Git-Url: https://git.decadent.org.uk/gitweb/?a=blobdiff_plain;f=lib%2FMaypole%2FManual%2FInheritance.pod;h=1c2fca93837bf4241cd341d1660fd0d2146a2dec;hb=672f0445d8c46ff29b0c6ebf18d30791c017260a;hp=2dd0eaf0f6e2048d2e6b4569eeebf9115c5afd68;hpb=1b05e3ca38fdb958cf9ced4d89e1478dc1e21257;p=maypole.git diff --git a/lib/Maypole/Manual/Inheritance.pod b/lib/Maypole/Manual/Inheritance.pod index 2dd0eaf..1c2fca9 100644 --- a/lib/Maypole/Manual/Inheritance.pod +++ b/lib/Maypole/Manual/Inheritance.pod @@ -238,6 +238,14 @@ C, then C, C, C, and C, before moving on to C and finally C. +B - if your Offline model overrides L methods, these methods +will B be overridden when called from the Maypole application, because the +Maypole model provides an alternative path to L which is searched +first. The solution is to place such methods in a separate package, e.g. +C. Place this B in the C<@ISA> of both +C and C. Note that C +does not itself need to inherit from L. + Methods defined in the Maypole model base class (C), override methods in the individual Offline table classes, and in the Offline model base class (C). @@ -262,3 +270,16 @@ Whatever label you prefer to use, this approach provides for clear separation of concerns between the underlying model and the web/user interface, and that's what it's all about. +=head1 AUTHOR + +David Baird, C<< >> + +=head1 COPYRIGHT & LICENSE + +Copyright 2005 David Baird, All Rights Reserved. + +This text is free documentation; you can redistribute it and/or modify it +under the same terms as the Perl documentation itself. + +=cut +