X-Git-Url: http://git.shadowcat.co.uk/gitweb/gitweb.cgi?a=blobdiff_plain;f=lib%2FCatalyst%2FComponent.pm;h=55f25c0092ec598d69484baabe728a53db37af47;hb=b4ed26ff40a4cad56a4b088ba0cf006bfde8df82;hp=0952b768f7ea1a66e1e796e5561565f8cd161802;hpb=3e5607485bfedb02a06193f653a2f05202db7a4e;p=catagits%2FCatalyst-Runtime.git diff --git a/lib/Catalyst/Component.pm b/lib/Catalyst/Component.pm index 0952b76..55f25c0 100644 --- a/lib/Catalyst/Component.pm +++ b/lib/Catalyst/Component.pm @@ -203,8 +203,8 @@ something like this: } B Generally when L starts, it initializes all the components -and passes the hashref present in any configutation information to the -COMPONET method. For example +and passes the hashref present in any configuration information to the +COMPONENT method. For example MyApp->config( 'Model::Foo' => { @@ -289,6 +289,14 @@ And in a controller: my $type = $c->model('FooFactory', 1,2,3,4): # $type->isa('Type1') +B If you define a ACCEPT_CONTEXT method it MUST check to see if the +second argument is blessed (is a context) or not (is an application class name) and +it MUST return something valid for the case when the scope is application. This is +required because a component maybe be called from the application scope even if it +requires a context and you must prevent errors from being issued if this happens. +Remember not all components that ACCEPT_CONTEXT actually need or use context information +(and there is a school of thought that suggestions doing so is a design error anyway...) + =head1 SEE ALSO L, L, L, L.