2 use base qw(Class::Accessor::Fast Class::Data::Inheritable);
3 use UNIVERSAL::require;
7 use Maypole::Constants;
11 our $VERSION = '2.11';
13 # proposed privacy conventions:
14 # - no leading underscore - public to custom application code and plugins
15 # - single leading underscore - private to the main Maypole stack - *not*
17 # - double leading underscore - private to the current package
21 Maypole - MVC web application framework
25 The canonical example used in the Maypole documentation is the beer database:
31 # choose a frontend, initialise the config object, and load a plugin
32 use Maypole::Application qw/Relationship/;
34 # get the empty config object created by Maypole::Application
35 my $config = __PACKAGE__->config;
38 $config->uri_base("http://localhost/beerdb");
39 $config->template_root("/path/to/templates");
40 $config->rows_per_page(10);
41 $config->display_tables([qw/beer brewery pub style/]);
44 $config->relationships([
45 "a brewery produces beers",
46 "a style defines beers",
47 "a pub has beers on handpumps",
51 BeerDB::Brewery->untaint_columns( printable => [qw/name notes url/] );
52 BeerDB::Pub->untaint_columns( printable => [qw/name notes url/] );
53 BeerDB::Style->untaint_columns( printable => [qw/name notes/] );
54 BeerDB::Beer->untaint_columns(
55 printable => [qw/abv name price notes/],
56 integer => [qw/style brewery score/],
61 __PACKAGE__->setup("dbi:SQLite:t/beerdb.db");
67 This documents the Maypole request object. See the L<Maypole::Manual>, for a
68 detailed guide to using Maypole.
70 Maypole is a Perl web application framework similar to Java's struts. It is
71 essentially completely abstracted, and so doesn't know anything about
72 how to talk to the outside world.
74 To use it, you need to create a driver package which represents your entire
75 application. This is the C<BeerDB> package used as an example in the manual.
77 This needs to first use L<Maypole::Application> which will make your package
78 inherit from the appropriate platform driver such as C<Apache::MVC> or
79 C<CGI::Maypole>. Then, the driver calls C<setup>. This sets up the model classes
80 and configures your application. The default model class for Maypole uses
81 L<Class::DBI> to map a database to classes, but this can be changed by altering
82 configuration (B<before> calling setup.)
85 =head1 DOCUMENTATION AND SUPPORT
87 Note that some details in some of these resources may be out of date.
91 =item The Maypole Manual
93 The primary documentation is the Maypole manual. This lives in the
94 C<Maypole::Manual> pod documents included with the distribution.
98 Individual packages within the distribution contain (more or less) detailed
99 reference documentation for their API.
103 There are two mailing lists - maypole-devel and maypole-users - see
104 http://maypole.perl.org/?MailingList
106 =item The Maypole Wiki
108 The Maypole wiki provides a useful store of extra documentation -
109 http://maypole.perl.org
111 In particular, there's a FAQ (http://maypole.perl.org/?FAQ) and a cookbook
112 (http://maypole.perl.org/?Cookbook). Again, certain information on these pages
115 =item Web applications with Maypole
117 A tutorial written by Simon Cozens for YAPC::EU 2005 -
118 http://www.droogs.org/perl/maypole/maypole-tutorial.pdf [228KB].
120 =item A Database-Driven Web Application in 18 Lines of Code
122 By Paul Barry, published in Linux Journal, March 2005.
124 http://www.linuxjournal.com/article/7937
126 "From zero to Web-based database application in eight easy steps".
128 Maypole won a 2005 Linux Journal Editor's Choice Award
129 (http://www.linuxjournal.com/article/8293) after featuring in this article.
131 =item Build Web apps with Maypole
133 By Simon Cozens, on IBM's DeveloperWorks website, May 2004.
135 http://www-128.ibm.com/developerworks/linux/library/l-maypole/
137 =item Rapid Web Application Deployment with Maypole
139 By Simon Cozens, on O'Reilly's Perl website, April 2004.
141 http://www.perl.com/pub/a/2004/04/15/maypole.html
145 Some notes written by Simon Cozens. A little bit out of date, but still
146 very useful: http://www.droogs.org/perl/maypole/authentication.html
150 There's a refcard for the Maypole (and Class::DBI) APIs on the wiki -
151 http://maypole.perl.org/?CheatSheet. Probably a little out of date now - it's a
152 wiki, so feel free to fix any errors!
154 =item Plugins and add-ons
156 There are a large and growing number of plugins and other add-on modules
157 available on CPAN - http://search.cpan.org/search?query=maypole&mode=module
161 You can find a range of useful Maypole links, particularly to several thoughtful
162 blog entries, starting here: http://del.icio.us/search/?all=maypole
166 There are a couple of short reviews here:
167 http://cpanratings.perl.org/dist/Maypole
173 A couple of demos are available, sometimes with source code and configs.
177 =item http://maypole.perl.org/beerdb/
179 The standard BeerDB example, using the TT factory templates supplied in the
182 =item beerdb.riverside-cms.co.uk
184 The standard BeerDB example, running on Mason, using the factory templates
185 supplied in the L<MasonX::Maypole> distribution.
187 =item beerfb.riverside-cms.co.uk
189 A demo of L<Maypole::FormBuilder>. This site is running on the set of Mason
190 templates included in the L<Maypole::FormBuilder> distribution. See the
191 synopsis of L<Maypole::Plugin::FormBuilder> for an example driver
197 __PACKAGE__->mk_classdata($_) for qw( config init_done view_object );
199 __PACKAGE__->mk_accessors(
200 qw( params query objects model_class template_args output path
201 args action template error document_encoding content_type table
202 headers_in headers_out stash session user)
205 __PACKAGE__->config( Maypole::Config->new() );
207 __PACKAGE__->init_done(0);
209 =head1 HOOKABLE METHODS
211 As a framework, Maypole provides a number of B<hooks> - methods that are
212 intended to be overridden. Some of these methods come with useful default
213 behaviour, others do nothing by default. Hooks include:
239 sub My::App::debug {1}
241 Returns the debugging flag. Override this in your application class to
242 enable/disable debugging.
244 You can also set the C<debug> flag via L<Maypole::Application>.
252 Returns the L<Maypole::Config> object
256 My::App->setup($data_source, $user, $password, \%attr);
258 Initialise the Maypole application and plugins and model classes - see
259 L<Maypole::Manual::Plugins>.
261 If your model is based on L<Maypole::Model::CDBI>, the C<\%attr> hashref can
262 contain options that are passed directly to L<Class::DBI::Loader>, to control
263 how the model hierarchy is constructed.
265 Your application should call this B<after> setting up configuration data via
274 $class->setup_model(@_);
279 Called by C<setup>. This method builds the Maypole model hierarchy.
281 A likely target for over-riding, if you need to build a customised model.
283 This method also ensures any code in custom model classes is loaded, so you
284 don't need to load them in the driver.
292 $class = ref $class if ref $class;
294 my $config = $class->config;
296 $config->model || $config->model('Maypole::Model::CDBI');
298 $config->model->require or die sprintf
299 "Couldn't load the model class %s: %s", $config->model, $@;
301 # among other things, this populates $config->classes
302 $config->model->setup_database($config, $class, @_);
304 foreach my $subclass ( @{ $config->classes } )
307 unshift @{ $subclass . "::ISA" }, $config->model;
309 # Load custom model code, if it exists - nb this must happen after the
310 # unshift, to allow code attributes to work, but before adopt(),
311 # in case adopt() calls overridden methods on $subclass
312 $class->load_model_subclass($subclass);
314 $config->model->adopt($subclass) if $config->model->can("adopt");
316 # eval "use $subclass";
317 # die "Error loading $subclass: $@"
318 # if $@ and $@ !~ /Can\'t locate \S+ in \@INC/;
322 =item load_model_subclass($subclass)
324 This method is called from C<setup_model()>. It attempts to load the
325 C<$subclass> package, if one exists. So if you make a customized C<BeerDB::Beer>
326 package, you don't need to explicitly load it.
328 If, perhaps during development, you don't want to load up custom classes, you
329 can override this method and load them manually.
333 sub load_model_subclass
335 my ($class, $subclass) = @_;
337 my $config = $class->config;
339 # Load any external files for the model base class or subclasses
340 # (e.g. BeerDB/DBI.pm or BeerDB/Beer.pm) based on code borrowed from
341 # Maypole::Plugin::Loader and Class::DBI.
342 if ( $subclass->require )
344 warn "Loaded external module for '$subclass'\n" if $class->debug > 1;
348 (my $filename = $subclass) =~ s!::!/!g;
349 die "Loading '$subclass' failed: $@\n"
350 unless $@ =~ /Can\'t locate \Q$filename\E\.pm/;
351 warn "Did not find external module for '$subclass'\n"
352 if $class->debug > 1;
358 Loads the view class and instantiates the view object.
360 You should not call this directly, but you may wish to override this to add
361 application-specific initialisation - see L<Maypole::Manual::Plugins>.
368 my $config = $class->config;
369 $config->view || $config->view("Maypole::View::TT");
370 $config->view->require;
371 die "Couldn't load the view class " . $config->view . ": $@" if $@;
372 $config->display_tables
373 || $config->display_tables( $class->config->tables );
374 $class->view_object( $class->config->view->new );
375 $class->init_done(1);
380 Constructs a very minimal new Maypole request object.
390 config => $class->config,
398 Get/set the Maypole::View object
402 =head1 INSTANCE METHODS
410 This method sets up the class if it's not done yet, sets some defaults and
411 leaves the dirty work to C<handler_guts>.
415 # handler() has a method attribute so that mod_perl will invoke
416 # BeerDB->handler() as a method rather than a plain function
417 # BeerDB::handler() and so this inherited implementation will be
418 # found. See e.g. "Practical mod_perl" by Bekman & Cholet for
419 # more information <http://modperlbook.org/html/ch25_01.html>
422 # See Maypole::Workflow before trying to understand this.
423 my ($class, $req) = @_;
425 $class->init unless $class->init_done;
427 my $self = $class->new;
429 # initialise the request
430 $self->headers_out(Maypole::Headers->new);
431 $self->get_request($req);
432 $self->parse_location;
434 # hook useful for declining static requests e.g. images, or perhaps for
435 # sanitizing request parameters
436 my $status = $self->start_request_hook;
437 return $status unless $status == Maypole::Constants::OK();
439 $self->session($self->get_session);
440 $self->user($self->get_user);
442 $status = $self->handler_guts;
444 # moving this here causes unit test failures - need to check why
445 # before committing the move
446 #$status = $self->__call_process_view unless $self->output;
448 return $status unless $status == OK;
450 # TODO: require send_output to return a status code
458 This is the main request handling method and calls various methods to handle the
459 request/response and defines the workflow within Maypole.
461 B<Currently undocumented and liable to be refactored without warning>.
465 # The root of all evil
470 $self->__load_request_model;
472 my $applicable = $self->is_model_applicable;
474 $self->__setup_plain_template unless $applicable;
478 eval { $status = $self->call_authenticate };
480 if ( my $error = $@ )
482 $status = $self->call_exception($error);
486 warn "caught authenticate error: $error";
487 return $self->debug ?
488 $self->view_object->error($self, $error) : ERROR;
492 if ( $self->debug and $status != OK and $status != DECLINED )
494 $self->view_object->error( $self,
495 "Got unexpected status $status from calling authentication" );
498 return $status unless $status == OK;
500 # We run additional_data for every request
501 $self->additional_data;
505 eval { $self->model_class->process($self) };
507 if ( my $error = $@ )
509 $status = $self->call_exception($error);
513 warn "caught model error: $error";
514 return $self->debug ?
515 $self->view_object->error($self, $error) : ERROR;
520 # less frequent path - perhaps output has been set to an error message
521 return OK if $self->output;
523 # normal path - no output has been generated yet
524 return $self->__call_process_view;
527 sub __load_request_model
530 $self->model_class( $self->config->model->class_of($self, $self->table) );
533 # is_applicable() returned false, so set up a plain template. Model processing
534 # will be skipped, but need to remove the model anyway so the template can't
536 sub __setup_plain_template
540 # It's just a plain template
541 $self->model_class(undef);
543 my $path = $self->path;
544 $path =~ s{/$}{}; # De-absolutify
547 $self->template($self->path);
550 # The model has been processed or skipped (if is_applicable returned false),
551 # any exceptions have been handled, and there's no content in $self->output
552 sub __call_process_view
558 eval { $status = $self->view_object->process($self) };
560 if ( my $error = $@ )
562 $status = $self->call_exception($error);
566 warn "caught view error: $error" if $self->debug;
567 return $self->debug ?
568 $self->view_object->error($self, $error) : ERROR;
577 You should only need to define this method if you are writing a new
578 Maypole backend. It should return something that looks like an Apache
579 or CGI request object, it defaults to blank.
587 Turns the backend request (e.g. Apache::MVC, Maypole, CGI) into a Maypole
588 request. It does this by setting the C<path>, and invoking C<parse_path> and
591 You should only need to define this method if you are writing a new Maypole
598 die "parse_location is a virtual method. Do not use Maypole directly; " .
599 "use Apache::MVC or similar";
602 =item start_request_hook
604 This is called immediately after setting up the basic request. The default
605 method simply returns C<Maypole::Constants::OK>.
607 Any other return value causes Maypole to abort further processing of the
608 request. This is useful for filtering out requests for static files, e.g.
609 images, which should not be processed by Maypole or by the templating engine:
611 sub start_request_hook
615 return Maypole::Constants::DECLINED if $r->path =~ /\.jpg$/;
616 return Maypole::Constants::OK;
621 sub start_request_hook { Maypole::Constants::OK }
625 B<This method is deprecated> as of version 2.11. If you have overridden it,
626 please override C<is_model_applicable> instead, and change the return type
627 from a Maypole:Constant to a true/false value.
629 Returns a Maypole::Constant to indicate whether the request is valid.
631 =item is_model_applicable
633 Returns true or false to indicate whether the request is valid.
635 The default implementation checks that C<< $r->table >> is publicly
636 accessible and that the model class is configured to handle the
641 sub is_model_applicable
645 # cater for applications that are using obsolete version
646 if ($self->can('is_applicable'))
648 warn "DEPRECATION WARNING: rewrite is_applicable to the interface ".
649 "of Maypole::is_model_applicable\n";
650 return $self->is_applicable == OK;
653 # Establish which tables should be processed by the model
654 my $config = $self->config;
656 $config->ok_tables || $config->ok_tables( $config->display_tables );
658 $config->ok_tables( { map { $_ => 1 } @{ $config->ok_tables } } )
659 if ref $config->ok_tables eq "ARRAY";
661 my $ok_tables = $config->ok_tables;
663 # Does this request concern a table to be processed by the model?
664 my $table = $self->table;
668 if (exists $ok_tables->{$table})
675 warn "We don't have that table ($table).\n"
676 . "Available tables are: "
677 . join( ",", keys %$ok_tables )
678 if $self->debug and not $ok_tables->{$table};
683 # Is the action public?
684 my $action = $self->action;
685 return 1 if $self->model_class->is_public($action);
687 warn "The action '$action' is not applicable to the table $table"
695 Called immediately after C<start_request_hook()>.
697 This method should return a session, which will be stored in the request's
698 C<session> attribute.
700 The default method is empty.
708 Called immediately after C<get_session>.
710 This method should return a user, which will be stored in the request's C<user>
713 The default method is empty.
719 =item call_authenticate
721 This method first checks if the relevant model class
722 can authenticate the user, or falls back to the default
723 authenticate method of your Maypole application.
727 sub call_authenticate
731 # Check if we have a model class with an authenticate() to delegate to
732 return $self->model_class->authenticate($self)
733 if $self->model_class and $self->model_class->can('authenticate');
735 # Interface consistency is a Good Thing -
736 # the invocant and the argument may one day be different things
737 # (i.e. controller and request), like they are when authenticate()
738 # is called on a model class (i.e. model and request)
739 return $self->authenticate($self);
744 Returns a Maypole::Constant to indicate whether the user is authenticated for
747 The default implementation returns C<OK>
751 sub authenticate { return OK }
756 This model is called to catch exceptions, first after authenticate, then after
757 processing the model class, and finally to check for exceptions from the view
760 This method first checks if the relevant model class
761 can handle exceptions the user, or falls back to the default
762 exception method of your Maypole application.
768 my ($self, $error) = @_;
770 # Check if we have a model class with an exception() to delegate to
771 if ( $self->model_class && $self->model_class->can('exception') )
773 my $status = $self->model_class->exception( $self, $error );
774 return $status if $status == OK;
777 return $self->exception($error);
783 This method is called if any exceptions are raised during the authentication or
784 model/view processing. It should accept the exception as a parameter and return
785 a Maypole::Constant to indicate whether the request should continue to be
790 sub exception { return ERROR }
792 =item additional_data
794 Called before the model processes the request, this method gives you a chance to
795 do some processing for each request, for example, manipulating C<template_args>.
799 sub additional_data { }
803 Sends the output and additional headers to the user.
808 die "send_output is a virtual method. Do not use Maypole directly; use Apache::MVC or similar";
816 =head2 Path processing and manipulation
822 Returns the request path
826 Parses the request path and sets the C<args>, C<action> and C<table>
827 properties. Calls C<preprocess_path> before parsing path and setting properties.
835 # Previous versions unconditionally set table, action and args to whatever
836 # was in @pi (or else to defaults, if @pi is empty).
837 # Adding preprocess_path(), and then setting table, action and args
838 # conditionally, broke lots of tests, hence this:
839 $self->$_(undef) for qw/action table args/;
841 $self->preprocess_path;
842 $self->path || $self->path('frontpage');
844 my @pi = grep {length} split '/', $self->path;
847 $self->table || $self->table(shift @pi);
848 $self->action || $self->action( shift @pi or 'index' );
849 $self->args || $self->args(\@pi);
852 =item preprocess_path
854 Sometimes when you don't want to rewrite or over-ride parse_path but
855 want to rewrite urls or extract data from them before it is parsed.
857 This method is called after parse_location has populated the request
858 information and before parse_path has populated the model and action
859 information, and is passed the request object.
861 You can set action, args or table in this method and parse_path will
862 then leave those values in place or populate them if not present
866 sub preprocess_path { };
868 =item make_path( %args or \%args or @args )
870 This is the counterpart to C<parse_path>. It generates a path to use
871 in links, form actions etc. To implement your own path scheme, just override
872 this method and C<parse_path>.
874 %args = ( table => $table,
876 additional => $additional, # optional - generally an object ID
879 \%args = as above, but a ref
881 @args = ( $table, $action, $additional ); # $additional is optional
883 C<id> can be used as an alternative key to C<additional>.
885 C<$additional> can be a string, an arrayref, or a hashref. An arrayref is
886 expanded into extra path elements, whereas a hashref is translated into a query
897 if (@_ == 1 and ref $_[0] and ref $_[0] eq 'HASH')
901 elsif ( @_ > 1 and @_ < 4 )
903 $args{table} = shift;
904 $args{action} = shift;
905 $args{additional} = shift;
912 do { die "no $_" unless $args{$_} } for qw( table action );
914 my $additional = $args{additional} || $args{id};
920 # if $additional is a href, make_uri() will transform it into a query
921 @add = (ref $additional eq 'ARRAY') ? @$additional : ($additional);
924 my $uri = $r->make_uri($args{table}, $args{action}, @add);
926 return $uri->as_string;
931 =item make_uri( @segments )
933 Make a L<URI> object given table, action etc. Automatically adds
936 If the final element in C<@segments> is a hash ref, C<make_uri> will render it
943 my ($r, @segments) = @_;
945 my $query = (ref $segments[-1] eq 'HASH') ? pop(@segments) : undef;
947 my $base = $r->config->uri_base;
950 my $uri = URI->new($base);
951 $uri->path_segments($uri->path_segments, grep {length} @segments);
953 my $abs_uri = $uri->abs('/');
954 $abs_uri->query_form($query) if $query;
960 Turns post data and query string paramaters into a hash of C<params>.
962 You should only need to define this method if you are writing a new Maypole
969 die "parse_args() is a virtual method. Do not use Maypole directly; ".
970 "use Apache::MVC or similar";
973 =item get_template_root
975 Implementation-specific path to template root.
977 You should only need to define this method if you are writing a new Maypole
978 backend. Otherwise, see L<Maypole::Config/"template_root">
982 sub get_template_root {'.'}
986 =head2 Request properties
992 Returns the perl package name that will serve as the model for the
993 request. It corresponds to the request C<table> attribute.
998 Get/set a list of model objects. The objects will be accessible in the view
1001 If the first item in C<$self-E<gt>args> can be C<retrieve()>d by the model
1002 class, it will be removed from C<args> and the retrieved object will be added to
1003 the C<objects> list. See L<Maypole::Model> for more information.
1007 $self->template_args->{foo} = 'bar';
1009 Get/set a hash of template variables.
1013 A place to put custom application data. Not used by Maypole itself.
1017 Get/set the template to be used by the view. By default, it returns
1018 C<$self-E<gt>action>
1023 Get/set a request error
1027 Get/set the response output. This is usually populated by the view class. You
1028 can skip view processing by setting the C<output>.
1032 The table part of the Maypole request path
1036 The action part of the Maypole request path
1040 A list of remaining parts of the request path after table and action
1046 A L<Maypole::Headers> object containing HTTP headers for the request
1050 A L<HTTP::Headers> object that contains HTTP headers for the output
1052 =item document_encoding
1054 Get/set the output encoding. Default: utf-8.
1058 Get/set the output content type. Default: text/html
1062 Returns the protocol the request was made with, i.e. https
1067 die "get_protocol is a virtual method. Do not use Maypole directly; use Apache::MVC or similar";
1072 =head2 Request parameters
1074 The source of the parameters may vary depending on the Maypole backend, but they
1075 are usually populated from request query string and POST data.
1077 Maypole supplies several approaches for accessing the request parameters. Note
1078 that the current implementation (via a hashref) of C<query> and C<params> is
1079 likely to change in a future version of Maypole. So avoid direct access to these
1082 $r->{params}->{foo} # bad
1083 $r->params->{foo} # better
1085 $r->{query}->{foo} # bad
1086 $r->query->{foo} # better
1088 $r->param('foo') # best
1094 An accessor (get or set) for request parameters. It behaves similarly to
1095 CGI::param() for accessing CGI parameters, i.e.
1097 $r->param # returns list of keys
1098 $r->param($key) # returns value for $key
1099 $r->param($key => $value) # returns old value, sets to new value
1105 my ($self, $key) = (shift, shift);
1107 return keys %{$self->params} unless defined $key;
1109 return unless exists $self->params->{$key};
1111 my $val = $self->params->{$key};
1115 my $new_val = shift;
1116 $self->params->{$key} = $new_val;
1119 return ref $val ? @$val : ($val) if wantarray;
1121 return ref $val ? $val->[0] : $val;
1127 Returns a hashref of request parameters.
1129 B<Note:> Where muliple values of a parameter were supplied, the C<params> value
1130 will be an array reference.
1134 Alias for C<params>.
1138 =head3 Utility methods
1142 =item redirect_request
1144 Sets output headers to redirect based on the arguments provided
1146 Accepts either a single argument of the full url to redirect to, or a hash of
1149 $r->redirect_request('http://www.example.com/path');
1153 $r->redirect_request(protocol=>'https', domain=>'www.example.com', path=>'/path/file?arguments', status=>'302', url=>'..');
1155 The named parameters are protocol, domain, path, status and url
1157 Only 1 named parameter is required but other than url, they can be combined as
1158 required and current values (from the request) will be used in place of any
1159 missing arguments. The url argument must be a full url including protocol and
1160 can only be combined with status.
1164 sub redirect_request {
1165 die "redirect_request is a virtual method. Do not use Maypole directly; use Apache::MVC or similar";
1168 =item redirect_internal_request
1172 sub redirect_internal_request {
1177 =item make_random_id
1179 returns a unique id for this request can be used to prevent or detect repeat
1184 # Session and Repeat Submission Handling
1185 sub make_random_id {
1186 use Maypole::Session;
1187 return Maypole::Session::generate_unique_id();
1192 =head1 SEQUENCE DIAGRAMS
1194 See L<Maypole::Manual::Workflow> for a detailed discussion of the sequence of
1195 calls during processing of a request. This is a brief summary:
1199 BeerDB Maypole::Model::CDBI
1203 || setup_model | setup_database() creates
1204 ||------+ | a subclass of the Model
1205 |||<----+ | for each table
1207 ||| setup_database | |
1208 |||--------------------->|| 'create' *
1209 ||| ||----------> $subclass
1211 ||| load_model_subclass | |
1212 foreach |||------+ ($subclass) | |
1213 $subclass ||||<----+ | require |
1214 ||||--------------------------------------->|
1216 ||| adopt($subclass) | |
1217 |||--------------------->|| |
1222 || | new | view_object: e.g.
1223 ||---------------------------------------------> Maypole::View::TT
1235 BeerDB Model $subclass view_object
1238 o-------->| new | | |
1239 |-----> r:BeerDB | | |
1243 | ||-----+ parse_location | | |
1246 | ||-----+ start_request_hook | | |
1249 | ||-----+ get_session | | |
1252 | ||-----+ get_user | | |
1255 | ||-----+ handler_guts | | |
1257 | ||| class_of($table) | | |
1258 | |||------------------------->|| | |
1259 | ||| $subclass || | |
1260 | |||<-------------------------|| | |
1262 | |||-----+ is_model_applicable| | |
1265 | |||-----+ call_authenticate | | |
1268 | |||-----+ additional_data | | |
1271 | |||--------------------------------->|| fetch_objects
1279 | |||------------------------------------------->|| template
1283 | || send_output | | |
1287 <------------------|| | | |
1298 There's more documentation, examples, and information on our mailing lists
1299 at the Maypole web site:
1301 L<http://maypole.perl.org/>
1303 L<Maypole::Application>, L<Apache::MVC>, L<CGI::Maypole>.
1307 Maypole is currently maintained by Aaron Trevena, David Baird, Dave Howorth and
1310 =head1 AUTHOR EMERITUS
1312 Simon Cozens, C<simon#cpan.org>
1314 Simon Flack maintained Maypole from 2.05 to 2.09
1316 Sebastian Riedel, C<sri#oook.de> maintained Maypole from 1.99_01 to 2.04
1320 Sebastian Riedel, Danijel Milicevic, Dave Slack, Jesse Sheidlower, Jody Belka,
1321 Marcus Ramberg, Mickael Joanne, Randal Schwartz, Simon Flack, Steve Simms,
1322 Veljko Vidovic and all the others who've helped.
1326 You may distribute this code under the same terms as Perl itself.