Make getting to a PSGI app saner
authorFlorian Ragwitz <rafl@debian.org>
Tue, 1 Mar 2011 18:30:31 +0000 (19:30 +0100)
committerFlorian Ragwitz <rafl@debian.org>
Tue, 1 Mar 2011 18:32:59 +0000 (19:32 +0100)
commit8f076801b5c41543fdc20859452ed2cea1e1f82f
treeab5d0dfc41464a22a6059f2404d1da334a888763
parentaceee8b5c5fa1198e7c77652ba58049d4582b8d8
Make getting to a PSGI app saner

All the user should ever need to call is ->psgi_app (previously raw_psgi_app),
to get an unwrapped psgi app as provided by the engine. This is what should be
used when writing .psgi files.

For all other ways of running catalyst apps there's no need to be able to get to
the psgi application that'll actually run, so here we're making everything
that's responsible for reading .psgi files to run them with Catalyst::Script::*
or for wrapping the plain psgi code ref with back-compat middleware private.

Unfortunately this removes some of the docs about the automatic .psgi
loading. These should be added again elsewhere. Also the Upgrading docs need
updating after this.
lib/Catalyst.pm
lib/Catalyst/Test.pm
t/aggregate/psgi_file.t