Working With Managed Beans and Javaserver Faces

Working with Managed Beans and
JavaServer Faces
Copyright © 2008, Oracle. All rights reserved.

Objectives
After completing this lesson, you should be able to do the

following:
• Define key JavaServer Faces (JSF) terms
• Describe the JSF architecture with Application
Development Framework (ADF)
• Differentiate between managed and backing beans
• Create and reference managed beans
• Set and use managed properties
• Use context objects to access the application
7-2 Copyright © 2008, Oracle. All rights reserved.

Agenda
• Key Terms and Concepts

• Expression Language (EL)
• Managed Beans and Properties

JSF Review
JSF simplifies Web development because it:

• Is component-based, not markup-based
• Offers automatic event and state handling
• Can be used for a diverse client base, and not just
HTML
• Is designed with tooling in mind
• Is applicable to a wide spectrum of programmer types

Key Terms
• UI component: JSF is component based.

• Managed bean: It includes objects maintained by the JSF
inversion of control mechanism.
• Expression Language: It holds the key to bind the data.
• Life cycle: It involves the process of how JSF works.

JSF Architecture
Device renderer
Markup
JSF Page
<f:view> UI component
…
<h:inputText Expr. language
required="true"
value="#{emp.name}" Managed bean
/>
…
</f:view> J2EE persistence layer/JDBC
RDBMS

Standard Component Model
for Web Development
• JSF provides the UI component.
• JSF components:
– Have properties and can raise events
– Can be nested
– Offer predictable rendering
and follow the event-handling life cycle
• Basic library of UI components
• Core and HTML
• Third-party component libraries

JSF Expression Language
EL connects UI components:
• To model properties for data:
<h:inputText id="lastName“
required="true"
value="#{customer.lastName}"/>
• To create Web-tier application object methods for handling

events:
<h:commandButton id="save“
value="Save Changes"
action="#{customerHandler.saveAll}"/>

Summary of Key Elements
Renderer generates Event

displays consumes
translates value UI Component Contained in View
contains
verifies Event listener
Converter value manipulates
executes
generates updates selects
Validator Model objects
generates specialized
Backing bean
Message Action method Navigation
generates outcome

JSF Suggestions
• Use only JSF:

– Use components, not HTML, for creating the layout.
– Exploit the rendered property for conditional display.
• Manage all (non-model) states through JSF managed
beans; try not to access the session or request directly.
FacesContext fctx = FacesContext.getCurrentInstance();

Application application = fctx.getApplication();
ELContext elctx = fctx.getELContext();

ExpressionFactory exprfactory = application.getExpressionFactory();
ValueExpression valueExpression =
exprfactory.createValueExpression(elctx,"#{mybean}",Object.class);
MyBean myBean = (MyBean) valueExpression.getValue(elctx);
7 - 10 Copyright © 2008, Oracle. All rights reserved.

Agenda


EL Used in Managed Beans
<managed-bean>
<managed-bean-name>userbean</managed-bean-name>
<managed-bean-class>com.oracle.sample.User</managed-bean-class>
<managed-bean-scope>request</managed-bean-scope>
<managed-property>
<property-name>userType</property-name>
<value>#{reference['USER_TYPES'].['EMPLOYEE']}</value>
</managed-property>
</managed-bean>
Managed properties Java code


exprfactory.createValueExpression(elctx,"#{userbean}",Object.class);
User user = (User) valueExpression.getValue(elctx);

Expression Language: Examples
• #{somevar}: Value of the variable named somevar

– Checks at different scopes until it finds a match
– If no match is found, tries the managed bean named
somevar
• #{param.somevar}: Value of the request parameter
named somevar
• #{requestScope.somevar}: Value of the request
attribute named somevar
• #{sessionScope.somevar}: Value of the session
attribute named somevar
• #{cookie.somevar}: Value of the cookie named
somevar

More Expression Language
• #{user.name} and #{user["name"]}: Check at

different scopes until a match is found
– The name property of the scoped variable user
• #{resources.rowLockedError}: The entry with the
rowLockedError key in the Map named resources
• #{user[name]}: The user bean property whose name
is given by the value of the name property
• #{user.addresses[0]}: The first element in the
addresses collection property of user
• #{bindings}: A scoped variable named bindings
• #{bindings.empTable.labels}: The labels
property of the entry with the empTable key in the Map
named bindings

