The Perl Toolchain Summit needs more sponsors. If your company depends on Perl, please support this very important event.


Catalyst::Manual::Intro - Introduction to Catalyst


This is a brief introduction to Catalyst. It explains the most important features of how Catalyst works and shows how to get a simple application up and running quickly. For an introduction (without code) to Catalyst itself, and why you should be using it, see Catalyst::Manual::About. For a systematic step-by-step introduction to writing an application with Catalyst, see Catalyst::Manual::Tutorial.

What is Catalyst?

Catalyst is an elegant web application framework, extremely flexible yet extremely simple. It's similar to Ruby on Rails, Spring (Java), and Maypole, upon which it was originally based. Its most important design philosphy is to provide easy access to all the tools you need to develop web applications, with few restrictions on how you need to use these tools. However, this does mean that it is always possible to do things in a different way. Other web frameworks are initially simpler to use, but achieve this by locking the programmer into a single set of tools. Catalyst's emphasis on flexibility means that you have to think more to use it. We view this as a feature. For example, this leads to Catalyst being more suited to system integration tasks than other web frameworks.


Catalyst follows the Model-View-Controller (MVC) design pattern, allowing you to easily separate concerns, like content, presentation, and flow control, into separate modules. This separation allows you to modify code that handles one concern without affecting code that handles the others. Catalyst promotes the re-use of existing Perl modules that already handle common web application concerns well.

Here's how the Model, View, and Controller map to those concerns, with examples of well-known Perl modules you may want to use for each.

If you're unfamiliar with MVC and design patterns, you may want to check out the original book on the subject, Design Patterns, by Gamma, Helm, Johnson, and Vlissides, also known as the Gang of Four (GoF). Many, many web application frameworks are based on MVC, which is becoming a popular design paradigm for the world wide web.


