Ahh that is clever. Seems counterintuitive but apparently it reverses the
queue. Wish I thought of that.
Thanks Eden once again!
-Eric
On Wed, Nov 26, 2008 at 6:20 PM, Eden Cardim [EMAIL PROTECTED] wrote:
On Wed, Nov 26, 2008 at 6:45 PM, Eric Wright [EMAIL PROTECTED]
wrote:
I wrote a plugin to add some global functionality to our apps which
depends
on Catalyst::Plugin::Authorization::ACL. The problem is trying to
configure
setup for this plugin. When I override setup or setup_actions the
necessary
engine for ACL has not yet been loaded unless I edit the source for ACL
by
moving its dispatch invocation of $app-NEXT::setup_actions(@_) to the
end
of its routine. Is there a better way to ensure that dependencies for
your
plugin are in place during setup?
Load your plugin before Auth::ACL and call $app-NEXT::setup_actions
before everything else
--
Eden Cardim Need help with your Catalyst or DBIx::Class project?
Code Monkeyhttp://www.shadowcat.co.uk/catalyst/
Shadowcat Systems Ltd. Want a managed development or deployment platform?
http://edenc.vox.com/http://www.shadowcat.co.uk/servers/
___
List: Catalyst@lists.scsys.co.uk
Listinfo: http://lists.scsys.co.uk/cgi-bin/mailman/listinfo/catalyst
Searchable archive:
http://www.mail-archive.com/catalyst@lists.scsys.co.uk/
Dev site: http://dev.catalyst.perl.org/
___
List: Catalyst@lists.scsys.co.uk
Listinfo: http://lists.scsys.co.uk/cgi-bin/mailman/listinfo/catalyst
Searchable archive: http://www.mail-archive.com/catalyst@lists.scsys.co.uk/
Dev site: http://dev.catalyst.perl.org/