Immediate EL Syntax: ${}
• It is evaluated immediately.
• It can only be used within template text or as the value of a
JSP tag attribute.
<fmt:formatNumber value="${sessionScope.cart.total}"/>
• Code example: JSP value attribute references EL that gets

the total price from the session-scoped bean named cart.
The JSP engine evaluates the expression, converts it, and
passes the returned value to the tag handler.
• Immediate evaluation expressions are always read-only
value expressions. The example can only get the total
price from the cart bean; it cannot set the total price.

Deferred EL Syntax: #{}
• It is evaluated at other phases of a page life cycle as

defined by the technology that uses the expression (JSF).
<h:inputText id="name" value="#{customer.name}" />
• Code example: JSF value attribute references EL that

points to the name property of the customer bean.
– First request: #{customer.name} evaluated during the
Render Response phase of the life cycle. EL gets the value
of name from the customer bean, as is done in the
immediate evaluation.
– Postback: JSF evaluates the expression at different phases
of the life cycle, during which the value is retrieved from the
request, validated, and propagated to the customer bean.
• Deferred EL can be value expressions that can be used to
read and write data.

Agenda


Managed Beans
• Managed beans are optional and can be used to:

– Hold presentation and navigation logic
– Store state (for example, information about the authenticated
user)
– Execute a Java routine (for example, by clicking a button)
– Define a handler for event listeners
• Managed beans are not the same as backing beans.
Backing beans are a specialized type of managed bean
that:
– Contain getter and setter methods for UI components
– Have a one-to-one relationship with a page

Defining Managed Beans
• Can be any Java object, such as maps and lists, as long

as it has an empty constructor
• Are defined in faces-config.xml for JSF and in adfc-
config.xml or other task flow metadata files for ADF
• Are defined with various scopes:
– Application
– Session
– Request
– None
• Have a lazy initialization by JSF, as needed

Using Managed Beans
• Definition:
<managed-bean>
<managed-bean-name>userbean</managed-bean-name>
<managed-bean-class>com.oracle.sample.User</managed-bean-class>
</managed-bean>
• Usage on a page:
<h:inputText value="#{userbean.name}"/>
• Usage in Java code:


exprfactory.createValueExpression(elctx,"#{userbean}",Object.class);
User user = (User) valueExpression.getValue(elctx);

Accessing One Managed Bean from
Another Managed Bean
There are three major ways:
• Using value binding
• Using variable resolver
• Having the reference property
<managed-bean>
<managed-bean-name>person</managed-bean-name>
<managed-bean-class>demo.PersonBean</managed-bean-class>
<managed-bean-scope>session</managed-bean-scope>
<managed-bean>
<managed-bean>
<managed-bean-name>bank</managed-bean-name>
<managed-bean-class>demo.BankBean</managed-bean-class>
<managed-bean>

Hard-Coded Access
Both value binding and variable resolvers hard code values.


exprfactory.createValueExpression(elctx,"#{bank}",Object.class);
BankBean bank = (BankBean) valueExpression.getValue(elctx);
ELResolver elResolver = fctx.getApplication().getELResolver();

