X-Git-Url: http://git.shadowcat.co.uk/gitweb/gitweb.cgi?p=catagits%2FCatalyst-Runtime.git;a=blobdiff_plain;f=lib%2FCatalyst%2FComponent.pm;h=0952b768f7ea1a66e1e796e5561565f8cd161802;hp=13c9323440515f52c485e92a119f84f0402a45ac;hb=3e5607485bfedb02a06193f653a2f05202db7a4e;hpb=cbe627b901f8e459035a76d423229694e1fefbff diff --git a/lib/Catalyst/Component.pm b/lib/Catalyst/Component.pm index 13c9323..0952b76 100644 --- a/lib/Catalyst/Component.pm +++ b/lib/Catalyst/Component.pm @@ -202,6 +202,19 @@ something like this: return $class->new($app, $args); } +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 + + MyApp->config( + 'Model::Foo' => { + bar => 'baz', + }); + +You would expect COMPONENT to be called like this ->COMPONENT( 'MyApp', +{ bar=>'baz'}); + +This would happen ONCE during setup. + =head2 $c->config =head2 $c->config($hashref) @@ -251,6 +264,31 @@ would cause your MyApp::Model::Foo instance's ACCEPT_CONTEXT to be called with ($c, 'bar', 'baz')) and the return value of this method is returned to the calling code in the application rather than the component itself. +B All classes that are Ls will have a COMPONENT +method, but classes that are intended to be factories or generators will +have ACCEPT_CONTEXT. If you have initialization arguments (such as from +configuration) that you wish to expose to the ACCEPT_CONTEXT you should +proxy them in the factory instance. For example: + + MyApp::Model::FooFactory; + + use Moose; + extends 'Catalyst::Model'; + + has type => (is=>'ro', required=>1); + + sub ACCEPT_CONTEXT { + my ($self, $c, @args) = @_; + return bless { args=>\@args }, $self->type; + } + + MyApp::Model::Foo->meta->make_immutable; + MyApp::Model::Foo->config( type => 'Type1' ); + +And in a controller: + + my $type = $c->model('FooFactory', 1,2,3,4): # $type->isa('Type1') + =head1 SEE ALSO L, L, L, L.