[Catalyst] "Catalyst::Plugin::Authentication uses NEXT, which is deprecated."

Tomas Doran bobtfish at bobtfish.net
Mon May 31 14:34:13 GMT 2010

On 31 May 2010, at 05:16, will at serensoft.com wrote:

> Okay, we should uninstall the deprecated modules just to be sure our  
> dependencies are all clean, and we should use  
> Catalyst::Authentication instead of  
> Catalyst::Plugin::Authentication...

Erm, no. You still use Catalyst::Plugin::Authentication

> So I've got two questions:
> A) How do you uninstall these deprecated Catalyst modules?

You don't. Why do you think you need to? Just don't use them in your  
app and they won't be loaded.

> B) How do we make sure we're using the recommended Store/Credential  
> modules? This isn't something we specify via "use Catalyst qw/blah/"  
> I take it.

Correct, you specify it by the authentication config (as documented in  
the Authentication plugin)

> And is this also true for Session modules? E.g. is  
> C::P::Session::Store::DBIC deprecated in favor of something like  
> C::Session::Store::DBIx::Class, etc?



More information about the Catalyst mailing list