You can bind an input field on a page directly to a bean attribute. Use the EL format “<beanname>.<attribute>” to reference it. (Note: “<scope>.<beanname>.<attribute>” may cause an error.)
You can opt to have JDev automatically maintain backing beans so when you add a new attribute to a page the backing bean gets a corresponding attribute added. (You can also double-click on a GUI component and create a bean from there.)
Can change name (id) property of your fields and beans by altering the id in your property sheet. This editing method allows you to have better names for your fields to references in your custom code later.
Initially it was difficult for me to understand what a collection was and what an iterator was.
Model has Application Modules and View Object instances inside of it. ViewController has DataControl with Collections inside of it. I think they are two ways of looking at the nearly the same things respectively.
Iterators are like cursor pointers in pl/sql; they point at a particular row in a returned set of data rows (a collection…which is a rowset inside a view object instance).
On a Form component, if you use bindings EL expression to keep a record counter against an iterator (to create “page 3 of 10” and the like) and the iterator’s RangeStart expression does not seem to be advancing, …
make sure that the page definition file’s setting of RangeSize is set to the number of rows displayed on the screen (i.e., 1 for a Form).
The default for this attribute for iterators is 10.
It should instead match the number of records you are displaying on that page (1 for a form component).
The application module’s constructor does not represent the start of the life of the application module. Instead, override “create” method if you want to do something which coincides with the beginning of the App Module’s life.
Try to create your Framework Extension Layer as soon as you can stomach it
check out chapter 25.1 through 25.3 in Developer’s Guide to do so.