Over the last two weeks, I’ve been talking about model layer code to facilitate integration of database-level validation logic into an ADF application. This week, let’s finish off the project by writing the controller-layer code that will turn these custom exceptions into nice, user-friendly error messages. Continue reading Business Components Without the Business: Part III
Last week, I talked about how to code database error messages, entity object classes, and custom exceptions to facilitate integration of database-level validation logic into an ADF application. And I promised that this week, we’d finish off the project by writing the controller-layer code that will turn these custom exceptions into nice, user-friendly error messages, right? Well, I’m not going to do that, because I actually forgot something at the ADF Business Components (ADF BC) layer. Controller stuff next week. I really promise this time.
Continue reading Business Components Without the Business: Part II
…well, sort of. They don’t have the title correct, and Dr. Paul Dorsey probably won’t be joining us (me, Peter Koletzke, and Duncan Mills) in this project, but you can sign up to be notified about Oracle JDeveloper Fusion Development – A Handbook for 4GL Developers on Amazon now. It’s being written against the upcoming JDeveloper/ADF 11g release.
We now return to our regularly scheduled programming.
I have my own very strong opinion on where to put business logic, but it isn’t any of the above. It’s this: It depends. Continue reading The Business Logic Wars