ADF is highly declarative and you can do a lot with it without writing a single line of code. But sooner or later, the average ADF developer is going to have to write a little Java. There are use cases that simply can’t be met with the declarative components and page definition files alone. For instance, you can add a database Commit to a button declaratively. What if you want to check for commit-time errors, and if there are errors, you want to show them to the user and stay on the same page so the user can correct them, but with no errors you want to navigate to another page and show a “success” message? This will take a little bit of code. In short, you need a managed bean.
In this presentation, I will show some of the most common use cases for a managed bean. I’ll give some cases where a managed bean may or may not be needed and a few “rules of thumb” for when to use one. I’ll show attendees three ways to get a managed bean configured in their applications. I’ll talk about managed bean scopes, when to use which scope, and explain when a managed bean is a “backing bean”. I’ll show the base class that I use with most of my managed beans to cover the ADF methods that I call most frequently. And I’ll give a few dos and don'ts about managed beans.
Managed beans may not grow into a beanstalk, but they will help Jack and Jill ADF Developer fight some of the giant problems in developing an ADF application.
Become a member of ODTUG to gain access to more than 2,500 files in our technical database.
- Not a member? Click through to the topic of interest to browse a list of available presentations.
- Already a member? Log-in here to access the full database
Click here to see the Full Techincal Resource Database