はてなブックマーク

The Symfony Security Component provides a two-layer security system: first it authenticates a user, then is authorizes him for the current request. Authentication means "identify yourself". Authorization means: "let's see if you have the right to be here". The deciding authority in this case will be the AccessDecisionManager. It has a number of voters (which you may create yourself too). Each vote

Symfony2 Config Component: Config Definition and Processing Matthias Noback May 12, 2012 My previous post was about finding and loading configuration files. I now continue my Symfony2 Config Component quest with a post about the way you can “semantically expose your configuration” (using the TreeBuilder). I wrote this piece to later contribute it to the Symfony documentation so feedback is very we

Symfony2 & JMSSerializerBundle: Vendor MIME types and API versioning Matthias Noback April 26, 2012 The JMSSerializerBundle has a VersionExclusionStrategy, which allows you to serialize/deserialize objects for a specific version of your API. You can mark the properties that are available for different versions using the @Since and @Until annotations: use JMS\SerializerBundle\Annotation\Type; use J

Silex: getting your project structure right Matthias Noback January 29, 2012 When I created my first Silex project, I almost felt encouraged to let go of my high standards in programming. So things were starting to look very much like my “legacy” PHP projects, in which everything was put in functions with lengthy parameter lists and those functions were called from within a single index.php file.

Symfony2: Creating a Validator with dependencies? Make it a service! Matthias Noback November 22, 2011 One of the ugly things about Symfony 1 validators was that their dependencies were generally fetched from far away, mainly by calling sfContext::getInstance(). With Symfony2 and it’s service container, this isn’t necessary anymore. Validators can be services. The example below is quite simple, bu

Symfony2 service container: how to make your service use tags Matthias Noback October 12, 2011 First of all: dependency injection is GREAT! Several of Symfony2’s core services depend on tags to recognize which user-defined services should be loaded, notified of events, etc. For example, Twig uses the tag twig.extension to load extra extensions. It would also be great to use tags in case your servi

Symfony2 & Doctrine Common: creating powerful annotations Matthias Noback December 20, 2011 I was looking into the Doctrine Common library; it seems to me that especially the AnnotationReader is quite interesting. Several Symfony2 bundles use annotation for quick configuration. For example adding an @Route annotation to your actions allows you to add them “automatically” to the route collection. T