Catalyst is much more flexible than many other frameworks. Rest assured you can use your favorite Perl modules with Catalyst.

  • Multiple Models, Views, and Controllers

    To build a Catalyst application, you handle each type of concern inside special modules called "Components". Often this code will be very simple, just calling out to Perl modules like those listed above under "MVC". Catalyst handles these components in a very flexible way. Use as many Models, Views, and Controllers as you like, using as many different Perl modules as you like, all in the same application. Want to manipulate multiple databases, and retrieve some data via LDAP? No problem. Want to present data from the same Model using Template Toolkit and PDF::Template? Easy.

  • Reuseable Components

    Not only does Catalyst promote the re-use of already existing Perl modules, it also allows you to re-use your Catalyst components in multiple Catalyst applications.

  • Unrestrained URL-to-Action Dispatching

    Catalyst allows you to dispatch any URLs to any application "Actions", even through regular expressions! Unlike most other frameworks, it doesn't require mod_rewrite or class and method names in URLs.

    With Catalyst you register your actions and address them directly. For example:

        sub hello : Global {
            my ( $self, $context ) = @_;
            $context->response->body('Hello World!');

    Now http://localhost:3000/hello prints "Hello World!".

  • Support for CGI, mod_perl, Apache::Request, FastCGI

    Use Catalyst::Engine::Apache or Catalyst::Engine::CGI. Other engines are also available.


The best part is that Catalyst implements all this flexibility in a very simple way.

  • Building Block Interface

    Components interoperate very smoothly. For example, Catalyst automatically makes a "Context" object available to every component. Via the context, you can access the request object, share data between components, and control the flow of your application. Building a Catalyst application feels a lot like snapping together toy building blocks, and everything just works.

  • Component Auto-Discovery

    No need to use all of your components. Catalyst automatically finds and loads them.

  • Pre-Built Components for Popular Modules

    See Catalyst::Model::DBIC::Schema for DBIx::Class, or Catalyst::View::TT for Template Toolkit.

  • Built-in Test Framework

    Catalyst comes with a built-in, lightweight http server and test framework, making it easy to test applications from the web browser, and the command line.

  • Helper Scripts

    Catalyst provides helper scripts to quickly generate running starter code for components and unit tests. Install Catalyst::Devel and see Catalyst::Helper.


Here's how to install Catalyst and get a simple application up and running, using the helper scripts described above.


Installation of Catalyst can be a time-consuming and frustrating effort, due to its large number of dependencies. The easiest way to get up and running is to use Matt Trout's cat-install script, from, and then install Catalyst::Devel.

    # perl cat-install
    # perl -MCPAN -e 'install Catalyst::Devel'


    $ MyApp
    # output omitted
    $ cd MyApp
    $ script/ controller Library::Login


    $ script/

Now visit these locations with your favorite browser or user agent to see Catalyst in action:

(NOTE: Although we create a controller here, we don't actually use it. Both of these URLs should take you to the welcome page.)


How It Works

Let's see how Catalyst works, by taking a closer look at the components and other parts of a Catalyst application.


Catalyst has an uncommonly flexible component system. You can define as many "Models", "Views", and "Controllers" as you like. As discussed previously, the general idea is that the View is responsible for the output of data to the user (typically via a web browser, but a View can also generate PDFs or e-mails, for example); the Model is responsible for providing data (typically from a relational database); and the Controller is responsible for interacting with the user and deciding how user input determines what actions the application takes.

In the world of MVC, there are frequent discussions and disagreements about the nature of each element - whether certain types of logic belong in the Model or the Controller, etc. Catalyst's flexibility means that this decision is entirely up to you, the programmer; Catalyst doesn't enforce anything. See Catalyst::Manual::About for a general discussion of these issues.

All components must inherit from Catalyst::Base, which provides a simple class structure and some common class methods like config and new (constructor).

    package MyApp::Controller::Catalog;

    use strict;
    use base 'Catalyst::Base';

    __PACKAGE__->config( foo => 'bar' );


You don't have to use or otherwise register Models, Views, and Controllers. Catalyst automatically discovers and instantiates them when you call setup in the main application. All you need to do is put them in directories named for each Component type. You can use a short alias for each one.

  • MyApp/Model/

  • MyApp/M/

  • MyApp/View/

  • MyApp/V/

  • MyApp/Controller/

  • MyApp/C/

In older versions of Catalyst, the recommended practice (and the one automatically created by helper scripts) was to name the directories M/, V/, and C/. Though these still work, we now recommend the use of the full names.


To show how to define views, we'll use an already-existing base class for the Template Toolkit, Catalyst::View::TT. All we need to do is inherit from this class:

    package MyApp::View::TT;

    use strict;
    use base 'Catalyst::View::TT';


(You can also generate this automatically by using the helper script:

    script/ view TT TT

where the first TT tells the script that the name of the view should be TT, and the second that it should be a Template Toolkit view.)

This gives us a process() method and we can now just do $c->forward('MyApp::View::TT') to render our templates. The base class makes process() implicit, so we don't have to say $c->forward(qw/MyApp::View::TT process/).

    sub hello : Global {
        my ( $self, $c ) = @_;
        $c->stash->{template} = '';

    sub end : Private {
        my ( $self, $c ) = @_;
        $c->forward( $c->view('TT') );

You normally render templates at the end of a request, so it's a perfect use for the global end action.

In practice, however, you would use a default end action as supplied by Catalyst::Action::RenderView.

Also, be sure to put the template under the directory specified in $c->config->{root}, or you'll end up looking at the debug screen.


Models are providers of data. This data could come from anywhere - a search engine index, a spreadsheet, the file system - but typically a Model represents a database table. The data source does not intrinsically have much to do with web applications or Catalyst - it could just as easily be used to write an offline report generator or a command-line tool.

To show how to define models, again we'll use an already-existing base class, this time for DBIx::Class: Catalyst::Model::DBIC::Schema. We'll also need DBIx::Class::Schema::Loader.

But first, we need a database.

    -- myapp.sql
    CREATE TABLE foo (
        data TEXT

    CREATE TABLE bar (
        foo INTEGER REFERENCES foo,
        data TEXT

    INSERT INTO foo (data) VALUES ('TEST!');

    % sqlite3 /tmp/myapp.db < myapp.sql

Now we can create a DBIC::Schema model for this database.

    script/ model MyModel DBIC::Schema MySchema create=static 'dbi:SQLite:/tmp/myapp.db'

DBIx::Class::Schema::Loader automatically loads table layouts and relationships, and converts them into a static schema definition MySchema, which you can edit later.

Use the stash to pass data to your templates.

We add the following to MyApp/Controller/

    sub view : Global {
        my ( $self, $c, $id ) = @_;
        $c->stash->{item} = $c->model('MyModel::Foo')->find($id);

    sub end : Private {
        my ( $self, $c ) = @_;
        $c->stash->{template} ||= '';
        $c->forward( $c->view('TT') );

We then create a new template file "root/" containing:

    The Id's data is [% %]

Models do not have to be part of your Catalyst application; you can always call an outside module that serves as your Model:

    # in a Controller
    sub list : Local {
      my ( $self, $c ) = @_;
      $c->stash->{template} = '';
      use Some::Outside::Database::Module;
      my @records = Some::Outside::Database::Module->search({
        artist => 'Led Zeppelin',
      $c->stash->{records} = \@records;

But by using a Model that is part of your Catalyst application, you gain several things: you don't have to use each component, Catalyst will find and load it automatically at compile-time; you can forward to the module, which can only be done to Catalyst components. Only Catalyst components can be fetched with $c->model('SomeModel').

Happily, since many people have existing Model classes that they would like to use with Catalyst (or, conversely, they want to write Catalyst models that can be used outside of Catalyst, e.g. in a cron job), it's trivial to write a simple component in Catalyst that slurps in an outside Model:

    package MyApp::Model::DB;
    use base qw/Catalyst::Model::DBIC::Schema/;
        schema_class => 'Some::DBIC::Schema',
        connect_info => ['dbi:SQLite:foo.db', '', '', {AutoCommit=>1}]

and that's it! Now Some::DBIC::Schema is part of your Cat app as MyApp::Model::DB.

Within Catalyst, the common approach to writing a model for your application is wrapping a generic model (e.g. DBIx::Class::Schema, a bunch of XMLs, or anything really) with an object that contains configuration data, convenience methods, and so forth. Thus you will in effect have two models - a wrapper model that knows something about Catalyst and your web application, and a generic model that is totally independent of these needs.

Technically, within Catalyst a model is a component - an instance of the model's class belonging to the application. It is important to stress that the lifetime of these objects is per application, not per request.

While the model base class (Catalyst::Model) provides things like config to better integrate the model into the application, sometimes this is not enough, and the model requires access to $c itself.

Situations where this need might arise include:

  • Interacting with another model

  • Using per-request data to control behavior

  • Using plugins from a Model (for example Catalyst::Plugin::Cache).

From a style perspective it's usually considered bad form to make your model "too smart" about things - it should worry about business logic and leave the integration details to the controllers. If, however, you find that it does not make sense at all to use an auxillary controller around the model, and the model's need to access $c cannot be sidestepped, there exists a power tool called "ACCEPT_CONTEXT".


Multiple controllers are a good way to separate logical domains of your application.

    package MyApp::Controller::Login;

    use base qw/Catalyst::Controller/;

    sub login : Path("login") { }
    sub new_password : Path("new-password") { }
    sub logout : Path("logout") { }

    package MyApp::Controller::Catalog;

    use base qw/Catalyst::Controller/;

    sub view : Local { }
    sub list : Local { }

    package MyApp::Controller::Cart;

    use base qw/Catalyst::Controller/;

    sub add : Local { }
    sub update : Local { }
    sub order : Local { }

Note that you can also supply attributes via the Controller's config so long as you have at least one attribute on a subref to be exported (:Action is commonly used for this) - for example the following is equivalent to the same controller above:

    package MyApp::Controller::Login;

    use base qw/Catalyst::Controller/;

      actions => {
        'sign_in' => { Path => 'sign-in' },
        'new_password' => { Path => 'new-password' },
        'sign_out' => { Path => 'sign-out' },

    sub sign_in : Action { }
    sub new_password : Action { }
    sub sign_out : Action { }


Whenever you call $c->component("Foo") you get back an object - the instance of the model. If the component supports the ACCEPT_CONTEXT method instead of returning the model itself, the return value of $model->ACCEPT_CONTEXT( $c ) will be used.

This means that whenever your model/view/controller needs to talk to $c it gets a chance to do this when it's needed.

A typical ACCEPT_CONTEXT method will either clone the model and return one with the context object set, or it will return a thin wrapper that contains $c and delegates to the per-application model object.

A typical ACCEPT_CONTEXT method could look like this:

      my ( $self, $c, @extra_arguments ) = @_;
      bless { %$self, c => $c }, ref($self);

effectively treating $self as a prototype object that gets a new parameter. @extra_arguments comes from any trailing arguments to $c->component( $bah, @extra_arguments ) (or $c->model(...), $c->view(...) etc).

The life time of this value is per usage, and not per request. To make this per request you can use the following technique:

Add a field to $c, like my_model_instance. Then write your ACCEPT_CONTEXT method to look like this:

      my ( $self, $c ) = @_;

      if ( my $per_request = $c->my_model_instance ) {
        return $per_request;
      } else {
        my $new_instance = bless { %$self, c => $c }, ref($self);
        Scalar::Util::weaken($new_instance->{c}); # or we have a circular reference
        $c->my_model_instance( $new_instance );
        return $new_instance;

Application Class

In addition to the Model, View, and Controller components, there's a single class that represents your application itself. This is where you configure your application, load plugins, and extend Catalyst.

    package MyApp;

    use strict;
    use Catalyst qw/-Debug/; # Add other plugins here, e.g.
                             # for session support

        name => 'My Application',

        # You can put anything else you want in here:
        my_configuration_variable => 'something',

In older versions of Catalyst, the application class was where you put global actions. However, as of version 5.66, the recommended practice is to place such actions in a special Root controller (see "Actions", below), to avoid namespace collisions.

  • name

    The name of your application.

Optionally, you can specify a root parameter for templates and static data. If omitted, Catalyst will try to auto-detect the directory's location. You can define as many parameters as you want for plugins or whatever you need. You can access them anywhere in your application via $context->config->{$param_name}.


Catalyst automatically blesses a Context object into your application class and makes it available everywhere in your application. Use the Context to directly interact with Catalyst and glue your "Components" together. For example, if you need to use the Context from within a Template Toolkit template, it's already there:

    <h1>Welcome to [% %]!</h1>

As illustrated in our URL-to-Action dispatching example, the Context is always the second method parameter, behind the Component object reference or class name itself. Previously we called it $context for clarity, but most Catalyst developers just call it $c:

    sub hello : Global {
        my ( $self, $c ) = @_;
        $c->res->body('Hello World!');

The Context contains several important objects:

  • Catalyst::Request

        $c->req # alias

    The request object contains all kinds of request-specific information, like query parameters, cookies, uploads, headers, and more.

        $c->req->uri_with( { page = $pager->next_page } );
  • Catalyst::Response

        $c->res # alias

    The response is like the request, but contains just response-specific information.

        $c->res->body('Hello World');
  • Catalyst::Config

  • Catalyst::Log

        $c->log->debug('Something happened');
        $c->log->info('Something you should know');
  • Stash

        $c->stash->{foo} = 'bar';
        $c->stash->{baz} = {baz => 'qox'};
        $c->stash->{fred} = [qw/wilma pebbles/];

    and so on.

The last of these, the stash, is a universal hash for sharing data among application components. For an example, we return to our 'hello' action:

    sub hello : Global {
        my ( $self, $c ) = @_;
        $c->stash->{message} = 'Hello World!';

    sub show_message : Private {
        my ( $self, $c ) = @_;
        $c->res->body( $c->stash->{message} );

Note that the stash should be used only for passing data in an individual request cycle; it gets cleared at a new request. If you need to maintain persistent data, use a session. See Catalyst::Plugin::Session for a comprehensive set of Catalyst-friendly session-handling tools.


A Catalyst controller is defined by its actions. An action is a subroutine with a special attribute. You've already seen some examples of actions in this document. The URL (for example http://localhost.3000/foo/bar) consists of two parts, the base (http://localhost:3000/ in this example) and the path (foo/bar). Please note that the trailing slash after the hostname[:port] always belongs to base and not to the action.

  • Application Wide Actions

    Actions which are called at the root level of the application (e.g. http://localhost:3000/ ) go in MyApp::Controller::Root, like this:

        package MyApp::Controller::Root;
        use base 'Catalyst::Controller';
        # Sets the actions in this controller to be registered with no prefix
        # so they function identically to actions created in
        __PACKAGE__->config->{namespace} = '';
        sub default : Private {
            my ( $self, $context ) = @_;
            $context->response->body('Catalyst rocks!');

Action types

Catalyst supports several types of actions:

  • Literal (Path actions)

        package MyApp::Controller::My::Controller;
        sub bar : Path('foo/bar') { }

    Literal Path actions will act relative to their current namespace. The above example matches only http://localhost:3000/my/controller/foo/bar. If you start your path with a forward slash, it will match from the root. Example:

        package MyApp::Controller::My::Controller;
        sub bar : Path('/foo/bar') { }

    Matches only http://localhost:3000/foo/bar.

        package MyApp::Controller::My::Controller;
        sub bar : Path { }

    By leaving the Path definition empty, it will match on the namespace root. The above code matches http://localhost:3000/my/controller.

  • Regex

        sub bar : Regex('^item(\d+)/order(\d+)$') { }

    Matches any URL that matches the pattern in the action key, e.g. http://localhost:3000/item23/order42. The '' around the regexp is optional, but perltidy likes it. :)

    Regex matches act globally, i.e. without reference to the namespace from which it is called, so that a bar method in the MyApp::Controller::Catalog::Order::Process namespace won't match any form of bar, Catalog, Order, or Process unless you explicitly put this in the regex. To achieve the above, you should consider using a LocalRegex action.

  • LocalRegex

        sub bar : LocalRegex('^widget(\d+)$') { }

    LocalRegex actions act locally. If you were to use bar in MyApp::Controller::Catalog, the above example would match urls like http://localhost:3000/catalog/widget23.

    If you omit the "^" from your regex, then it will match any depth from the controller and not immediately off of the controller name. The following example differs from the above code in that it will match http://localhost:3000/catalog/foo/widget23 as well.

        package MyApp::Controller::Catalog;
        sub bar : LocalRegex('widget(\d+)$') { }

    For both LocalRegex and Regex actions, if you use capturing parentheses to extract values within the matching URL, those values are available in the $c->req->captures array. In the above example, "widget23" would capture "23" in the above example, and $c->req->captures->[0] would be "23". If you want to pass arguments at the end of your URL, you must use regex action keys. See "URL Path Handling" below.

  • Top-level (Global)

        package MyApp::Controller::Foo;
        sub foo : Global { }

    Matches http://localhost:3000/foo. The function name is mapped directly to the application base. You can provide an equivalent function in this case by doing the following:

        package MyApp::Controller::Root
        sub foo : Local { }
  • Namespace-Prefixed (Local)

        package MyApp::Controller::My::Controller; 
        sub foo : Local { }

    Matches http://localhost:3000/my/controller/foo.

    This action type indicates that the matching URL must be prefixed with a modified form of the component's class (package) name. This modified class name excludes the parts that have a pre-defined meaning in Catalyst ("MyApp::Controller" in the above example), replaces "::" with "/", and converts the name to lower case. See "Components" for a full explanation of the pre-defined meaning of Catalyst component class names.

  • Chained

    Catalyst also provides a method to build and dispatch chains of actions, like

        sub catalog : Chained : CaptureArgs(1) {
            my ( $self, $c, $arg ) = @_;
        sub item : Chained('catalog') : Args(1) {
            my ( $self, $c, $arg ) = @_;

    to handle a /catalog/*/item/* path. For further information about this dispatch type, please see Catalyst::DispatchType::Chained.

  • Private

        sub foo : Private { }

    Matches no URL, and cannot be executed by requesting a URL that corresponds to the action key. Catalyst's :Private attribute is exclusive and doesn't work with other attributes (so will not work combined with Path or Chained attributes). With the exception of the index , auto and default actions, Private actions can only be executed from inside a Catalyst application, by calling the forward or detach methods:

        # or

    See "Flow Control" for a full explanation of forward. Note that, as discussed there, when forwarding from another component, you must use the absolute path to the method, so that a private bar method in your MyApp::Controller::Catalog::Order::Process controller must, if called from elsewhere, be reached with $c->forward('/catalog/order/process/bar').

  • Args

    Args is not an action type per se, but an action modifier - it adds a match restriction to any action it's provided to, requiring only as many path parts as are specified for the action to be valid - for example in MyApp::Controller::Foo,

      sub bar :Local

    would match any URL starting /foo/bar/. To restrict this you can do

      sub bar :Local :Args(1)

    to only match /foo/bar/*/

Note: After seeing these examples, you probably wonder what the point is of defining names for regex and path actions. Every public action is also a private one, so you have one unified way of addressing components in your forwards.

Built-in Private Actions

In response to specific application states, Catalyst will automatically call these built-in private actions in your application class:

  • default : Private

    Called when no other action matches. Could be used, for example, for displaying a generic frontpage for the main app, or an error page for individual controllers.

    If default isn't acting how you would expect, look at using a "Literal" Path action (with an empty path string). The difference is that Path takes arguments relative from the namespace and default always takes arguments relative from the root, regardless of what controller it's in. Indeed, this is now the recommended way of handling default situations; the default private controller should be considered deprecated.

  • index : Private

    index is much like default except that it takes no arguments and it is weighted slightly higher in the matching process. It is useful as a static entry point to a controller, e.g. to have a static welcome page. Note that it's also weighted higher than Path.

  • begin : Private

    Called at the beginning of a request, before any matching actions are called.

  • end : Private

    Called at the end of a request, after all matching actions are called.

Built-in actions in controllers/autochaining

    Package MyApp::Controller::Foo;
    sub begin : Private { }
    sub default : Private { }
    sub auto : Private { }

You can define built-in private actions within your controllers as well. The actions will override the ones in less-specific controllers, or your application class. In other words, for each of the three built-in private actions, only one will be run in any request cycle. Thus, if MyApp::Controller::Catalog::begin exists, it will be run in place of MyApp::begin if you're in the catalog namespace, and MyApp::Controller::Catalog::Order::begin would override this in turn.

  • auto : Private

    In addition to the normal built-in actions, you have a special action for making chains, auto. Such auto actions will be run after any begin, but before your action is processed. Unlike the other built-ins, auto actions do not override each other; they will be called in turn, starting with the application class and going through to the most specific class. This is the reverse of the order in which the normal built-ins override each other.

Here are some examples of the order in which the various built-ins would be called:

for a request for /foo/foo
  MyApp::Controller::Foo::default # in the absence of MyApp::Controller::Foo::Foo
for a request for /foo/bar/foo
  MyApp::Controller::Foo::Bar::default # for MyApp::Controller::Foo::Bar::foo

The auto action is also distinguished by the fact that you can break out of the processing chain by returning 0. If an auto action returns 0, any remaining actions will be skipped, except for end. So, for the request above, if the first auto returns false, the chain would look like this:

for a request for /foo/bar/foo where first auto returns false

An example of why one might use this is an authentication action: you could set up a auto action to handle authentication in your application class (which will always be called first), and if authentication fails, returning 0 would skip any remaining methods for that URL.

Note: Looking at it another way, auto actions have to return a true value to continue processing! You can also die in the auto action; in that case, the request will go straight to the finalize stage, without processing further actions.

URL Path Handling

You can pass variable arguments as part of the URL path, separated with forward slashes (/). If the action is a Regex or LocalRegex, the '$' anchor must be used. For example, suppose you want to handle /foo/$bar/$baz, where $bar and $baz may vary:

    sub foo : Regex('^foo$') { my ($self, $context, $bar, $baz) = @_; }

But what if you also defined actions for /foo/boo and /foo/boo/hoo?

    sub boo : Path('foo/boo') { .. }
    sub hoo : Path('foo/boo/hoo') { .. }

Catalyst matches actions in most specific to least specific order:

    /foo # might be /foo/bar/baz but won't be /foo/boo/hoo

So Catalyst would never mistakenly dispatch the first two URLs to the '^foo$' action.

If a Regex or LocalRegex action doesn't use the '$' anchor, the action will still match a URL containing arguments, however the arguments won't be available via @_.

Parameter Processing

Parameters passed in the URL query string are handled with methods in the Catalyst::Request class. The param method is functionally equivalent to the param method of and can be used in modules that require this.

    # http://localhost:3000/catalog/view/?category=hardware&page=3
    my $category = $c->req->param('category');
    my $current_page = $c->req->param('page') || 1;

    # multiple values for single parameter name
    my @values = $c->req->param('scrolling_list');          

    # DFV requires a input hash
    my $results = Data::FormValidator->check($c->req->params, \%dfv_profile);

Flow Control

You control the application flow with the forward method, which accepts the key of an action to execute. This can be an action in the same or another Catalyst controller, or a Class name, optionally followed by a method name. After a forward, the control flow will return to the method from which the forward was issued.

A forward is similar to a method call. The main differences are that it wraps the call in an eval to allow exception handling; it automatically passes along the context object ($c or $context); and it allows profiling of each call (displayed in the log with debugging enabled).

    sub hello : Global {
        my ( $self, $c ) = @_;
        $c->stash->{message} = 'Hello World!';
        $c->forward('check_message'); # $c is automatically included

    sub check_message : Private {
        my ( $self, $c ) = @_;
        return unless $c->stash->{message};

    sub show_message : Private {
        my ( $self, $c ) = @_;
        $c->res->body( $c->stash->{message} );

A forward does not create a new request, so your request object ($c->req) will remain unchanged. This is a key difference between using forward and issuing a redirect.

You can pass new arguments to a forward by adding them in an anonymous array. In this case $c->req->args will be changed for the duration of the forward only; upon return, the original value of $c->req->args will be reset.

    sub hello : Global {
        my ( $self, $c ) = @_;
        $c->stash->{message} = 'Hello World!';
        # now $c->req->args is back to what it was before

    sub check_message : Private {
        my ( $self, $c ) = @_;
        my $first_argument = $c->req->args->[0]; # now = 'test1'
        # do something...

As you can see from these examples, you can just use the method name as long as you are referring to methods in the same controller. If you want to forward to a method in another controller, or the main application, you will have to refer to the method by absolute path.

  $c->forward('/default'); # calls default in main application

Here are some examples of how to forward to classes and methods.

    sub hello : Global {
        my ( $self, $c ) = @_;
        $c->forward(qw/MyApp::Model::Hello say_hello/);

    sub bye : Global {
        my ( $self, $c ) = @_;
        $c->forward('MyApp::Model::Hello'); # no method: will try 'process'

    package MyApp::Model::Hello;

    sub say_hello {
        my ( $self, $c ) = @_;
        $c->res->body('Hello World!');

    sub process {
        my ( $self, $c ) = @_;
        $c->res->body('Goodbye World!');

Note that forward returns to the calling action and continues processing after the action finishes. If you want all further processing in the calling action to stop, use detach instead, which will execute the detached action and not return to the calling sub. In both cases, Catalyst will automatically try to call process() if you omit the method.


Catalyst has a built-in http server for testing or local deployment. (Later, you can easily use a more powerful server, for example Apache/mod_perl or FastCGI, in a production environment.)

Start your application on the command line...


...then visit http://localhost:3000/ in a browser to view the output.

You can also do it all from the command line:

    script/ http://localhost/

Catalyst has a number of tools for actual regression testing of applications. The helper scripts will automatically generate basic tests that can be extended as you develop your project. To write your own comprehensive test scripts, Test::WWW::Mechanize::Catalyst is an invaluable tool.

For more testing ideas, see Catalyst::Manual::Tutorial::Testing.

Have fun!




    Join #catalyst on
    Join #catalyst-dev on to help with development.

Mailing lists:


Sebastian Riedel, David Naughton, Marcus Ramberg, Jesse Sheidlower, Danijel Milicevic, Kieren Diment, Yuval Kogman,


This program is free software. You can redistribute it and/or modify it under the same terms as Perl itself.