[Catalyst-commits] r10177 - Catalyst-Controller-DBIC-API/1.003/trunk/lib/Catalyst/Controller/DBIC

[lukes at dev.catalyst.perl.org]

Author: lukes
Date: 2009-05-16 13:15:08 +0000 (Sat, 16 May 2009)
New Revision: 10177

Modified:
   Catalyst-Controller-DBIC-API/1.003/trunk/lib/Catalyst/Controller/DBIC/API.pm
Log:
altered docs to make action config clearer

Modified: Catalyst-Controller-DBIC-API/1.003/trunk/lib/Catalyst/Controller/DBIC/API.pm
===================================================================
--- Catalyst-Controller-DBIC-API/1.003/trunk/lib/Catalyst/Controller/DBIC/API.pm	2009-05-16 13:05:24 UTC (rev 10176)
+++ Catalyst-Controller-DBIC-API/1.003/trunk/lib/Catalyst/Controller/DBIC/API.pm	2009-05-16 13:15:08 UTC (rev 10177)
@@ -80,6 +80,8 @@
 
 Generally it's better to have one controller for each DBIC source with the config hardcoded, but in some cases this isn't possible.
 
+Note that the Chained, CaptureArgs and PathPart are just standard Catalyst configuration parameters and that then endpoint specified in Chained - in this case '/api/rpc/rpc_base' - must actually exist elsewhere in your application. See L<Catalyst::DispatchType::Chained> for more details.
+
 =head2 class
 
 Whatever you would pass to $c->model to get a resultset for this class. MyAppDB::Track for example.