CakePHP’s security component is awesome. I use it all the time for its CSRF protection (Which will be the subject of a future post).
But sometimes, it does not work as expected. Frustration ensues.
“Setter not found for property class” is one of the most frustrating errors you can get in a Seam / facelets project.
It usually appears late, and you spend a long time trying to solve it. The solution is so simple you have to bang your hand when you finally find it.
I write this in the hope that it shows first in Google searches for this error…
CakePHP is in many ways an awesome framework. It does lots of things for you automagically, and makes development quite pleasant on most days. However, there are a few places where the framework displays irritating glitches.
One of those unlucky places is when you want to use an image as the submit button for your forms.
I am working on three projects at the same time. One of them is my paying job – a large bespoke development using JEE, Seam framework, Hibernate and a structured waterfall process that has gone all over the place as we’re nearing delivery to a fixed schedule (that, truth be told, was postponed for a few weeks…) The team is not huge – there are six developers and two testers, together with a DBA, an architect, a web designer, a BA and two project managers. Yes. Two.