I'm new to Reactor, and am interested in information regarding the Service Layer in a Reactor app. The last project I worked on happened to have used Transfer ORM, but I still think the controller ended up more complicated than it should have, the service layer was a bit thin, and the objects themselves were pretty dumb. I wasn't really satisfied with the outcome, and I'd like to have an enlightened approach for this project.
I know there are a million ways to skin a cat, but I'm looking for code snippets, demo apps, etc., that illustrate approaches to the service layer (especially for Reactor), so anything anybody could provide would be helpful. I think if I see some service layer examples, I could piece some things together. BTW, I'm looking at Qasim Rasheed's CFDefect app (on RIAForge). It seems to use a framework/layer for every possible piece, which is pretty cool, but it also makes for a rather dense application (especially with the dearth of comments/documentation), and it takes a while to read through a single request and its tangents. I'm not faulting Qasim... I'm glad he made the code public (and I'm sending him patches). [Qasim, if you're around these parts, have you gotten my emails?] Anyways, I'd appreciate your feedback. Thanks, Jamie -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- Reactor for ColdFusion Mailing List [EMAIL PROTECTED] Archives at: http://www.mail-archive.com/reactor%40doughughes.net/ -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
