Commit | Line | Data |
8c57b129 |
1 | =head1 NAME |
2 | |
3 | Catalyst::Upgrading - Instructions for upgrading to the latest Catalyst |
4 | |
dacd8b0e |
5 | =head1 Upgrading to Catalyst 5.9 |
5d5f4a73 |
6 | |
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 |
040835f0 |
9 | L<Catalyst::Engine> this should be a straightforward upgrade for you. It was |
5d5f4a73 |
10 | a design goal for this release to be as backwardly compatible as possible. |
773b3b08 |
11 | However since L<Plack> is different from L<Catalyst::Engine> it is possible |
12 | that edge case differences exist. Therefore we recommend care be taken with |
13 | this upgrade and that testing should be greater than would be the case with a |
14 | minor point update. |
5d5f4a73 |
15 | |
773b3b08 |
16 | It is highly recommended that you become familiar with the L<Plack> ecosystem |
ae908e7e |
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>. |
5d5f4a73 |
21 | |
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>. |
24 | |
25 | If you are using the L<Plack> engine, L<Catalyst::Engine::PSGI>, this new |
773b3b08 |
26 | release supersedes that code. |
5d5f4a73 |
27 | |
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. |
31 | |
32 | Advice for specific subclasses of L<Catalyst::Engine> follows: |
33 | |
93d60cae |
34 | =head2 Upgrading the FastCGI Engine |
5d5f4a73 |
35 | |
040835f0 |
36 | No upgrade needed if your myapp_fastcgi.pl script is already upgraded |
37 | enough to use L<Catalyst::Script::FastCGI>. |
5d5f4a73 |
38 | |
93d60cae |
39 | =head2 Upgrading the mod_perl / Apache Engines |
5d5f4a73 |
40 | |
040835f0 |
41 | The engines that are build upon the various iterations of mod_perl, |
42 | L<Catalyst::Engine::Apache::MP13> and |
773b3b08 |
43 | L<Catalyst::Engine::Apache2::MP20> should be seamless upgrades and will |
5d5f4a73 |
44 | work using using L<Plack::Handler::Apache1> or L<Plack::Handler::Apache2> |
45 | as required. |
46 | |
040835f0 |
47 | L<Catalyst::Engine::Apache2::MP19>, is however no longer supported, as Plack |
24fd6115 |
48 | does not support mod_perl version 1.99 |
5d5f4a73 |
49 | |
93d60cae |
50 | =head2 Upgrading the HTTP Engine |
5d5f4a73 |
51 | |
040835f0 |
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>. |
5d5f4a73 |
55 | |
93d60cae |
56 | =head2 Upgrading the CGI Engine |
5d5f4a73 |
57 | |
697a3e9e |
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>. |
5d5f4a73 |
60 | |
93d60cae |
61 | =head2 Upgrading the Preforking Engine |
5d5f4a73 |
62 | |
040835f0 |
63 | If you were using L<Catalyst::Engine::HTTP::Prefork> then L<Starman> |
da9eab5a |
64 | is automatically loaded. You should (at least) change your C<Makefile.PL> |
65 | to depend on Starman. |
0ea8962d |
66 | |
da9eab5a |
67 | You can regenerate your C<myapp_server.pl> script with C<catalyst.pl> |
68 | and implement a C<MyApp::Script::Server> class that looks like this: |
69 | |
70 | package MyApp::Script::Server; |
71 | use Moose; |
72 | use namespace::autoclean; |
73 | |
74 | extends 'CatalystX::Script::Server::Starman'; |
75 | |
76 | 1; |
77 | |
78 | This takes advantage of the new script system, and adds a number of options to |
79 | the standard server script as extra options are added by Starman. |
80 | |
81 | More information about these options can be seen at |
82 | L<CatalystX::Script::Server::Starman/SYNOPSIS>. |
83 | |
84 | An alternate route to implement this functionality is to write a simple .psgi |
85 | file for your application, then use the L<plackup> utility to start the |
86 | server. |
5d5f4a73 |
87 | |
93d60cae |
88 | =head2 Upgrading the PSGI Engine |
5d5f4a73 |
89 | |
773b3b08 |
90 | If you were using L<Catalyst::Engine::PSGI> this new release supersedes this |
697a3e9e |
91 | engine in supporting L<Plack>. By default the Engine is now always L<Plack>. |
92 | As a result, you can stop depending on L<Catalyst::Engine::PSGI> in your |
8f912f0b |
93 | C<Makefile.PL>. |
94 | |
95 | Applications that were using L<Catalyst::Engine::PSGI> |
96 | previously should entirely continue to work in this release with no changes. |
97 | |
98 | However, if you have an C<app.psgi> script, then you no longer |
697a3e9e |
99 | need to specify the PSGI engine. Instead, the L<Catalyst> application class |
82452b29 |
100 | now has a new method C<psgi_app> which returns a L<PSGI> compatible coderef |
8f912f0b |
101 | which you can wrap in middleware of your choice. |
102 | |
103 | Catalyst will use the .psgi for your application if it is located in the C<home> |
104 | directory of the application |
697a3e9e |
105 | |
93a57b4b |
106 | For example, if you were using L<Catalyst::Engine::PSGI> in the past, you will |
8f912f0b |
107 | have written (or generated) a C<script/myapp.psgi> file similar to this one: |
697a3e9e |
108 | |
109 | use Plack::Builder; |
110 | use MyCatalytApp; |
111 | |
112 | MyCatalystApp->setup_engine('PSGI'); |
113 | |
114 | builder { |
115 | enable ... # enable your desired middleware |
116 | sub { MyCatalystApp->run(@_) }; |
117 | }; |
118 | |
8f912f0b |
119 | Instead, you now say: |
697a3e9e |
120 | |
121 | use Plack::Builder; |
122 | use MyCatalystApp; |
123 | |
124 | builder { |
125 | enable ... #enable your desired middleware |
75d68821 |
126 | MyCatalystApp->psgi_app; |
697a3e9e |
127 | }; |
5d5f4a73 |
128 | |
34effbc7 |
129 | In the simplest case: |
8f912f0b |
130 | |
34effbc7 |
131 | MyCatalystApp->setup_engine('PSGI'); |
132 | my $app = sub { MyCatalystApp->run(@_) } |
133 | |
134 | becomes |
135 | |
136 | MyCatalystApp->setup_engine('PSGI'); |
137 | my $app = MyCatalystApp->psgi_app(@_); |
138 | |
139 | B<NOT>: |
140 | |
141 | my $app = sub { MyCatalystApp->psgi_app(@_) }; |
142 | # If you make ^^ this mistake, your app won't work, and will confuse the hell out of you! |
143 | |
773b3b08 |
144 | You can now move C<< script/myapp.psgi >> to C<< myapp.psgi >> and the built-in |
145 | Catalyst scripts and your test suite will start using your .psgi file. |
ad15c817 |
146 | |
34effbc7 |
147 | B<NOTE:> If you rename your .psgi file without these modifications, then any tests run via |
8f912f0b |
148 | L<Catalyst::Test> will not be compatible with the new release, and will result in |
149 | the development server starting, rather than the expected test running. |
93a57b4b |
150 | |
151 | =head2 Engines which are known broken |
152 | |
dacd8b0e |
153 | The following engines B<DO NOT> work as of Catalyst version 5.9. The core |
93a57b4b |
154 | team is extremely happy to work with the developers and/or users of these |
155 | engines to help them port to the new Plack/Engine system, however applications |
156 | which are currently using these engines B<WILL NOT> run without modification |
157 | to the engine code. |
158 | |
159 | =over |
160 | |
161 | =item Catalyst::Engine::Wx |
162 | |
ad15c817 |
163 | =item Catalyst::Engine::Zeus |
164 | |
165 | =item Catalyst::Engine::JobQueue::POE |
166 | |
167 | =item Catalyst::Engine::XMPP2 |
168 | |
169 | =item Catalyst::Engine::SCGI |
170 | |
93a57b4b |
171 | =back |
172 | |
5d5f4a73 |
173 | =head2 Engines with unknown status |
174 | |
175 | The following engines have untested or unknown compatibility. Reports are |
176 | highly welcomed: |
177 | |
ad15c817 |
178 | =over |
179 | |
180 | =item Catalyst::Engine::Mojo |
181 | |
182 | =item Catalyst::Engine::Server (Marked as Deprecated) |
183 | |
184 | =item Catalyst::Engine::HTTP::POE (Marked as Deprecated) |
185 | |
186 | =back |
5d5f4a73 |
187 | |
0aafa77a |
188 | =head2 Specifying the engine in the call to ->setup |
189 | |
190 | XXX FIXME |
191 | |
3f22de0b |
192 | =head2 Plack functionality |
040835f0 |
193 | |
3f22de0b |
194 | See L<Catalyst::PSGI>. |
0aafa77a |
195 | |
dacd8b0e |
196 | =head2 Tests in 5.9 |
4db14a9a |
197 | |
dacd8b0e |
198 | Tests should generally work the same in Catalyst 5.9, however there are some differences. |
4db14a9a |
199 | |
200 | Previously, if using L<Catalyst::Test> and doing local requests (against a local server), |
201 | if the application threw an exception then this exception propagated into the test. |
202 | |
773b3b08 |
203 | This behavior has been removed, and now a 500 response will be returned to the test. |
204 | This change unifies behavior, to make local test requests behave similarly to remote |
4db14a9a |
205 | requests. |
206 | |
7e2ec16e |
207 | =head1 Upgrading to Catalyst 5.80 |
208 | |
5687c7f9 |
209 | Most applications and plugins should run unaltered on Catalyst 5.80. |
7e2ec16e |
210 | |
8f61d649 |
211 | However, a lot of refactoring work has taken place, and several changes have |
1a98f036 |
212 | been made which could cause incompatibilities. If your application or plugin |
8f61d649 |
213 | is using deprecated code, or relying on side effects, then you could have |
ba03ccca |
214 | issues upgrading to this release. |
5687c7f9 |
215 | |
8f61d649 |
216 | Most issues found with pre-existing components have been easy to |
217 | solve. This document provides a complete description of behavior changes |
218 | which may cause compatibility issues, and of new Catalyst warnings which |
773b3b08 |
219 | might be unclear. |
7e2ec16e |
220 | |
8f61d649 |
221 | If you think you have found an upgrade-related issue which is not covered in |
222 | this document, please email the Catalyst list to discuss the problem. |
7e2ec16e |
223 | |
85f0a66f |
224 | =head1 Moose features |
225 | |
8f61d649 |
226 | =head2 Application class roles |
85f0a66f |
227 | |
8f61d649 |
228 | You can only apply method modifiers after the application's C<< ->setup >> |
85f0a66f |
229 | method has been called. This means that modifiers will not work with methods |
773b3b08 |
230 | run during the call to C<< ->setup >>. |
85f0a66f |
231 | |
a6eb852a |
232 | See L<Catalyst::Manual::ExtendingCatalyst> for more information about using |
233 | L<Moose> in your applications. |
234 | |
85f0a66f |
235 | =head2 Controller actions in Moose roles |
236 | |
d76c88f3 |
237 | You can use L<MooseX::MethodAttributes::Role> if you want to declare actions |
238 | inside Moose roles. |
85f0a66f |
239 | |
d935773d |
240 | =head2 Using Moose in Components |
241 | |
242 | The correct way to use Moose in a component in a both forward and backwards |
243 | compatible way is: |
244 | |
245 | package TestApp::Controller::Root; |
246 | use Moose; |
247 | BEGIN { extends 'Catalyst::Component' }; # Or ::Controller, or whatever |
248 | |
249 | See L<Components which inherit from Moose::Object before Catalyst::Component>. |
250 | |
8f61d649 |
251 | =head1 Known backwards compatibility breakages |
7e2ec16e |
252 | |
8f61d649 |
253 | =head2 Applications in a single file |
85f0a66f |
254 | |
255 | Applications must be in their own file, and loaded at compile time. This |
8f61d649 |
256 | issue generally only affects the tests of CPAN distributions. Your |
257 | application will fail if you try to define an application inline in a |
258 | block, and use plugins which supply a C< new > method, then use that |
259 | application latter in tests within the same file. |
85f0a66f |
260 | |
261 | This is due to the fact that Catalyst is inlining a new method on your |
8f61d649 |
262 | application class allowing it to be compatible with Moose. The method |
263 | used to do this changed in 5.80004 to avoid the possibility of reporting |
264 | an 'Unknown Error' if your application failed to compile. |
85f0a66f |
265 | |
38f90e49 |
266 | =head2 Issues with Class::C3 |
267 | |
8f61d649 |
268 | Catalyst 5.80 uses the L<Algorithm::C3> method dispatch order. This is |
269 | built into Perl 5.10, and comes via L<Class::C3> for Perl 5.8. This |
270 | replaces L<NEXT> with L<Class::C3::Adopt::NEXT>, forcing all components |
271 | to resolve methods using C3, rather than the unpredictable dispatch |
272 | order of L<NEXT>. |
38f90e49 |
273 | |
5d06547d |
274 | This issue is characterised by your application failing to start due to an |
275 | error message about having a non-linear @ISA. |
276 | |
8f61d649 |
277 | The Catalyst plugin most often causing this is |
278 | L<Catalyst::Plugin::Session::Store::FastMmap> - if you are using this |
279 | plugin and see issues, then please upgrade your plugins, as it has been |
280 | fixed. Note that Makefile.PL in the distribution will warn about known |
281 | incompatible components. |
5d06547d |
282 | |
283 | This issue can, however, be found in your own application - the only solution is |
284 | to go through each base class of the class the error was reported against, until |
285 | you identify the ones in conflict, and resolve them. |
286 | |
287 | To be able to generate a linear @ISA, the list of superclasses for each |
288 | class must be resolvable using the C3 algorithm. Unfortunately, when |
289 | superclasses are being used as mixins (to add functionality used in your class), |
ae7da8f5 |
290 | and with multiple inheritance, it is easy to get this wrong. |
38f90e49 |
291 | |
292 | Most common is the case of: |
293 | |
294 | package Component1; # Note, this is the common case |
295 | use base qw/Class::Accessor::Fast Class::Data::Inheritable/; |
296 | |
8f61d649 |
297 | package Component2; # Accidentally saying it this way causes a failure |
38f90e49 |
298 | use base qw/Class::Data::Inheritable Class::Accessor::Fast/; |
299 | |
300 | package GoesBang; |
301 | use base qw/Component1 Component2/; |
302 | |
5d06547d |
303 | Any situation like this will cause your application to fail to start. |
38f90e49 |
304 | |
8f61d649 |
305 | For additional documentation about this issue, and how to resolve it, see |
5d06547d |
306 | L<Class::C3::Adopt::NEXT>. |
38f90e49 |
307 | |
6f04e56a |
308 | =head2 Components which inherit from Moose::Object before Catalyst::Component |
7e2ec16e |
309 | |
6f04e56a |
310 | Moose components which say: |
7e2ec16e |
311 | |
6f04e56a |
312 | package TestApp::Controller::Example; |
313 | use Moose; |
845bfcd2 |
314 | extends qw/Moose::Object Catalyst::Component/; |
7e2ec16e |
315 | |
8f61d649 |
316 | to use the constructor provided by Moose, while working (if you do some hacks |
1a98f036 |
317 | with the C< BUILDARGS > method), will not work with Catalyst 5.80 as |
6f04e56a |
318 | C<Catalyst::Component> inherits from C<Moose::Object>, and so C< @ISA > fails |
25f61108 |
319 | to linearize. |
6f04e56a |
320 | |
6f04e56a |
321 | The correct way to use Moose in a component in a both forward and backwards |
322 | compatible way is: |
323 | |
324 | package TestApp::Controller::Root; |
325 | use Moose; |
326 | BEGIN { extends 'Catalyst::Component' }; # Or ::Controller, or whatever |
327 | |
ba03ccca |
328 | Note that the C< extends > declaration needs to occur in a begin block for |
3df46b1b |
329 | L<attributes> to operate correctly. |
330 | |
d935773d |
331 | This way you do not inherit directly from C<Moose::Object> |
332 | yourself. Having components which do not inherit their constructor from |
333 | C<Catalyst::Component> is B<unsupported>, and has never been recommended, |
334 | therefore you're on your own if you're using this technique. You'll need |
335 | to detect the version of Catalyst your application is running, and deal |
336 | with it appropriately. |
337 | |
eaae9a92 |
338 | You also don't get the L<Moose::Object> constructor, and therefore attribute |
339 | initialization will not work as normally expected. If you want to use Moose |
3df46b1b |
340 | attributes, then they need to be made lazy to correctly initialize. |
341 | |
342 | Note that this only applies if your component needs to maintain component |
343 | backwards compatibility for Catalyst versions before 5.71001 - in 5.71001 |
344 | attributes work as expected, and the BUILD method is called normally |
eaae9a92 |
345 | (although BUILDARGS is not). |
3df46b1b |
346 | |
347 | If you depend on Catalyst 5.8, then B<all> Moose features work as expected. |
8566c0de |
348 | |
d935773d |
349 | You will also see this issue if you do the following: |
350 | |
351 | package TestApp::Controller::Example; |
352 | use Moose; |
353 | use base 'Catalyst::Controller'; |
354 | |
355 | as C< use base > appends to @ISA. |
356 | |
e11cac87 |
357 | =head3 use Moose in MyApp |
358 | |
359 | Similar to the above, this will also fail: |
360 | |
361 | package MyApp; |
362 | use Moose; |
363 | use Catalyst qw/ |
364 | ConfigLoader |
365 | /; |
366 | __PACKAGE__->setup; |
367 | |
368 | If you need to use Moose in your application class (e.g. for method modifiers |
8f61d649 |
369 | etc.) then the correct technique is: |
e11cac87 |
370 | |
371 | package MyApp; |
372 | use Moose; |
5b6f82d2 |
373 | use Catalyst; |
374 | |
e11cac87 |
375 | extends 'Catalyst'; |
5b6f82d2 |
376 | |
377 | __PACKAGE__->config( name => 'MyApp' ); |
e11cac87 |
378 | __PACKAGE__->setup(qw/ |
379 | ConfigLoader |
380 | /); |
381 | |
04a48104 |
382 | =head2 Anonymous closures installed directly into the symbol table |
383 | |
384 | If you have any code which installs anonymous subroutine references directly |
385 | into the symbol table, you may encounter breakages. The simplest solution is |
386 | to use L<Sub::Name> to name the subroutine. Example: |
387 | |
e11cac87 |
388 | # Original code, likely to break: |
1a98f036 |
389 | my $full_method_name = join('::', $package_name, $method_name); |
04a48104 |
390 | *$full_method_name = sub { ... }; |
391 | |
e11cac87 |
392 | # Fixed Code |
04a48104 |
393 | use Sub::Name 'subname'; |
394 | my $full_method_name = join('::',$package_name, $method_name); |
395 | *$full_method_name = subname $full_method_name, sub { ... }; |
396 | |
8f61d649 |
397 | Additionally, you can take advantage of Catalyst's use of L<Class::MOP> and |
398 | install the closure using the appropriate metaclass. Example: |
04a48104 |
399 | |
400 | use Class::MOP; |
401 | my $metaclass = Moose::Meta::Class->initialize($package_name); |
402 | $metaclass->add_method($method_name => sub { ... }); |
403 | |
780654ad |
404 | =head2 Hooking into application setup |
405 | |
8f61d649 |
406 | To execute code during application start-up, the following snippet in MyApp.pm |
780654ad |
407 | used to work: |
408 | |
409 | sub setup { |
410 | my ($class, @args) = @_; |
411 | $class->NEXT::setup(@args); |
412 | ... # things to do after the actual setup |
413 | } |
414 | |
8f61d649 |
415 | With Catalyst 5.80 this won't work anymore, because Catalyst no longer |
416 | uses NEXT.pm for method resolution. The functionality was only ever |
417 | originally operational as L<NEXT> remembers what methods have already |
418 | been called, and will not call them again. |
780654ad |
419 | |
1a98f036 |
420 | Using this now causes infinite recursion between MyApp::setup and |
421 | Catalyst::setup, due to other backwards compatibility issues related to how |
e6c5b548 |
422 | plugin setup works. Moose method modifiers like C<< before|after|around setup |
1a98f036 |
423 | => sub { ... }; >> also will not operate correctly on the setup method. |
780654ad |
424 | |
425 | The right way to do it is this: |
426 | |
427 | after setup_finalize => sub { |
428 | ... # things to do after the actual setup |
429 | }; |
430 | |
ade00972 |
431 | The setup_finalize hook was introduced as a way to avoid this issue. |
1a98f036 |
432 | |
e11cac87 |
433 | =head2 Components with a new method which returns false |
7e2ec16e |
434 | |
8dd2f514 |
435 | Previously, if you had a component which inherited from Catalyst::COMPONENT, |
8f61d649 |
436 | but overrode the new method to return false, then your class's configuration |
8dd2f514 |
437 | would be blessed into a hash on your behalf, and this would be returned from |
a87f5aa5 |
438 | the COMPONENT method. |
7e2ec16e |
439 | |
8f61d649 |
440 | This behavior makes no sense, and so has been removed. Implementing your own |
441 | C< new > method in components is B<highly> discouraged. Instead, you should |
442 | inherit the new method from Catalyst::Component, and use Moose's BUILD |
1a98f036 |
443 | functionality and/or Moose attributes to perform any construction work |
444 | necessary for your class. |
7e2ec16e |
445 | |
446 | =head2 __PACKAGE__->mk_accessor('meta'); |
447 | |
e11cac87 |
448 | Won't work due to a limitation of L<Moose>. This is currently being fixed |
449 | inside Moose. |
7e2ec16e |
450 | |
451 | =head2 Class::Data::Inheritable side effects |
452 | |
8dd2f514 |
453 | Previously, writing to a class data accessor would copy the accessor method |
454 | down into your package. |
455 | |
8f61d649 |
456 | This behavior has been removed. While the class data is still stored |
8dd2f514 |
457 | per-class, it is stored on the metaclass of the class defining the accessor. |
7e2ec16e |
458 | |
8f61d649 |
459 | Therefore anything relying on the side effect of the accessor being copied down |
8dd2f514 |
460 | will be broken. |
7e2ec16e |
461 | |
1a98f036 |
462 | The following test demonstrates the problem: |
8dd2f514 |
463 | |
464 | { |
465 | package BaseClass; |
466 | use base qw/Class::Data::Inheritable/; |
467 | __PACKAGE__->mk_classdata('foo'); |
468 | } |
469 | |
470 | { |
471 | package Child; |
472 | use base qw/BaseClass/; |
473 | } |
474 | |
475 | BaseClass->foo('base class'); |
476 | Child->foo('sub class'); |
eaae9a92 |
477 | |
e11cac87 |
478 | use Test::More; |
8dd2f514 |
479 | isnt(BaseClass->can('foo'), Child->can('foo')); |
7e2ec16e |
480 | |
8f61d649 |
481 | =head2 Extending Catalyst::Request or other classes in an ad-hoc manner using mk_accessors |
7e2ec16e |
482 | |
8dd2f514 |
483 | Previously, it was possible to add additional accessors to Catalyst::Request |
484 | (or other classes) by calling the mk_accessors class method. |
7e2ec16e |
485 | |
8f61d649 |
486 | This is no longer supported - users should make a subclass of the class whose |
487 | behavior they would like to change, rather than globally polluting the |
e11cac87 |
488 | Catalyst objects. |
8be895a7 |
489 | |
10011c19 |
490 | =head2 Confused multiple inheritance with Catalyst::Component::COMPONENT |
8be895a7 |
491 | |
8f61d649 |
492 | Previously, Catalyst's COMPONENT method would delegate to the method on |
493 | the right hand side, which could then delegate back again with |
494 | NEXT. This is poor practice, and in addition, makes no sense with C3 |
495 | method dispatch order, and is therefore no longer supported. |
bcc773b9 |
496 | |
ba03ccca |
497 | If a COMPONENT method is detected in the inheritance hierarchy to the right |
bcc773b9 |
498 | hand side of Catalyst::Component::COMPONENT, then the following warning |
499 | message will be emitted: |
7e2ec16e |
500 | |
8dd2f514 |
501 | There is a COMPONENT method resolving after Catalyst::Component |
5687c7f9 |
502 | in ${next_package}. |
8dd2f514 |
503 | |
8f61d649 |
504 | The correct fix is to re-arrange your class's inheritance hierarchy so that the |
bcc773b9 |
505 | COMPONENT method you would like to inherit is the first (left-hand most) |
506 | COMPONENT method in your @ISA. |
7e2ec16e |
507 | |
c571d2c8 |
508 | =head1 WARNINGS |
509 | |
63b546b1 |
510 | =head2 Actions in your application class |
511 | |
512 | Having actions in your application class will now emit a warning at application |
e256d0e1 |
513 | startup as this is deprecated. It is highly recommended that these actions are moved |
63b546b1 |
514 | into a MyApp::Controller::Root (as demonstrated by the scaffold application |
55dd186c |
515 | generated by catalyst.pl). |
da73c6af |
516 | |
e256d0e1 |
517 | This warning, also affects tests. You should move actions in your test, |
518 | creating a myTest::Controller::Root, like the following example: |
da73c6af |
519 | |
520 | package MyTest::Controller::Root; |
95a52a01 |
521 | |
da73c6af |
522 | use strict; |
523 | use warnings; |
95a52a01 |
524 | |
da73c6af |
525 | use parent 'Catalyst::Controller'; |
95a52a01 |
526 | |
da73c6af |
527 | __PACKAGE__->config(namespace => ''); |
95a52a01 |
528 | |
da73c6af |
529 | sub action : Local { |
530 | my ( $self, $c ) = @_; |
531 | $c->do_something; |
532 | } |
95a52a01 |
533 | |
da73c6af |
534 | 1; |
63b546b1 |
535 | |
ac9279b0 |
536 | =head2 ::[MVC]:: naming scheme |
537 | |
538 | Having packages called MyApp::[MVC]::XX is deprecated and can no longer be generated |
539 | by catalyst.pl |
540 | |
541 | This is still supported, but it is recommended that you rename your application |
542 | components to Model/View/Controller. |
543 | |
544 | A warning will be issued at application startup if the ::[MVC]:: naming scheme is |
545 | in use. |
546 | |
ade00972 |
547 | =head2 Catalyst::Base |
548 | |
8f61d649 |
549 | Any code using L<Catalyst::Base> will now emit a warning; this |
550 | module will be removed in a future release. |
ade00972 |
551 | |
c571d2c8 |
552 | =head2 Methods in Catalyst::Dispatcher |
553 | |
8f61d649 |
554 | The following methods in Catalyst::Dispatcher are implementation |
555 | details, which may change in the 5.8X release series, and therefore their use |
bcc773b9 |
556 | is highly deprecated. |
c571d2c8 |
557 | |
558 | =over |
559 | |
8dd2f514 |
560 | =item tree |
c571d2c8 |
561 | |
8dd2f514 |
562 | =item dispatch_types |
c571d2c8 |
563 | |
8dd2f514 |
564 | =item registered_dispatch_types |
c571d2c8 |
565 | |
8dd2f514 |
566 | =item method_action_class |
c571d2c8 |
567 | |
8dd2f514 |
568 | =item action_hash |
c571d2c8 |
569 | |
570 | =item container_hash |
571 | |
572 | =back |
573 | |
574 | The first time one of these methods is called, a warning will be emitted: |
7e2ec16e |
575 | |
bcc773b9 |
576 | Class $class is calling the deprecated method Catalyst::Dispatcher::$public_method_name, |
dacd8b0e |
577 | this will be removed in Catalyst 5.9 |
7e2ec16e |
578 | |
c571d2c8 |
579 | You should B<NEVER> be calling any of these methods from application code. |
580 | |
8f61d649 |
581 | Plugin authors and maintainers whose plugins currently call these methods |
8f5a2bd9 |
582 | should change to using the public API, or, if you do not feel the public API |
8f61d649 |
583 | adequately supports your use case, please email the development list to |
8f5a2bd9 |
584 | discuss what API features you need so that you can be appropriately supported. |
7e2ec16e |
585 | |
95b20422 |
586 | =head2 Class files with names that don't correspond to the packages they define |
7e2ec16e |
587 | |
e11cac87 |
588 | In this version of Catalyst, if a component is loaded from disk, but no |
ba03ccca |
589 | symbols are defined in that component's name space after it is loaded, this |
bcc773b9 |
590 | warning will be issued: |
7e2ec16e |
591 | |
bcc773b9 |
592 | require $class was successful but the package is not defined. |
7e2ec16e |
593 | |
8f61d649 |
594 | This is to protect against confusing bugs caused by mistyping package names, |
bcc773b9 |
595 | and will become a fatal error in a future version. |
596 | |
597 | Please note that 'inner packages' (via L<Devel::InnerPackage>) are still fully |
8f61d649 |
598 | supported; this warning is only issued when component file naming does not map |
bcc773b9 |
599 | to B<any> of the packages defined within that component. |
7e2ec16e |
600 | |
5687c7f9 |
601 | =head2 $c->plugin method |
602 | |
25f61108 |
603 | Calling the plugin method is deprecated, and calling it at run time is B<highly |
8dd2f514 |
604 | deprecated>. |
7e2ec16e |
605 | |
95a52a01 |
606 | Instead you are recommended to use L<Catalyst::Model::Adaptor> or similar to |
ba03ccca |
607 | compose the functionality you need outside of the main application name space. |
7e2ec16e |
608 | |
4e68badc |
609 | Calling the plugin method will not be supported past Catalyst 5.81. |
bcc773b9 |
610 | |
7e2ec16e |
611 | =cut |
4e68badc |
612 | |