BankBean b = (BankBean) elResolver.getValue(elctx,null,“bank");

Using Properties to Access Values
Add a property to one managed bean that references the

second managed bean.
<managed-bean>
<managed-bean-name>Person</managed-bean-name>
<managed-bean-class>demo.PersonBean</managed-bean-class>
<managed-property>
<property-name>bank</property-name>
<property-class>demo.BankBean</property-class>
<value>#{bank}</value>
</managed-property>
<managed-bean>
<managed-bean>
<managed-bean-name>bank</managed-bean-name>
<managed-bean-class>demo.BankBean</managed-bean-class>
<managed-bean>

Managed Properties
Managed properties:
• Are managed bean variables that are exposed through
getter and setter methods
• Are configured in faces-config.xml
• Can take the following possible values:
– Null
– Literal string
– Lists and maps
– Value-binding Expression Language (EL)

Managed Properties: Examples
• Literal string:
<managed-bean>
…
<managed-property>
<property-name>label</property-name>
<value>Hello World</value>
</managed-property>
…
• EL accessing managed bean:

<managed-bean>
…
<managed-property>
<property-name>label</property-name>
<value>#{Userbean['firstname']}</value>
</managed-property>
…

JSF Value Binding
JSF pages can create value bindings to the ADF binding

container using EL accessing the “bindings” object.
#{bindings.firstName.inputValue}
• The “bindings” object is created by the ADF servlet filter

that is defined in the web.xml file.
• The ADF servlet filter is mapped to *.jsp and *.jspx file
types.
• The “bindings” object needs to be configured as a
managed property before it can be used in managed
beans.

Writing Code That Interacts with Bindings
Getting access to the binding in the code (best practice):

• Inject the #{bindings} object into the managed bean.
<managed-bean>
<managed-bean-name>EditPageBean</managed-bean-name>
<managed-bean-class>view.backing.EditPageBean</managed-bean-class>
<managed-property>
<property-name>bindings</property-name>
<value>#{bindings}</value>
</managed-property>
</managed-bean>
• Add getters and setters for

oracle.binding.BindingContainer.
JDeveloper will do this automatically if you let it maintain
backing beans for you.

Accessing the Bindings
• Include process logic or write conditional logic to return

one of the multiple outcomes depending on certain criteria.
• For example, return null if there is an error in the
processing, or another outcome value if the processing
was successful.


ValueExpression valueExpression = exprfactory.createValueExpression

(elctx,"#{bindingsSomeAttrBind.inputvalue}"}",Object.class);
Object myValue = valueExpression.getValue(elctx);

Writing Code That Interacts with Bindings
Using the bindings object:
AttributeBinding deptBinding =
(AttributeBinding)getBindings().getControlBinding("DepartmentName");
String departmentName = (String)deptBinding.getInputValue();
BindingContainer bindings = getBindings();

OperationBinding operationBinding =
bindings.getOperationBinding("First");
Object result = operationBinding.execute();
OperationBinding operationBinding =
getBindings().getOperationBinding("findDepartmentManagerId");
Map params = operationBinding.getParamsMap();
params.put("searchTerm","Sales");
Number deptManager = operationBinding.execute();

Configuring ADF Binding Access for
Managed Beans
• Create a managed property
and set the value to
#{bindings}.
• In managed beans, create an
instance variable with the same
name as the managed property.
• Make sure that the variable type
is
oracle.binding.BindingCo
ntainer.
• Create setter and getter
methods for the instance
variable.
Binding is automatically configured
on the basis of declarative method
binding.

Getting and Setting Bound Data
Access the value of a CoreSelectOne ADF Faces list based on the

returned selected index, which is accessed from
ValueChangeListener.
01. CoreSelectOneChoice singleSelectItem = (CoreSelectOneChoice)

valueChangeEvent.getSource();
02. int SelectedIndx = ((Integer)

singleSelectItem.getValue()).intValue();
03. DCIteratorBinding iter = ((DCBindingContainer)bindings).

findIteratorBinding(“SupplierView11");
04. Row rw = iter.getRowAtRangeIndex(SelectedIndx);

05. valueToPrint = "The selected value is
"+rw.getAttribute(“AddressId");
…

Executing Methods in ADF
• Methods are defined in the pageDef

file as operation bindings.
• The operation can be accessed and
executed from ADF Faces.
• ADF Business Components uses
methods on the ADF binding for
Create, Read, Update, Delete (CRUD).
…
01. OperationBinding operationBinding =
(OperationBinding)bindings.getOperationBinding
(“addItemToCart");
02. Map params = operationBinding.getParamsMap();
03. params.put(“productId“,);
04. Object result = operationBinding.execute();
…

Executing Bound Methods on the
JSF Page Load
• Actions in the executable
section are invoked when the
page loads.
• Actions bind to methods or
actions in the bindings
definition.
• You can use EL to determine
the condition that is on when
the action is executed.

Context Objects
FacesContext:
• Is a static class that provides access to information such as
application messages, render kits, ViewRoots,
ExternalContext, and so on
• Represents the current request that is processed
ExternalContext:
• Provides access to the world outside JSF
ADFFacesContext:
• Is a context object to support ADF Faces–specific functionality:
– Partial page rendering (PPR)
– Skinning
– Oracle Help
– Dialog framework support

JavaServer Faces
Backing Beans
Backing beans are a type of managed bean.
• Use one backing bean per page, if needed.
– This gives you one place to manage the code.
– It contains logic and properties for some UI components.
– JDeveloper can create this backing bean for you, but you
may want your own superclass.
• Prune the contents of the backing bean; code “interesting”
objects only.
• Place backing beans in the request scope.
• Use consistent naming and packaging.

Summary
In this lesson, you should have learned how to:

• Define key JSF terms
• Describe the JSF architecture with ADF
• Differentiate between managed and backing beans
• Create and reference managed beans
• Set and use managed properties
• Use context objects to access the application

Practice 7 Overview:
Working with JSF and Managed Beans
This practice covers the following topics:
• Adding a method to delete order line items
• Creating a managed bean to track selected line items
• Including a button to initiate delete

Working With Managed Beans and Javaserver Faces

Încărcat de

Informații document

Titlu original

Drepturi de autor

Formate disponibile

Partajați acest document

Partajați sau inserați document

Opțiuni de partajare

Vi se pare util acest document?

Este necorespunzător acest conținut?

Drepturi de autor:

Formate disponibile

Working With Managed Beans and Javaserver Faces

Încărcat de

Drepturi de autor:

Formate disponibile

Working with Managed Beans and

Copyright © 2008, Oracle. All rights reserved.

After completing this lesson, you should be able to do the

7-2 Copyright © 2008, Oracle. All rights reserved.

• Key Terms and Concepts

7-3 Copyright © 2008, Oracle. All rights reserved.

JSF simplifies Web development because it:

7-4 Copyright © 2008, Oracle. All rights reserved.

• UI component: JSF is component based.

7-5 Copyright © 2008, Oracle. All rights reserved.

7-6 Copyright © 2008, Oracle. All rights reserved.

7-7 Copyright © 2008, Oracle. All rights reserved.

• To create Web-tier application object methods for handling

7-8 Copyright © 2008, Oracle. All rights reserved.

Renderer generates Event

translates value UI Component Contained in View

Validator Model objects

7-9 Copyright © 2008, Oracle. All rights reserved.

• Use only JSF:

FacesContext fctx = FacesContext.getCurrentInstance();

ELContext elctx = fctx.getELContext();

7 - 10 Copyright © 2008, Oracle. All rights reserved.

• Key Terms and Concepts

7 - 11 Copyright © 2008, Oracle. All rights reserved.

Managed properties Java code

ELContext elctx = fctx.getELContext();

7 - 12 Copyright © 2008, Oracle. All rights reserved.

• #{somevar}: Value of the variable named somevar

7 - 13 Copyright © 2008, Oracle. All rights reserved.

• #{user.name} and #{user["name"]}: Check at

7 - 14 Copyright © 2008, Oracle. All rights reserved.

• Code example: JSP value attribute references EL that gets

7 - 15 Copyright © 2008, Oracle. All rights reserved.

• It is evaluated at other phases of a page life cycle as

• Code example: JSF value attribute references EL that

7 - 16 Copyright © 2008, Oracle. All rights reserved.

• Key Terms and Concepts

7 - 17 Copyright © 2008, Oracle. All rights reserved.

• Managed beans are optional and can be used to:

7 - 18 Copyright © 2008, Oracle. All rights reserved.

• Can be any Java object, such as maps and lists, as long

7 - 19 Copyright © 2008, Oracle. All rights reserved.

• Usage in Java code:

ELContext elctx = fctx.getELContext();

7 - 20 Copyright © 2008, Oracle. All rights reserved.

7 - 21 Copyright © 2008, Oracle. All rights reserved.

Both value binding and variable resolvers hard code values.

FacesContext fctx = FacesContext.getCurrentInstance();

ELContext elctx = fctx.getELContext();

ELResolver elResolver = fctx.getApplication().getELResolver();

7 - 22 Copyright © 2008, Oracle. All rights reserved.

Add a property to one managed bean that references the

7 - 23 Copyright © 2008, Oracle. All rights reserved.

7 - 24 Copyright © 2008, Oracle. All rights reserved.

• EL accessing managed bean:

7 - 25 Copyright © 2008, Oracle. All rights reserved.

JSF pages can create value bindings to the ADF binding

• The “bindings” object is created by the ADF servlet filter

7 - 26 Copyright © 2008, Oracle. All rights reserved.

Getting access to the binding in the code (best practice):

• Add getters and setters for

7 - 27 Copyright © 2008, Oracle. All rights reserved.

• Include process logic or write conditional logic to return