Oracle ADF - Application development Framework

What is JSF ?
JSF -- Is treated as component, where as JSP is treated as custom tags and java code
Developed through JSR-127
It has always only a post request
Always a page gets submitted to the page itself.

6 phases in JSF life cycle
Restore View --> Apply Request Values --> Process Validation-->
update model-->Invoke applications-->Render response

Backing Bean -- binding, Access to data as well as component
Managed Bean -- value ( Create class file manually), access to only the data and not the component

validation
1. Manual Validation
2. Implict automatic Validation
3. Explicit automatic validation
4. Custom validators

ADF component -- Always client side
JSF Component -- Alwats Server side

Assco -- relationship btw entities
Links -- relationship btw views

First time accessing the jbean jsp file
1. web.xml
Look for Binding filters
2. Binding Context -- object created
CPX
3. Binding container



Localization
All messages in self service would be stored in .properties files as Resource Bundles. On a live environment there would be one property file for each supported locale. All the property files would have the name [_].properties. The baseName is configurable using the configuration parameter "MessageFileBaseName". The properties file for the default locale in the instance would be .properties.
1. Messages without tokens: #{messageBean['']}
2. Messages with one token: "#{adfFacesContext.formatter[messageBean['']][]}"

eg:
FacesContext facesContext = FacesContext.getCurrentInstance();
MessageBean message = ((oracle.apps.tks.base.view.util.MessageBean)
facesContext.getApplication().getVariableResolver().resolveVariable
(facesContext,"messageBean"));
MessageFormat form = new MessageFormat(message.get("MSG_WITH_TWO_PARAMS"));
return form.format(testArgs);