package Maypole;
-use base qw(Class::Accessor::FAST Class::Data::Inheritable);
+use base qw(Class::Accessor::Fast Class::Data::Inheritable);
use attributes ();
use UNIVERSAL::require;
use strict;
if ( my $error = $@ ) {
$status = $r->call_exception($error);
if ( $status != OK ) {
- warn "caught view error: $error";
+ warn "caught view error: $error" if $r->debug;
return $r->debug ? $r->view_object->error( $r, $error ) : ERROR;
}
}
this:
package ProductDatabase;
- use base 'Apache::MVC';
+ use base 'Maypole::Application';
__PACKAGE__->set_database("dbi:mysql:products");
ProductDatabase->config->uri_base = "http://your.site/catalogue/";
ProductDatabase::Product->has_a("category" => ProductDatabase::Category);
class which does not specify how to communicate with the outside world.
The most popular subclass of Maypole is L<Apache::MVC>, which interfaces
the Maypole framework to Apache mod_perl; another important one is
-L<CGI::Maypole>.
+L<CGI::Maypole>. However, if you just don't care, use Maypole::Application,
+and it will choose the right one for you.
If you are implementing Maypole subclasses, you need to provide at least
the C<parse_location> and C<send_output> methods. You may also want to
http://maypole.simon-cozens.org/
-L<Apache::MVC>, L<CGI::Maypole>.
+L<Maypole::Application>,L<Apache::MVC>, L<CGI::Maypole>.
=head1 MAINTAINER