This documents the Maypole request object. See the Maypole::Manual, for a detailed guide to using Maypole. Maypole is a Perl web application framework similar to Java's struts. It is essentially completely abstracted, and so doesn't know anything abo...

This module is used to test Maypole sites without going through a web server or modifying them to use a CGI frontend. To use it, you should first either be in the template root for your Maypole site or set the environment variable "MAYPOLE_TEMPLATES"...

This is a CGI platform driver for Maypole. Your application can inherit from CGI::Maypole directly, but it is recommended that you use Maypole::Application. This module requires CGI::Simple which you will have to install yourself via CPAN or manually...

This module replaces Maypole's main handler in your application with one which uses "Cache::Cache" to cache request output. By default it uses "Cache::SharedMemoryCache" although this, and all other "Cache::Cache" options, can be changed using the "c...

This is a stand-alone HTTPD for running your Maypole Applications....

This is a stand-alone HTTPD for running your maypole Applications....

This class stores all configuration data for your Maypole application....

A frontend and view for Maypole, using Mason....

This class provides session related methods for Maypole such as unique id's for requests. Currently it provides only the generate_unique_id() function, by checking the id's generated by this function and included in submitted forms, it is possible to...

A convenience wrapper around "HTTP::Headers". Additional methods are provided to make the mutators less repetitive and wordy. For example: $r->headers_out->header(Content_Base => $r->config->uri_base); can be written as: $r->headers_out->set(Content_...

This subclass of Maypole allows you to integrate the results of a Maypole request into an existing request. You'll need to set up actions and templates which return fragments of HTML rather than entire pages, but once you've done that, you can use th...

This class defines constants for use with Maypole CONSTANTS OK DECLINED ERROR...

Maypole provides a great framework for simplifying the interaction between a UI and a database. But it provides very little support for simplifying the interface itself. Programmers are left to construct each form, widget by widget, using modules tha...

This is a universal frontend for mod_perl1, mod_perl2, HTML::Mason and CGI. Automatically determines the appropriate frontend for your environment (unless you want to use MasonX::Maypole, in which case include "MasonX" in the arguments). Loads plugin...

Builds a database and a simple application driver, ready to use in test scripts for Maypole plugins and components. Provides functions for installing resources (SQL files, configurations, templates), and for discovering the directories these resource...

This is the default view class for Maypole; it uses the Template Toolkit to fill in templates with the objects produced by Maypole's model classes. Please see the Maypole manual, and in particular, the view chapter for the template variables availabl...

This is the base class for Maypole view classes. This is an abstract class that defines the interface, and can't be used directly. process This is the entry point for the view. It templates the request and returns a "Maypole::Constant" indicate succe...

This is the base class for Maypole data models. This is an abstract class that defines the interface, and can't be used directly. process This is the engine of this module. Given the request object, it populates all the relevant variables and calls t...

This is a master model class which uses Class::DBI to do all the hard work of fetching rows and representing them as objects. It is a good model to copy if you're replacing it with other database abstraction modules. It implements a base set of metho...