3 Catalyst::Manual::Intro - Introduction to Catalyst
7 This is a brief introduction to Catalyst. It explains the most important
8 features of how Catalyst works and shows how to get a simple application
9 up and running quickly. For an introduction (without code) to Catalyst
10 itself, and why you should be using it, see L<Catalyst::Manual::About>.
12 =head2 What is Catalyst?
14 Catalyst is an elegant web application framework, extremely flexible yet
15 extremely simple. It's similar to Ruby on Rails, Spring (Java), and
16 L<Maypole>, upon which it was originally based.
20 Catalyst follows the Model-View-Controller (MVC) design pattern,
21 allowing you to easily separate concerns, like content, presentation,
22 and flow control, into separate modules. This separation allows you to
23 modify code that handles one concern without affecting code that handles
24 the others. Catalyst promotes the re-use of existing Perl modules that
25 already handle common web application concerns well.
27 Here's how the M, V, and C map to those concerns, with examples of
28 well-known Perl modules you may want to use for each.
34 Access and modify content (data). L<DBIx::Class>, L<Class::DBI>,
35 L<Plucene>, L<Net::LDAP>...
39 Present content to the user. L<Template Toolkit|Template>,
40 L<Mason|HTML::Mason>, L<HTML::Template>...
44 Control the whole request phase, check parameters, dispatch actions, flow
45 control. Catalyst itself!
49 If you're unfamiliar with MVC and design patterns, you may want to check
50 out the original book on the subject, I<Design Patterns>, by Gamma,
51 Helm, Johnson, and Vlissides, also known as the Gang of Four (GoF).
52 Many, many web application frameworks are based on MVC, including all
57 Catalyst is much more flexible than many other frameworks. We'll talk
58 more about this later, but rest assured you can use your favorite Perl
59 modules with Catalyst.
63 =item * B<Multiple Models, Views, and Controllers>
65 To build a Catalyst application, you handle each type of concern inside
66 special modules called L</Components>. Often this code will be very
67 simple, just calling out to Perl modules like those listed above under
68 L</MVC>. Catalyst handles these components in a very flexible way. Use
69 as many Models, Views, and Controllers as you like, using as many
70 different Perl modules as you like, all in the same application. Want to
71 manipulate multiple databases, and retrieve some data via LDAP? No
72 problem. Want to present data from the same Model using L<Template
73 Toolkit|Template> and L<PDF::Template>? Easy.
75 =item * B<Reuseable Components>
77 Not only does Catalyst promote the re-use of already existing Perl
78 modules, it also allows you to re-use your Catalyst components in
79 multiple Catalyst applications.
81 =item * B<Unrestrained URL-to-Action Dispatching>
83 Catalyst allows you to dispatch any URLs to any application L</Actions>,
84 even through regular expressions! Unlike most other frameworks, it
85 doesn't require mod_rewrite or class and method names in URLs.
87 With Catalyst you register your actions and address them directly. For
91 my ( $self, $context ) = @_;
92 $context->response->body('Hello World!');
95 Now http://localhost:3000/hello prints "Hello World!".
97 =item * B<Support for CGI, mod_perl, Apache::Request>
99 Use L<Catalyst::Engine::Apache> or L<Catalyst::Engine::CGI>.
105 The best part is that Catalyst implements all this flexibility in a very
110 =item * B<Building Block Interface>
112 Components interoperate very smoothly. For example, Catalyst
113 automatically makes a L</Context> object available to every
114 component. Via the context, you can access the request object, share
115 data between components, and control the flow of your
116 application. Building a Catalyst application feels a lot like snapping
117 together toy building blocks, and everything just works.
119 =item * B<Component Auto-Discovery>
121 No need to C<use> all of your components. Catalyst automatically finds
124 =item * B<Pre-Built Components for Popular Modules>
126 See L<Catalyst::Model::DBIC::Schema> for L<DBIx::Class>, or
127 L<Catalyst::View::TT> for L<Template Toolkit|Template>.
129 =item * B<Built-in Test Framework>
131 Catalyst comes with a built-in, lightweight http server and test
132 framework, making it easy to test applications from the command line.
134 =item * B<Helper Scripts>
136 Catalyst provides helper scripts to quickly generate running starter
137 code for components and unit tests. See L<Catalyst::Helper>.
143 Here's how to install Catalyst and get a simple application up and
144 running, using the helper scripts described above.
148 $ perl -MCPAN -e 'install Task::Catalyst'
155 $ script/myapp_create.pl controller Library::Login
159 $ script/myapp_server.pl
161 Now visit these locations with your favorite browser or user agent to see
164 (NOTE: Although we create a controller here, we don't actually use it.
165 Both of these URLs should take you to the welcome page.)
170 =item http://localhost:3000/
172 =item http://localhost:3000/library/login/
180 Let's see how Catalyst works, by taking a closer look at the components
181 and other parts of a Catalyst application.
183 =head3 Application Class
185 In addition to the Model, View, and Controller components, there's a
186 single class that represents your application itself. This is where you
187 configure your application, load plugins, and extend Catalyst.
192 use Catalyst qw/-Debug/;
195 name => 'My Application',
197 # You can put anything else you want in here:
198 my_configuration_variable => 'something',
206 The name of your application.
210 Optionally, you can specify a B<root> parameter for templates and static
211 data. If omitted, Catalyst will try to auto-detect the directory's
212 location. You can define as many parameters as you want for plugins or
213 whatever you need. You can access them anywhere in your application via
214 C<$context-E<gt>config-E<gt>{$param_name}>.
218 Catalyst automatically blesses a Context object into your application
219 class and makes it available everywhere in your application. Use the
220 Context to directly interact with Catalyst and glue your L</Components>
221 together. For example, if you need to use the Context from within a
222 Template Toolkit template, it's already there:
224 <h1>Welcome to [% c.config.name %]!</h1>
226 As illustrated in our URL-to-Action dispatching example, the Context is
227 always the second method parameter, behind the Component object
228 reference or class name itself. Previously we called it C<$context> for
229 clarity, but most Catalyst developers just call it C<$c>:
232 my ( $self, $c ) = @_;
233 $c->res->body('Hello World!');
236 The Context contains several important objects:
240 =item * L<Catalyst::Request>
245 The request object contains all kinds of request-specific information, like
246 query parameters, cookies, uploads, headers, and more.
248 $c->req->params->{foo};
249 $c->req->cookies->{sessionid};
250 $c->req->headers->content_type;
253 =item * L<Catalyst::Response>
258 The response is like the request, but contains just response-specific
261 $c->res->body('Hello World');
262 $c->res->status(404);
263 $c->res->redirect('http://oook.de');
265 =item * L<Catalyst::Config>
271 =item * L<Catalyst::Log>
274 $c->log->debug('Something happened');
275 $c->log->info('Something you should know');
280 $c->stash->{foo} = 'bar';
284 The last of these, the stash, is a universal hash for sharing data among
285 application components. For an example, we return to our 'hello' action:
288 my ( $self, $c ) = @_;
289 $c->stash->{message} = 'Hello World!';
290 $c->forward('show_message');
293 sub show_message : Private {
294 my ( $self, $c ) = @_;
295 $c->res->body( $c->stash->{message} );
298 Note that the stash should be used only for passing data in an
299 individual request cycle; it gets cleared at a new request. If you need
300 to maintain more persistent data, use a session.
306 A Catalyst controller is defined by its actions. An action is a
307 subroutine with a special attribute. You've already seen some examples
308 of actions in this document. The URL (for example
309 http://localhost.3000/foo/bar) consists of two parts, the base
310 (http://localhost:3000/ in this example) and the path (foo/bar). Please
311 note that the trailing slash after the hostname[:port] always belongs to
312 base and not to the action.
316 =item * B<Application Wide Actions>
318 Actions which are called at the root level of the application
319 (e.g. http:///localhost:3000/ ) go in MyApp::Controller::Root, like
322 package MyApp::Controller::Root;
323 use base 'Catalyst::Controller';
324 # Sets the actions in this controller to be registered with no prefix
325 # so they function identically to actions created in MyApp.pm
326 __PACKAGE__->config->{namespace} = '';
327 sub default : Private {
328 my ( $self, $context ) = @_;
329 $context->response->body('Catalyst rocks!');
336 For most applications, Catalyst requires you to define only one config
341 Catalyst supports several types of actions:
345 =item * B<Literal> (B<Path> actions)
347 package MyApp::Controller::My::Controller;
348 sub bar : Path('foo/bar') { }
350 Literal C<Path> actions will act relative to their current
351 namespace. The above example matches only
352 http://localhost:3000/my/controller/foo/bar. If you start your path with
353 a forward slash, it will match from the root. Example:
355 package MyApp::Controller::My::Controller;
356 sub bar : Path('/foo/bar') { }
358 Matches only http://localhost:3000/foo/bar.
360 package MyApp::Controller::My::Controller;
363 By leaving the C<Path> definition empty, it will match on the namespace
364 root. The above code matches http://localhost:3000/my/controller.
368 sub bar : Regex('^item(\d+)/order(\d+)$') { }
370 Matches any URL that matches the pattern in the action key, e.g.
371 http://localhost:3000/item23/order42. The '' around the regexp is
372 optional, but perltidy likes it. :)
374 Regex matches act globally, i.e. without reference to the namespace from
375 which it is called, so that a C<bar> method in the
376 C<MyApp::Controller::Catalog::Order::Process> namespace won't match any
377 form of C<bar>, C<Catalog>, C<Order>, or C<Process> unless you
378 explicitly put this in the regex. To achieve the above, you should
379 consider using a C<LocalRegex> action.
381 =item * B<LocalRegex>
383 sub bar : LocalRegex('^widget(\d+)$') { }
385 LocalRegex actions act locally. If you were to use C<bar> in
386 C<MyApp::Controller::Catalog>, the above example would match urls like
387 http://localhost:3000/catalog/widget23.
389 If you omit the "C<^>" from your regex, then it will match any depth
390 from the controller and not immediately off of the controller name. The
391 following example differs from the above code in that it will match
392 http://localhost:3000/catalog/foo/widget23 as well.
394 package MyApp::Controller::Catalog;
395 sub bar : LocalRegex('widget(\d+)$') { }
397 For both LocalRegex and Regex actions, if you use capturing parentheses
398 to extract values within the matching URL, those values are available in
399 the C<$c-E<gt>req-E<gt>captures> array. In the above example, "widget23"
400 would capture "23" in the above example, and
401 C<$c-E<gt>req-E<gt>captures-E<gt>[0]> would be "23". If you want to pass
402 arguments at the end of your URL, you must use regex action keys. See
403 L</URL Path Handling> below.
405 =item * B<Top-level> (B<Global>)
407 package MyApp::Controller::Foo;
410 Matches http://localhost:3000/foo. The function name is mapped
411 directly to the application base. You can provide an equivalent
412 function in this case by doing the following:
414 package MyApp::Controller::Root
417 =item * B<Namespace-Prefixed> (B<Local>)
419 package MyApp::Controller::My::Controller;
422 Matches http://localhost:3000/my/controller/foo.
424 This action type indicates that the matching URL must be prefixed with a
425 modified form of the component's class (package) name. This modified
426 class name excludes the parts that have a pre-defined meaning in
427 Catalyst ("MyApp::Controller" in the above example), replaces "::" with
428 "/", and converts the name to lower case. See L</Components> for a full
429 explanation of the pre-defined meaning of Catalyst component class
434 sub foo : Private { }
436 Matches no URL, and cannot be executed by requesting a URL that
437 corresponds to the action key. Private actions can be executed only
438 inside a Catalyst application, by calling the C<forward> method:
442 See L</Flow Control> for a full explanation of C<forward>. Note that, as
443 discussed there, when forwarding from another component, you must use
444 the absolute path to the method, so that a private C<bar> method in your
445 C<MyApp::Controller::Catalog::Order::Process> controller must, if called
446 from elsewhere, be reached with
447 C<$c-E<gt>forward('/catalog/order/process/bar')>.
451 Args is not an action type per se, but an action modifier - it adds a match
452 restriction to any action it's provided to, requiring only as many path parts
453 as are specified for the action to be valid - for example in
454 MyApp::Controller::Foo,
458 would match any URL starting /foo/bar/. To restrict this you can do
460 sub bar :Local :Args(1)
462 to only match /foo/bar/*/
466 B<Note:> After seeing these examples, you probably wonder what the point
467 is of defining names for regex and path actions. Every public action is
468 also a private one, so you have one unified way of addressing components
471 =head4 Built-in Private Actions
473 In response to specific application states, Catalyst will automatically
474 call these built-in private actions in your application class:
478 =item * B<default : Private>
480 Called when no other action matches. Could be used, for example, for
481 displaying a generic frontpage for the main app, or an error page for
482 individual controllers.
484 If C<default> isn't acting how you would expect, look at using a
485 L</Literal> C<Path> action (with an empty path string). The difference is
486 that C<Path> takes arguments relative from the namespace and C<default>
487 I<always> takes arguments relative from the root, regardless of what
490 =item * B<index : Private>
492 C<index> is much like C<default> except that it takes no arguments
493 and it is weighted slightly higher in the matching process. It is
494 useful as a static entry point to a controller, e.g. to have a static
495 welcome page. Note that it's also weighted higher than Path.
497 =item * B<begin : Private>
499 Called at the beginning of a request, before any matching actions are
502 =item * B<end : Private>
504 Called at the end of a request, after all matching actions are called.
508 =head4 Built-in actions in controllers/autochaining
510 Package MyApp::Controller::Foo;
511 sub begin : Private { }
512 sub default : Private { }
513 sub auto : Private { }
515 You can define built-in private actions within your controllers as
516 well. The actions will override the ones in less-specific controllers,
517 or your application class. In other words, for each of the three
518 built-in private actions, only one will be run in any request
519 cycle. Thus, if C<MyApp::Controller::Catalog::begin> exists, it will be
520 run in place of C<MyApp::begin> if you're in the C<catalog> namespace,
521 and C<MyApp::Controller::Catalog::Order::begin> would override this in
524 In addition to the normal built-in actions, you have a special action
525 for making chains, C<auto>. Such C<auto> actions will be run after any
526 C<begin>, but before your action is processed. Unlike the other
527 built-ins, C<auto> actions I<do not> override each other; they will be
528 called in turn, starting with the application class and going through to
529 the I<most> specific class. I<This is the reverse of the order in which
530 the normal built-ins override each other>.
532 Here are some examples of the order in which the various built-ins
537 =item for a request for C</foo/foo>
541 MyApp::Controller::Foo::default # in the absence of MyApp::Controller::Foo::Foo
544 =item for a request for C</foo/bar/foo>
546 MyApp::Controller::Foo::Bar::begin
548 MyApp::Controller::Foo::auto
549 MyApp::Controller::Foo::Bar::auto
550 MyApp::Controller::Foo::Bar::default # for MyApp::Controller::Foo::Bar::foo
551 MyApp::Controller::Foo::Bar::end
555 The C<auto> action is also distinguished by the fact that you can break
556 out of the processing chain by returning 0. If an C<auto> action returns
557 0, any remaining actions will be skipped, except for C<end>. So, for the
558 request above, if the first auto returns false, the chain would look
563 =item for a request for C</foo/bar/foo> where first C<auto> returns
566 MyApp::Controller::Foo::Bar::begin
568 MyApp::Controller::Foo::Bar::end
572 An example of why one might use this is an authentication action: you
573 could set up a C<auto> action to handle authentication in your
574 application class (which will always be called first), and if
575 authentication fails, returning 0 would skip any remaining methods
578 B<Note:> Looking at it another way, C<auto> actions have to return a
579 true value to continue processing! You can also C<die> in the autochain
580 action; in that case, the request will go straight to the finalize
581 stage, without processing further actions.
583 =head4 URL Path Handling
585 You can pass variable arguments as part of the URL path, separated with
586 forward slashes (/). If the action is a Regex or LocalRegex, the '$' anchor
587 must be used. For example, suppose you want to handle C</foo/$bar/$baz>,
588 where C<$bar> and C<$baz> may vary:
590 sub foo : Regex('^foo$') { my ($self, $context, $bar, $baz) = @_; }
592 But what if you also defined actions for C</foo/boo> and C</foo/boo/hoo>?
594 sub boo : Path('foo/boo') { .. }
595 sub hoo : Path('foo/boo/hoo') { .. }
597 Catalyst matches actions in most specific to least specific order:
601 /foo # might be /foo/bar/baz but won't be /foo/boo/hoo
603 So Catalyst would never mistakenly dispatch the first two URLs to the
606 If a Regex or LocalRegex action doesn't use the '$' anchor, the action will
607 still match a URL containing arguments, however the arguments won't be
610 =head4 Parameter Processing
612 Parameters passed in the URL query string are handled with methods in
613 the L<Catalyst::Request> class. The C<param> method is functionally
614 equivalent to the C<param> method of C<CGI.pm> and can be used in
615 modules that require this.
617 # http://localhost:3000/catalog/view/?category=hardware&page=3
618 my $category = $c->req->param('category');
619 my $current_page = $c->req->param('page') || 1;
621 # multiple values for single parameter name
622 my @values = $c->req->param('scrolling_list');
624 # DFV requires a CGI.pm-like input hash
625 my $results = Data::FormValidator->check($c->req->params, \%dfv_profile);
629 You control the application flow with the C<forward> method, which
630 accepts the key of an action to execute. This can be an action in the
631 same or another Catalyst controller, or a Class name, optionally
632 followed by a method name. After a C<forward>, the control flow will
633 return to the method from which the C<forward> was issued.
635 A C<forward> is similar to a method call. The main differences are that
636 it wraps the call in an C<eval> to allow exception handling; it
637 automatically passes along the context object (C<$c> or C<$context>);
638 and it allows profiling of each call (displayed in the log with
642 my ( $self, $c ) = @_;
643 $c->stash->{message} = 'Hello World!';
644 $c->forward('check_message'); # $c is automatically included
647 sub check_message : Private {
648 my ( $self, $c ) = @_;
649 return unless $c->stash->{message};
650 $c->forward('show_message');
653 sub show_message : Private {
654 my ( $self, $c ) = @_;
655 $c->res->body( $c->stash->{message} );
658 A C<forward> does not create a new request, so your request
659 object (C<$c-E<gt>req>) will remain unchanged. This is a
660 key difference between using C<forward> and issuing a
663 You can pass new arguments to a C<forward> by adding them
664 in an anonymous array. In this case C<$c-E<gt>req-E<gt>args>
665 will be changed for the duration of the C<forward> only; upon
666 return, the original value of C<$c-E<gt>req-E<gt>args> will
670 my ( $self, $c ) = @_;
671 $c->stash->{message} = 'Hello World!';
672 $c->forward('check_message',[qw/test1/]);
673 # now $c->req->args is back to what it was before
676 sub check_message : Private {
677 my ( $self, $c ) = @_;
678 my $first_argument = $c->req->args->[0]; # now = 'test1'
682 As you can see from these examples, you can just use the method name as
683 long as you are referring to methods in the same controller. If you want
684 to forward to a method in another controller, or the main application,
685 you will have to refer to the method by absolute path.
687 $c->forward('/my/controller/action');
688 $c->forward('/default'); # calls default in main application
690 Here are some examples of how to forward to classes and methods.
693 my ( $self, $c ) = @_;
694 $c->forward(qw/MyApp::Model::Hello say_hello/);
698 my ( $self, $c ) = @_;
699 $c->forward('MyApp::Model::Hello'); # no method: will try 'process'
702 package MyApp::Model::Hello;
705 my ( $self, $c ) = @_;
706 $c->res->body('Hello World!');
710 my ( $self, $c ) = @_;
711 $c->res->body('Goodbye World!');
714 Note that C<forward> returns to the calling action and continues
715 processing after the action finishes. If you want all further processing
716 in the calling action to stop, use C<detach> instead, which will execute
717 the C<detach>ed action and not return to the calling sub. In both cases,
718 Catalyst will automatically try to call process() if you omit the
723 Catalyst has an uncommonly flexible component system. You can define as
724 many L</Models>, L</Views>, and L</Controllers> as you like.
726 All components must inherit from L<Catalyst::Base>, which provides a
727 simple class structure and some common class methods like C<config> and
728 C<new> (constructor).
730 package MyApp::Controller::Catalog;
733 use base 'Catalyst::Base';
735 __PACKAGE__->config( foo => 'bar' );
739 You don't have to C<use> or otherwise register Models, Views, and
740 Controllers. Catalyst automatically discovers and instantiates them
741 when you call C<setup> in the main application. All you need to do is
742 put them in directories named for each Component type. Notice that you
743 can use some very terse aliases for each one.
747 =item * B<MyApp/Model/>
751 =item * B<MyApp/View/>
755 =item * B<MyApp/Controller/>
763 To show how to define views, we'll use an already-existing base class for the
764 L<Template Toolkit|Template>, L<Catalyst::View::TT>. All we need to do is
765 inherit from this class:
767 package MyApp::View::TT;
770 use base 'Catalyst::View::TT';
774 (You can also generate this automatically by using the helper script:
776 script/myapp_create.pl view TT TT
778 where the first C<TT> tells the script that the name of the view should
779 be C<TT>, and the second that it should be a Template Toolkit view.)
781 This gives us a process() method and we can now just do
782 $c->forward('MyApp::View::TT') to render our templates. The base class
783 makes process() implicit, so we don't have to say
784 C<$c-E<gt>forward(qw/MyApp::View::TT process/)>.
787 my ( $self, $c ) = @_;
788 $c->stash->{template} = 'hello.tt';
792 my ( $self, $c ) = @_;
793 $c->forward('MyApp::View::TT');
796 You normally render templates at the end of a request, so it's a perfect
797 use for the global C<end> action.
799 Also, be sure to put the template under the directory specified in
800 C<$c-E<gt>config-E<gt>{root}>, or you'll be forced to look at our
801 eyecandy debug screen. ;)
805 To show how to define models, again we'll use an already-existing base
806 class, this time for L<DBIx::Class>: L<Catalyst::Model::DBIC::Schema>.
807 We'll also need L<DBIx::Class::Schema::Loader>.
809 But first, we need a database.
813 id INTEGER PRIMARY KEY,
818 id INTEGER PRIMARY KEY,
819 foo INTEGER REFERENCES foo,
823 INSERT INTO foo (data) VALUES ('TEST!');
826 % sqlite /tmp/myapp.db < myapp.sql
828 Now we can create a DBIC::SchemaLoader component for this database.
830 script/myapp_create.pl model DBIC DBIC::SchemaLoader 'dbi:SQLite:/tmp/myapp.db'
832 L<DBIx::Class::Schema::Loader> automatically loads table layouts and
833 relationships. Use the stash to pass data to your templates.
835 We add the following to MyApp/Controller/Root.pm
838 my ( $self, $c, $id ) = @_;
840 $c->stash->{item} = $c->model('DBIC::Foo')->find($id);
846 my ( $self, $c ) = @_;
848 $c->stash->{template} ||= 'index.tt';
849 $c->forward( $c->view('TT') );
852 We then create a new template file "root/index.tt" containing:
854 The Id's data is [% item.data %]
856 Models do not have to be part of your Catalyst application; you
857 can always call an outside module that serves as your Model:
861 my ( $self, $c ) = @_;
863 $c->stash->{template} = 'list.tt';
865 use Some::Outside::DBIC::Module;
866 my @records = Some::Outside::DBIC::Module->search({
870 $c->stash->{records} = \@records;
873 But by using a Model that is part of your Catalyst application, you gain
874 several things: you don't have to C<use> each component, Catalyst will
875 find and load it automatically at compile-time; you can C<forward> to
876 the module, which can only be done to Catalyst components; and only
877 Catalyst components can be fetched with
878 C<$c-E<gt>model('SomeModel')>.
880 Happily, since many people have existing Model classes that they
881 would like to use with Catalyst (or, conversely, they want to
882 write Catalyst models that can be used outside of Catalyst, e.g.
883 in a cron job), it's trivial to write a simple component in
884 Catalyst that slurps in an outside Model:
886 package MyApp::Model::DB;
887 use base qw/Catalyst::Model::DBIC::Schema/;
889 schema_class => 'Some::DBIC::Schema',
890 connect_info => ['dbi:SQLite:foo.db', '', '', {AutoCommit=>1}]
894 and that's it! Now C<Some::DBIC::Schema> is part of your
895 Cat app as C<MyApp::Model::DB>.
899 Multiple controllers are a good way to separate logical domains of your
902 package MyApp::Controller::Login;
904 use base qw/Catalyst::Controller/;
906 sub sign_in : Path("sign-in") { }
907 sub new_password : Path("new-password") { }
908 sub sign_out : Path("sign-out") { }
910 package MyApp::Controller::Catalog;
912 use base qw/Catalyst::Controller/;
917 package MyApp::Controller::Cart;
919 use base qw/Catalyst::Controller/;
922 sub update : Local { }
923 sub order : Local { }
925 Note that you can also supply attributes via the Controller's config so long
926 as you have at least one attribute on a subref to be exported (:Action is
927 commonly used for this) - for example the following is equivalent to the same
930 package MyApp::Controller::Login;
932 use base qw/Catalyst::Controller/;
936 'sign_in' => { Path => 'sign-in' },
937 'new_password' => { Path => 'new-password' },
938 'sign_out' => { Path => 'sign-out' },
942 sub sign_in : Action { }
943 sub new_password : Action { }
944 sub sign_out : Action { }
948 Catalyst has a built-in http server for testing! (Later, you can easily
949 use a more powerful server, e.g. Apache/mod_perl, in a production
952 Start your application on the command line...
954 script/myapp_server.pl
956 ...then visit http://localhost:3000/ in a browser to view the output.
958 You can also do it all from the command line:
960 script/myapp_test.pl http://localhost/
968 Join #catalyst on irc.perl.org.
972 http://lists.rawmode.org/mailman/listinfo/catalyst
973 http://lists.rawmode.org/mailman/listinfo/catalyst-dev
977 Sebastian Riedel, C<sri@oook.de>
978 David Naughton, C<naughton@umn.edu>
979 Marcus Ramberg, C<mramberg@cpan.org>
980 Jesse Sheidlower, C<jester@panix.com>
981 Danijel Milicevic, C<me@danijel.de>
982 Kieren Diment, C<kd@totaldatasolution.com>
986 This program is free software, you can redistribute it and/or modify it
987 under the same terms as Perl itself.