3 Catalyst::Upgrading - Instructions for upgrading to the latest Catalyst
5 =head1 Upgrading to Catalyst 5.90
7 The major change is that L<Plack> now replaces most of the subclasses of
8 L<Catalyst::Engine>. If you are using one of the standard subclasses of
9 L<Catalyst::Engine> this should be a straightforward upgrade for you. It was
10 a design goal for this release to be as backwardly compatible as possible.
11 However since L<Plack> is different from L<Catalyst::Engine> it would be
12 possible that edge case differences would exist. Therefore we recommend care
13 be taken with this upgrade and that testing should be greater than would be
14 the case with a minor point update.
16 It is highly recommended that you become familar with the L<Plack> ecosystem
17 and documentation. Being able to take advantage of L<Plack> development and
18 middleware is a major bonus to this upgrade. Documentation about how to
19 take advantage of L<Plack::Middleware> by writing your own C<< .psgi >> file
20 is contained in L<Catalyst::PSGI>.
22 If you have created a custom subclass of L<Catalyst:Engine> you will need to
23 convert it to be a subclass of L<Plack::Handler>.
25 If you are using the L<Plack> engine, L<Catalyst::Engine::PSGI>, this new
26 release supercedes that code.
28 If you are using a subclass of L<Catalyst::Engine> that is aimed at nonstandard
29 or internal / testing uses, such as L<Catalyst::Engine::Embeddable> you should
30 still be able to continue using that engine.
32 Advice for specific subclasses of L<Catalyst::Engine> follows:
34 =head2 Upgrading the FastCGI Engine
36 No upgrade needed if your myapp_fastcgi.pl script is already upgraded
37 enough to use L<Catalyst::Script::FastCGI>.
39 =head2 Upgrading the mod_perl / Apache Engines
41 The engines that are build upon the various iterations of mod_perl,
42 L<Catalyst::Engine::Apache::MP13> and
43 L<Catalyst::Engine::Apache2::MP20> should be seemless upgrades and will
44 work using using L<Plack::Handler::Apache1> or L<Plack::Handler::Apache2>
47 L<Catalyst::Engine::Apache2::MP19>, is however no longer supported, as Plack
48 does not support mod_perl version 1.99
50 =head2 Upgrading the HTTP Engine
52 The default development server that comes with the L<Catalyst> distribution
53 should continue to work as expected with no changes as long as your C<myapp_server>
54 script is upgraded to use L<Catalyst::Script::HTTP>.
56 =head2 Upgrading the CGI Engine
58 If you were using L<Catalyst::Engine::CGI> there is no upgrade needed if your
59 myapp_cgi.pl script is already upgraded enough to use L<Catalyst::Script::CGI>.
61 =head2 Upgrading the Preforking Engine
63 If you were using L<Catalyst::Engine::HTTP::Prefork> then L<Starman>
64 is automatically loaded.
66 If you were customising your server script to pass opttions to the prefork engine,
67 then this is no longer supported. The recommended route to implement this functionality
68 is to write a simple .psgi file for your application, then use the L<plackup> untility.
70 =head2 Upgrading the PSGI Engine
72 If you were using L<Catalyst::Engine::PSGI> this new release supercedes this
73 engine in supporting L<Plack>. By default the Engine is now always L<Plack>.
74 As a result, you can stop depending on L<Catalyst::Engine::PSGI> in your
77 Applications that were using L<Catalyst::Engine::PSGI>
78 previously should entirely continue to work in this release with no changes.
80 However, if you have an C<app.psgi> script, then you no longer
81 need to specify the PSGI engine. Instead, the L<Catalyst> application class
82 now has a new method C<psgi_app> which returns a L<PSGI> compatible coderef
83 which you can wrap in middleware of your choice.
85 Catalyst will use the .psgi for your application if it is located in the C<home>
86 directory of the application
88 For example, if you were using L<Catalyst::Engine::PSGI> in the past, you will
89 have written (or generated) a C<script/myapp.psgi> file similar to this one:
94 MyCatalystApp->setup_engine('PSGI');
97 enable ... # enable your desired middleware
98 sub { MyCatalystApp->run(@_) };
101 Instead, you now say:
107 enable ... #enable your desired middleware
108 MyCatalystApp->psgi_app;
111 In the simplest case:
113 MyCatalystApp->setup_engine('PSGI');
114 my $app = sub { MyCatalystApp->run(@_) }
118 MyCatalystApp->setup_engine('PSGI');
119 my $app = MyCatalystApp->psgi_app(@_);
123 my $app = sub { MyCatalystApp->psgi_app(@_) };
124 # If you make ^^ this mistake, your app won't work, and will confuse the hell out of you!
126 You can now rename C<< script/myapp.psgi >> to C<< myapp.psgi >>, and the built-in
127 Catalyst scripts, and your test suite will start using your .psgi file.
129 B<NOTE:> If you rename your .psgi file without these modifications, then any tests run via
130 L<Catalyst::Test> will not be compatible with the new release, and will result in
131 the development server starting, rather than the expected test running.
133 =head2 Engines which are known broken
135 The following engines B<DO NOT> work as of Catalyst version 5.90. The core
136 team is extremely happy to work with the developers and/or users of these
137 engines to help them port to the new Plack/Engine system, however applications
138 which are currently using these engines B<WILL NOT> run without modification
143 =item Catalyst::Engine::Wx
145 =item Catalyst::Engine::Zeus
147 =item Catalyst::Engine::JobQueue::POE
149 =item Catalyst::Engine::XMPP2
151 =item Catalyst::Engine::SCGI
155 =head2 Engines with unknown status
157 The following engines have untested or unknown compatibility. Reports are
162 =item Catalyst::Engine::Mojo
164 =item Catalyst::Engine::Server (Marked as Deprecated)
166 =item Catalyst::Engine::HTTP::POE (Marked as Deprecated)
170 =head2 Using middleware
172 XXX Should this be here or elsewhere?
174 =head2 Making an app.psgi file
176 =head2 Running with plackup?
178 =head1 Upgrading to Catalyst 5.80
180 Most applications and plugins should run unaltered on Catalyst 5.80.
182 However, a lot of refactoring work has taken place, and several changes have
183 been made which could cause incompatibilities. If your application or plugin
184 is using deprecated code, or relying on side effects, then you could have
185 issues upgrading to this release.
187 Most issues found with pre-existing components have been easy to
188 solve. This document provides a complete description of behavior changes
189 which may cause compatibility issues, and of new Catalyst warnings which
192 If you think you have found an upgrade-related issue which is not covered in
193 this document, please email the Catalyst list to discuss the problem.
195 =head1 Moose features
197 =head2 Application class roles
199 You can only apply method modifiers after the application's C<< ->setup >>
200 method has been called. This means that modifiers will not work with methods
201 which run during the call to C<< ->setup >>.
203 See L<Catalyst::Manual::ExtendingCatalyst> for more information about using
204 L<Moose> in your applications.
206 =head2 Controller actions in Moose roles
208 You can use L<MooseX::MethodAttributes::Role> if you want to declare actions
211 =head2 Using Moose in Components
213 The correct way to use Moose in a component in a both forward and backwards
216 package TestApp::Controller::Root;
218 BEGIN { extends 'Catalyst::Component' }; # Or ::Controller, or whatever
220 See L<Components which inherit from Moose::Object before Catalyst::Component>.
222 =head1 Known backwards compatibility breakages
224 =head2 Applications in a single file
226 Applications must be in their own file, and loaded at compile time. This
227 issue generally only affects the tests of CPAN distributions. Your
228 application will fail if you try to define an application inline in a
229 block, and use plugins which supply a C< new > method, then use that
230 application latter in tests within the same file.
232 This is due to the fact that Catalyst is inlining a new method on your
233 application class allowing it to be compatible with Moose. The method
234 used to do this changed in 5.80004 to avoid the possibility of reporting
235 an 'Unknown Error' if your application failed to compile.
237 =head2 Issues with Class::C3
239 Catalyst 5.80 uses the L<Algorithm::C3> method dispatch order. This is
240 built into Perl 5.10, and comes via L<Class::C3> for Perl 5.8. This
241 replaces L<NEXT> with L<Class::C3::Adopt::NEXT>, forcing all components
242 to resolve methods using C3, rather than the unpredictable dispatch
245 This issue is characterised by your application failing to start due to an
246 error message about having a non-linear @ISA.
248 The Catalyst plugin most often causing this is
249 L<Catalyst::Plugin::Session::Store::FastMmap> - if you are using this
250 plugin and see issues, then please upgrade your plugins, as it has been
251 fixed. Note that Makefile.PL in the distribution will warn about known
252 incompatible components.
254 This issue can, however, be found in your own application - the only solution is
255 to go through each base class of the class the error was reported against, until
256 you identify the ones in conflict, and resolve them.
258 To be able to generate a linear @ISA, the list of superclasses for each
259 class must be resolvable using the C3 algorithm. Unfortunately, when
260 superclasses are being used as mixins (to add functionality used in your class),
261 and with multiple inheritence, it is easy to get this wrong.
263 Most common is the case of:
265 package Component1; # Note, this is the common case
266 use base qw/Class::Accessor::Fast Class::Data::Inheritable/;
268 package Component2; # Accidentally saying it this way causes a failure
269 use base qw/Class::Data::Inheritable Class::Accessor::Fast/;
272 use base qw/Component1 Component2/;
274 Any situation like this will cause your application to fail to start.
276 For additional documentation about this issue, and how to resolve it, see
277 L<Class::C3::Adopt::NEXT>.
279 =head2 Components which inherit from Moose::Object before Catalyst::Component
281 Moose components which say:
283 package TestApp::Controller::Example;
285 extends qw/Moose::Object Catalyst::Component/;
287 to use the constructor provided by Moose, while working (if you do some hacks
288 with the C< BUILDARGS > method), will not work with Catalyst 5.80 as
289 C<Catalyst::Component> inherits from C<Moose::Object>, and so C< @ISA > fails
292 The correct way to use Moose in a component in a both forward and backwards
295 package TestApp::Controller::Root;
297 BEGIN { extends 'Catalyst::Component' }; # Or ::Controller, or whatever
299 Note that the C< extends > declaration needs to occur in a begin block for
300 L<attributes> to operate correctly.
302 This way you do not inherit directly from C<Moose::Object>
303 yourself. Having components which do not inherit their constructor from
304 C<Catalyst::Component> is B<unsupported>, and has never been recommended,
305 therefore you're on your own if you're using this technique. You'll need
306 to detect the version of Catalyst your application is running, and deal
307 with it appropriately.
309 You also don't get the L<Moose::Object> constructor, and therefore attribute
310 initialization will not work as normally expected. If you want to use Moose
311 attributes, then they need to be made lazy to correctly initialize.
313 Note that this only applies if your component needs to maintain component
314 backwards compatibility for Catalyst versions before 5.71001 - in 5.71001
315 attributes work as expected, and the BUILD method is called normally
316 (although BUILDARGS is not).
318 If you depend on Catalyst 5.8, then B<all> Moose features work as expected.
320 You will also see this issue if you do the following:
322 package TestApp::Controller::Example;
324 use base 'Catalyst::Controller';
326 as C< use base > appends to @ISA.
328 =head3 use Moose in MyApp
330 Similar to the above, this will also fail:
339 If you need to use Moose in your application class (e.g. for method modifiers
340 etc.) then the correct technique is:
348 __PACKAGE__->config( name => 'MyApp' );
349 __PACKAGE__->setup(qw/
353 =head2 Anonymous closures installed directly into the symbol table
355 If you have any code which installs anonymous subroutine references directly
356 into the symbol table, you may encounter breakages. The simplest solution is
357 to use L<Sub::Name> to name the subroutine. Example:
359 # Original code, likely to break:
360 my $full_method_name = join('::', $package_name, $method_name);
361 *$full_method_name = sub { ... };
364 use Sub::Name 'subname';
365 my $full_method_name = join('::',$package_name, $method_name);
366 *$full_method_name = subname $full_method_name, sub { ... };
368 Additionally, you can take advantage of Catalyst's use of L<Class::MOP> and
369 install the closure using the appropriate metaclass. Example:
372 my $metaclass = Moose::Meta::Class->initialize($package_name);
373 $metaclass->add_method($method_name => sub { ... });
375 =head2 Hooking into application setup
377 To execute code during application start-up, the following snippet in MyApp.pm
381 my ($class, @args) = @_;
382 $class->NEXT::setup(@args);
383 ... # things to do after the actual setup
386 With Catalyst 5.80 this won't work anymore, because Catalyst no longer
387 uses NEXT.pm for method resolution. The functionality was only ever
388 originally operational as L<NEXT> remembers what methods have already
389 been called, and will not call them again.
391 Using this now causes infinite recursion between MyApp::setup and
392 Catalyst::setup, due to other backwards compatibility issues related to how
393 plugin setup works. Moose method modifiers like C<< before|after|around setup
394 => sub { ... }; >> also will not operate correctly on the setup method.
396 The right way to do it is this:
398 after setup_finalize => sub {
399 ... # things to do after the actual setup
402 The setup_finalize hook was introduced as a way to avoid this issue.
404 =head2 Components with a new method which returns false
406 Previously, if you had a component which inherited from Catalyst::COMPONENT,
407 but overrode the new method to return false, then your class's configuration
408 would be blessed into a hash on your behalf, and this would be returned from
409 the COMPONENT method.
411 This behavior makes no sense, and so has been removed. Implementing your own
412 C< new > method in components is B<highly> discouraged. Instead, you should
413 inherit the new method from Catalyst::Component, and use Moose's BUILD
414 functionality and/or Moose attributes to perform any construction work
415 necessary for your class.
417 =head2 __PACKAGE__->mk_accessor('meta');
419 Won't work due to a limitation of L<Moose>. This is currently being fixed
422 =head2 Class::Data::Inheritable side effects
424 Previously, writing to a class data accessor would copy the accessor method
425 down into your package.
427 This behavior has been removed. While the class data is still stored
428 per-class, it is stored on the metaclass of the class defining the accessor.
430 Therefore anything relying on the side effect of the accessor being copied down
433 The following test demonstrates the problem:
437 use base qw/Class::Data::Inheritable/;
438 __PACKAGE__->mk_classdata('foo');
443 use base qw/BaseClass/;
446 BaseClass->foo('base class');
447 Child->foo('sub class');
450 isnt(BaseClass->can('foo'), Child->can('foo'));
452 =head2 Extending Catalyst::Request or other classes in an ad-hoc manner using mk_accessors
454 Previously, it was possible to add additional accessors to Catalyst::Request
455 (or other classes) by calling the mk_accessors class method.
457 This is no longer supported - users should make a subclass of the class whose
458 behavior they would like to change, rather than globally polluting the
461 =head2 Confused multiple inheritance with Catalyst::Component::COMPONENT
463 Previously, Catalyst's COMPONENT method would delegate to the method on
464 the right hand side, which could then delegate back again with
465 NEXT. This is poor practice, and in addition, makes no sense with C3
466 method dispatch order, and is therefore no longer supported.
468 If a COMPONENT method is detected in the inheritance hierarchy to the right
469 hand side of Catalyst::Component::COMPONENT, then the following warning
470 message will be emitted:
472 There is a COMPONENT method resolving after Catalyst::Component
475 The correct fix is to re-arrange your class's inheritance hierarchy so that the
476 COMPONENT method you would like to inherit is the first (left-hand most)
477 COMPONENT method in your @ISA.
481 =head2 Actions in your application class
483 Having actions in your application class will now emit a warning at application
484 startup as this is deprecated. It is highly recommended that these actions are moved
485 into a MyApp::Controller::Root (as demonstrated by the scaffold application
486 generated by catalyst.pl).
488 This warning, also affects tests. You should move actions in your test,
489 creating a myTest::Controller::Root, like the following example:
491 package MyTest::Controller::Root;
496 use parent 'Catalyst::Controller';
498 __PACKAGE__->config(namespace => '');
501 my ( $self, $c ) = @_;
507 =head2 ::[MVC]:: naming scheme
509 Having packages called MyApp::[MVC]::XX is deprecated and can no longer be generated
512 This is still supported, but it is recommended that you rename your application
513 components to Model/View/Controller.
515 A warning will be issued at application startup if the ::[MVC]:: naming scheme is
518 =head2 Catalyst::Base
520 Any code using L<Catalyst::Base> will now emit a warning; this
521 module will be removed in a future release.
523 =head2 Methods in Catalyst::Dispatcher
525 The following methods in Catalyst::Dispatcher are implementation
526 details, which may change in the 5.8X release series, and therefore their use
527 is highly deprecated.
535 =item registered_dispatch_types
537 =item method_action_class
545 The first time one of these methods is called, a warning will be emitted:
547 Class $class is calling the deprecated method Catalyst::Dispatcher::$public_method_name,
548 this will be removed in Catalyst 5.9X
550 You should B<NEVER> be calling any of these methods from application code.
552 Plugin authors and maintainers whose plugins currently call these methods
553 should change to using the public API, or, if you do not feel the public API
554 adequately supports your use case, please email the development list to
555 discuss what API features you need so that you can be appropriately supported.
557 =head2 Class files with names that don't correspond to the packages they define
559 In this version of Catalyst, if a component is loaded from disk, but no
560 symbols are defined in that component's name space after it is loaded, this
561 warning will be issued:
563 require $class was successful but the package is not defined.
565 This is to protect against confusing bugs caused by mistyping package names,
566 and will become a fatal error in a future version.
568 Please note that 'inner packages' (via L<Devel::InnerPackage>) are still fully
569 supported; this warning is only issued when component file naming does not map
570 to B<any> of the packages defined within that component.
572 =head2 $c->plugin method
574 Calling the plugin method is deprecated, and calling it at run time is B<highly
577 Instead you are recommended to use L<Catalyst::Model::Adaptor> or similar to
578 compose the functionality you need outside of the main application name space.
580 Calling the plugin method will not be supported past Catalyst 5.81.