This post is a continuation of another post where I am discussing form handling and validation.

Please see part 2 before you read this post.

Now, and this is where things get interesting, I call the validate() method from the TransferObject "itemBean". What you say? validate() method? There is not validate() method in a TransferObject.

I used a Transfer decorator to add a validate() method to my itemBean. I also added a populate() method. Here, have a look:

[More]

This post is a continuation of another post where I am discussing form handling and validation.

Please see part 1 before you read this post.

So, after my user enters data into the form, they will hit the add/update button and the form will get posted to the next event handler, called items.editPost().

[More]

The last time I blogged about this I got some great feedback, so I have gone back to it again and I am trying something new that combines some of the advice I have received from that post, and some advice from Brian Kotek.

[More]

So I have been working on my first ColdBox application the last couple of week, and one of the things I have been struggling with is Form Handling and Validation. I have not been struggling because these concepts are difficult, but with not knowing how they should be implemented in ColdBox or any other MVC framework.

The heart of my question is, when I want to display a form with values pre-populated (like when a user clicks on an 'edit' button for page in a CMS), do I pass the whole bean to the view for insertion into the input tags using getter and setter methods, or do I use the getter and setter methods in the controller to insert the values into the event/request context object and then using the events getValue and setValue() method in the view?

[More]