Mainly because I keep forgetting how to do this, I decided to create a quick reminder on how to get forms to hydrate into objects when they are successfully validated.
I know lots of people have been waiting a long time for Part 3 of this series, I can only apologies for the delay, and hope that this post somehow makes up for the wait!
In February I gave a talk on behalf of Zend which compiled parts one and two of this series, plus the non-written part
three into a spoken talk that included code examples. The video is included here for all your viewing pleasure:
This is part 2 of my series aimed at giving Zend Framework 1 developers an introduction to Zend Framework 2, if you haven’t read part 1, there’s a link at the top of the page.
I’ve decided to actually make this series 3 parts, in this part I’ll be talking about Routing, the Event Manager, and finally the Service Manager.
Having worked with ZF1 for a lot of years, I’ve been watching the development of ZF2 with interest. I’ve tried nearly every version, from the heady days of the pre-Skeleton App, right through the betas and release candidates.
After speaking to a prospective employer in a job interview, I was interested to try out the ZendMvcControllerRestfulController. With Zend_Json_Server in ZF1 having, shall we say, a less than sterling reputation, it was very interesting for me to see how the strategy has been implemented in ZF2.
Recently I’ve been working a lot on trying to get OAuth2 support into beta 4 of Zend Framework 2, and there were a few challenges. Allowing the client to consume the variety of providers out there proved to be the first. There have been several drafts of the OAuth2 specification, and providers have implemented a variety of the drafts. As each of the drafts have subtle differences, the client needs to be able to have a default configuration that can be over-ridden on a per-provider basis.