From 0afbfaee75e8480e8e0ed0a3bbd3749a4756f727 Mon Sep 17 00:00:00 2001
From: franck cuny <franck@lumberjaph.net>
Date: Fri, 10 Sep 2010 23:25:10 +0200
Subject: initial import

---
 ...ome-components-to-be-loaded-by-catalyst.textile | 26 ++++++++++++++++++++++
 1 file changed, 26 insertions(+)
 create mode 100644 _posts/2009-06-25-how-to-prevent-some-components-to-be-loaded-by-catalyst.textile

(limited to '_posts/2009-06-25-how-to-prevent-some-components-to-be-loaded-by-catalyst.textile')

diff --git a/_posts/2009-06-25-how-to-prevent-some-components-to-be-loaded-by-catalyst.textile b/_posts/2009-06-25-how-to-prevent-some-components-to-be-loaded-by-catalyst.textile
new file mode 100644
index 0000000..fefbede
--- /dev/null
+++ b/_posts/2009-06-25-how-to-prevent-some-components-to-be-loaded-by-catalyst.textile
@@ -0,0 +1,26 @@
+---
+layout: post
+category: perl
+title: How to prevent some components to be loaded by Catalyst
+---
+
+Let's say you have a "large" [Catalyst](http://search.cpan.org/perldoc?Catalyst) application, with a lot of compoments. When you deploy your application, or when you want to test it while your developping, you may not want to have some of thoses components loaded (you don't have all the dependencies, they are incompatible, etc...). Catalyst use [Module::Pluggable](http://search.cpan.org/perldoc?Module::Pluggable) to load the components, so you can easily configure this. In your application's configuration, add:
+
+{% highlight yaml %}
+setup_components:
+  except:
+    - MyApp::Model::AAAA
+    - MyAPP::Model::BBBB::REST
+    ...
+{% endhighlight %}
+
+Module::Pluggable have some other interesting features. You may have a second Catalyst application, and want to use one or more components from this one. You can easily do this: 
+
+{% highlight yaml %}
+setup_components:
+  search_path:
+    - MyApp
+    - MyOtherApp::Model
+{% endhighlight %}
+
+
-- 
cgit v1.2.3

