The first time we navigate to the messages.jsp
page, whether by a JSF postback (faces request) or a direct browser GET request (non-faces request), the page will try to resolve the messageList
context variable. Since this context variable is not initialized, Seam will call the factory method findMessages()
, which performs a query against the database and results in a DataModel
being outjected. This DataModel
provides the row data needed for rendering the <h:dataTable>
.
When the user clicks the <h:commandLink>
, JSF calls the select()
action listener. Seam intercepts this call and injects the selected row data into the message
attribute of the messageManager
component. The action listener fires, marking the selected Message
as read. At the end of the call, Seam outjects the selected Message
to the context variable named message
. Next, the EJB container commits the transaction, and the change to the Message
is flushed to the database. Finally, the page is re-rendered, redisplaying the message list, and displaying the selected message below it.
If the user clicks the <h:commandButton>
, JSF calls the delete()
action listener. Seam intercepts this call and injects the selected row data into the message
attribute of the messageList
component. The action listener fires, removing the selected Message
from the list, and also calling remove()
on the EntityManager
. At the end of the call, Seam refreshes the messageList
context variable and clears the context variable named message
. The EJB container commits the transaction, and deletes the Message
from the database. Finally, the page is re-rendered, redisplaying the message list.