Comments on: My pet store is better than yours! http://www.brianlegros.com/blog/2007/05/03/my-pet-store-is-better-than-yours/ eat, program, and be merry Fri, 28 Oct 2011 00:48:25 +0000 hourly 1 http://wordpress.org/?v=3.3.1 By: admin http://www.brianlegros.com/blog/2007/05/03/my-pet-store-is-better-than-yours/comment-page-1/#comment-16 admin Tue, 08 May 2007 05:12:40 +0000 http://www.brianlegros.com/blog/2007/05/03/my-pet-store-is-better-than-yours/#comment-16 Adam - After some thinking, I'm probably gonna hold off until CF8 to put together something that is comparable to what they're doing in JEE 5. AJAX data binding and <cffeed> will help out a lot. I think I'll have to rely on good practices for the persistence stuff for sure. Since I want to implement the frameworks as a supplemental task, it'll be easy to show how Transfer/Reactor/etc provide a benefit. Adam – After some thinking, I’m probably gonna hold off until CF8 to put together something that is comparable to what they’re doing in JEE 5. AJAX data binding and <cffeed> will help out a lot. I think I’ll have to rely on good practices for the persistence stuff for sure. Since I want to implement the frameworks as a supplemental task, it’ll be easy to show how Transfer/Reactor/etc provide a benefit.

]]> By: AdamFortuna http://www.brianlegros.com/blog/2007/05/03/my-pet-store-is-better-than-yours/comment-page-1/#comment-12 AdamFortuna Fri, 04 May 2007 09:08:24 +0000 http://www.brianlegros.com/blog/2007/05/03/my-pet-store-is-better-than-yours/#comment-12 Sounds like you'll have to use some JS library for the ajax stuff, unless you plan on waiting until CF8 comes out that is. It could be written into a XML forms xsl technically. Those are what create the alerts used for typical form processing actually, so there are examples of those in the cfide/scripts/ folder. There's a lot of possibilities in there, but hammering out a reusable form component where all cases are covered is pretty tricky. I like the rails way of handling persistence, which can be utilized in reactor or transfer. Basic idea is that form fields have names like "user[username]" and user[first_name]" then when it hits the server you have a "user" struct with keys for username and first_name. This can be passed right into a reactor DAO without a problem, and I think transfer has a setMemento() function that can be used to populate a bean from a structure, which can then be saved. Validation needs to be done before either case though, which is it's own problem. Sounds like you’ll have to use some JS library for the ajax stuff, unless you plan on waiting until CF8 comes out that is. It could be written into a XML forms xsl technically. Those are what create the alerts used for typical form processing actually, so there are examples of those in the cfide/scripts/ folder. There’s a lot of possibilities in there, but hammering out a reusable form component where all cases are covered is pretty tricky.

I like the rails way of handling persistence, which can be utilized in reactor or transfer. Basic idea is that form fields have names like “user[username]” and user[first_name]” then when it hits the server you have a “user” struct with keys for username and first_name. This can be passed right into a reactor DAO without a problem, and I think transfer has a setMemento() function that can be used to populate a bean from a structure, which can then be saved. Validation needs to be done before either case though, which is it’s own problem.

]]>