package Apache::MVC;
-use base qw(Class::Accessor Class::Data::Inheritable);
-use attributes ();
-use Class::DBI::Loader;
+use base 'Maypole';
+use Apache;
+use Apache::Request;
use strict;
use warnings;
-
-__PACKAGE__->mk_classdata(qw( _config init_done view_object ));
-__PACKAGE__->mk_accessors ( qw( config ar params objects model_class args ));
-__PACKAGE__->config({});
-__PACKAGE__->init_done(0);
-
-# This is really dirty.
-sub config {
- my $self = shift;
- if (ref $self) { return $self->_config_accessor(@_) }
- return $self->_config(@_);
-}
-
-sub set_database {
- my ($calling_class, $dsn) = @_;
- $calling_class = ref $calling_class if ref $calling_class;
- $calling_class->config->{dsn} = $dsn;
- $calling_class->config->{loader} = Class::DBI::Loader->new(
- namespace => $calling_class,
- dsn => $dsn
- );
-}
-
-sub init {
- my $class = shift;
- my $config = $class->config;
- $config->{model} ||= "Apache::MVC::Model::CDBI";
- $config->{view} ||= "Apache::MVC::View::TT";
- $config->{classes} = [ $class->config->{loader}->classes ];
- $config->{display_tables} ||= [ $class->config->{loader}->tables ];
- for my $class (@{$config->{classes}}) {
- no strict 'refs';
- push @{$class."::ISA"}, $class->config->{model};
- }
- $class->view_object($class->config->{view}->new);
-
-}
-
-sub class_of {
- my ($self, $table) = @_;
- return $self->config->{loader}->_table2class($table);
-}
-
-sub handler {
- # See Apache::MVC::Workflow before trying to understand this.
- my $class = (caller(0))[0];
- $class->init unless $class->init_done;
- my $r = bless { config => $class->config }, $class;
- $r->get_request();
- $r->parse_location();
- $r->model_class($r->class_of($r->{table}));
- my $status = $r->is_applicable;
- return $status unless $status == 200;
- $status = $r->call_authenticate;
- return $status unless $status == 200;
- $r->find_objects();
- $r->additional_data();
- $r->class->process($r);
-}
+our $VERSION = "0.3";
sub get_request {
- my $self = shift;
- require Apache; require Apache::Request;
- $self->{ar} = Apache::Request->new(Apache->request);
+ shift->{ar} = Apache::Request->new(Apache->request);
}
sub parse_location {
my $self = shift;
- my @pi = split /\//, $self->{ar}->uri();
+ $self->{path} = $self->{ar}->uri;
+ my $loc = $self->{ar}->location;
+ $self->{path} =~ s/^$loc//; # I shouldn't need to do this?
+ $self->{path} ||= "frontpage";
+ my @pi = split /\//, $self->{path};
shift @pi while @pi and !$pi[0];
$self->{table} = shift @pi;
$self->{action} = shift @pi;
$self->{args} = \@pi;
-}
-sub is_applicable {
- my $self = shift;
- require Apache::Constants;
- Apache::Constants->import(":common");
- my $config = $self->config;
- my %ok = map {$_ => 1} @{$config->{displaying_tables}};
- return DECLINED() unless exists $ok{$self->{table}};
-
- # Does the action method exist?
- my $cv = $self->model_class->can($self->{action});
- return DECLINED() unless $cv;
-
- # Is it exported?
- my $attribs = join " ", attributes::get($cv);
- return DECLINED() unless $attribs =~ /\b(Exported|Class|Single|Multiple)\b/i;
- return OK();
+ $self->{params} = { $self->{ar}->content };
+ $self->{query} = { $self->{ar}->args };
}
+1;
-sub authenticate { return 200 }
+=head1 NAME
-1;
+Apache::MVC - Apache front-end to Maypole
+
+=head1 SYNOPSIS
+
+ package BeerDB;
+ use base 'Apache::MVC';
+ BeerDB->setup("dbi:mysql:beerdb");
+ BeerDB->config->{uri_base} = "http://your.site/";
+ BeerDB->config->{display_tables} = [qw[beer brewery pub style]];
+ # Now set up your database:
+ # has-a relationships
+ # untaint columns
+
+ 1;
+
+=head1 DESCRIPTION
+
+Maypole is a Perl web application framework to Java's struts. It is
+essentially completely abstracted, and so doesn't know anything about
+how to talk to the outside world. C<Apache::MVC> is a mod_perl based
+subclass of Maypole.
+
+To use it, you need to create a package which represents your entire
+application. In our example above, this is the C<BeerDB> package.
+
+This needs to first inherit from C<Apache::MVC>, and then call setup.
+This will give your package an Apache-compatible C<handler> subroutine,
+and then pass any parameters onto the C<setup_database> method of the
+model class. The default model class for Maypole uses L<Class::DBI> to
+map a database to classes, but this can be changed by messing with the
+configuration. (B<Before> calling setup.)
+
+Next, you should configure your application through the C<config>
+method. Configuration parameters at present are:
+
+=over
+
+=item uri_base
+
+You B<must> specify this; it is the base URI of the application, which
+will be used to construct links.
+
+=item display_tables
+
+If you do not want all of the tables in the database to be accessible,
+then set this to a list of only the ones you want to display
+
+=item rows_per_page
+
+List output is paged if you set this to a positive number of rows.
+
+=back
+
+You should also set up relationships between your classes, such that,
+for instance, calling C<brewery> on a C<BeerDB::Beer> object returns an
+object representing its associated brewery.
+
+For a full example, see the included "beer database" application.
+
+=head1 INSTALLATION
+
+Create a driver module like the one above.
+
+Put the following in your Apache config:
+
+ <Location /beer>
+ SetHandler perl-script
+ PerlHandler BeerDB
+ </Location>
+
+Copy the templates found in F<templates/factory> into the
+F<beer/factory> directory off the web root. When the designers get
+back to you with custom templates, they are to go in
+F<beer/custom>. If you need to do override templates on a
+database-table-by-table basis, put the new template in
+F<beer/I<table>>.
+
+This will automatically give you C<add>, C<edit>, C<list>, C<view> and
+C<delete> commands; for instance, a list of breweries, go to
+
+ http://your.site/beer/brewery/list
+
+For more information about how the system works and how to extend it,
+see L<Maypole>.
+
+=head1 AUTHOR
+
+Simon Cozens, C<simon@cpan.org>
+
+=head1 LICENSE
+
+You may distribute this code under the same terms as Perl itself.
projects / maypole.git / blobdiff