In Chapter 1 I have deliberately not mentioned where the dependency injection container gets built because I knew it'll change. The new hotness is the existence of Bundles. Roughly, what Drupal provides in modules (a package of related code and functionality), is a bundle for Symfony. Bundles expose their contents through the dependency injection container and subscribe to events. All the kernel functionality described in chapter 1 is now added in the CoreBundle class. Modules can have their own bundles, too. So modules will define magic named classes to define their bundles (besides magic named functions for hooks) and have specific methods dictated by the BundleInterface, most bundles will only override build().
Commenting on this Story is closed.
Thanks for outlining the new addition to Drupal 8!
-cpliakas
This is great but introduces a nomenclature conflict between Symfony-style bundles and the traditional Drupal entity bundles... I assume this has been brought up before, any thoughts?
there's an issue for that :)
http://drupal.org/node/1380720
well, not *exactly* that, but related...
Yes and some people have problems with it BUT this Bundle approach makes it possible to use symfony bundles *if* it doesn't depend on symfony components we don't have in core :). That is potentially interesting. (I'm very carefull with my words here)