JDev11 with ADF backing bean examples?

Question

I have gone through many of the OBEs, How To examples, and a few custom examples in blog posts. Almost all of the examples that use ADF Business Components to model oracle data do not use backing beans, at least not of the ones I have found. If anyone know of links to examples that show JDeveloper using ADF to model Oracle table and using backing beans (Could be calls to the application module, whatever). Could you please post links. The examples from Oracle tend to be declarative with ADF components, and I want to get to the next level of complexity in development that combines custom code with existing declarative code.
It would be great if a few of the OBEs could show a declarative, and also a programmatic way to solve the same problem in a few cases - such as the "Build a Fusion Web Application" in the help. I don't need everything programmatically done, just show where something can be done declarative and how it could also be done programmatically. It would also help to know the limits of declarative programming and where you would need to code a solution.
Thanks, Ken

Answer 1

>
Warning: Long Post. I wanted this to be clear as to what I really need help with.
>
What I am looking for is more clarification on both how to use and when to use backing beans.
Here is an example that I am currently working on using jdev11u2 with ADF BC for the model and JSF.
I have a single page. The goal is to have several filter components, then a run report. Under the run report there are several components based on select statements that use one or more of the filter components. These components are displayed as graphs (because that is what management wants to see.)
Seems easy enough.
I have four graphs that are desired. In my oracle schema, I use sql developer to develop four queries that return the data that I want.
In the model, I create four view objects. Each one has a one or more binds for filters. I don't put in a default value, but make them required. Most of the views have a common bind for techID, which actually points to a different column name in each of the views, but generally has a similar meaning. I didn't create the tables, just have to live with the existing design. Sound familiar? After creating read only views that do not have EOs, I add these to the Application Module. I also create a lookup for techid that queries a table and returns two values, techname and techid. I want this to be used for a combobox to select the user to run the report on.
Three of the queries have a date component. The idea is to have options so that the use can select from three choices, last 30 days, last 60 days, and last 90 days. I modify three of the queries in the VOs, and add a DateFilter bind that is of type Date. This happens to be oracle.jbo.domain.Date
So to get this to work so far, I create a method named updateViews in my Application Module. I create two methods, one that receives String TechID, and another that receives String TechID and java.util.Date date. In the code for the first choice, I simple get the date 30 days ago and use that, then call the second method with both techid and the date. In the second method, I convert java.util.Date to oracle.jbo.domain.Date. I create an instance of each VO, and call a method on each named updateWithParams(String techid, Date date). The Date is automatically defined as the oracle.jbo.domain.Date. In each of my VO's, I create a method in the VOImpl.java for each that is basically the same - accepts the parameters, sets them in the where clause, then calls the execute method.
In the form, I start simple. I drag the ExecuteWithParam method to the form from the updateView that only has the techid field as an ADF Button. I Then drag the techid parameter under this method to the form as a single selection, and set this up so that it uses my lookup for the data, displays the name, and uses the techid as the value.
To test, I drag each of the VOs to the page as simple read only tables, not bothering to change any of the settings. This is just to make sure it is working.
To note, the page uses an actionlistener for the button, so the code on the page for the button is:
<af:commandButton actionListener="#{bindings.updateViews1.execute}"
  text="updateViews1"
  disabled="#{!bindings.updateViews1.enabled}"/>Everything works! Yea!
Now to make this more interesting, I want to add the date filter.
I delete the Command button and the combobox. I now drag the method that has two parameters. Same procedure as before, adding the techid parameter that uses the combobox that uses the lookup vo. Great so far.
Now here is where I run into problems and am trying to understand backing beans as a possible solution.
I need the data selection to be a radio button that has three choices: Last 30, Last 60, and Last 90. Using the drop method of the parameter to the form, it doesn't appear that I have any way to setup initial values correctly. Just to test, I dropped as an input date. In this case I can't set the default date. I get the following component on the page:
          <af:inputDate value="#{bindings.date.inputValue}"
                        required="#{bindings.date.hints.mandatory}"
                        shortDesc="#{bindings.date.hints.tooltip}">
            <f:validator binding="#{bindings.date.validator}"/>
            <af:convertDateTime pattern="#{bindings.date.format}"/>
          </af:inputDate>What I want is to be able to modify the value for #{bindings.date.inputValue}, but I don't understand how backing beans work well enough to implement this. When I try, everything gets messed up. I even tried to use a backing bean for the command button, but then I have an actionlistener, I have to create both the binding and action. I don't know if this is correct, and haven't found documentation that shows what to do.
So this is my dilemma, I think that a backing bean will solve the problem, but need examples that incorporate both standard table bound components to ADF BC model, that I can manipulate. Eventually, I want the date component to point to a radio button. If I drop the component on the form and drop as a select one radio, this is my starting point. Now, how can I setup the values so that the 30, 60, and 90 are really SYSDATE - 30, SYSDATE - 60, and SYSDATE -90 (or java equivalent using Calendar), and still bound to the ADF component so when the command button is pressed, the correct parameters are sent.
What is not clear is whether I need to switch out the execwithparams to backingbean functionality to call the method. Can both co-exist with actionlistener being set, and an action pointing to a backing bean?
This is why I am requesting more examples, so that the mixing of ADF BC model bound to ADF faces components and programming code to get the compoents to work according to a specific user case can be completed.
Thanks, Ken