org.apache.myfaces.trinidaddemo.email
Class MessagesBackingBean

java.lang.Object
  org.apache.myfaces.trinidaddemo.email.MessagesBackingBean

public class MessagesBackingBean
extends Object

Backing bean for the "messages" page.

Constructor Summary

MessagesBackingBean()

Method Summary

String	compact()
String	first()
FolderData	getFolder()
UIXTable	getMessagesTable()
boolean	isFirstEnabled()
boolean	isLastEnabled()
String	last()
void	performDelete(javax.faces.event.ActionEvent event)
String	refresh()
void	saveFirst(RangeChangeEvent event) Remember the "first" row for the table.
void	setFolder(FolderData folder)
void	setMessagesTable(UIXTable table)

Methods inherited from class java.lang.Object

clone, equals, finalize, getClass, hashCode, notify, notifyAll, toString, wait, wait, wait

Constructor Detail

MessagesBackingBean

public MessagesBackingBean()

Method Detail

compact

public String compact()
               throws javax.mail.MessagingException

Throws:

javax.mail.MessagingException

refresh

public String refresh()

setFolder

public void setFolder(FolderData folder)

getFolder

public FolderData getFolder()

setMessagesTable

public void setMessagesTable(UIXTable table)

getMessagesTable

public UIXTable getMessagesTable()

isFirstEnabled

public boolean isFirstEnabled()

isLastEnabled

public boolean isLastEnabled()

first

public String first()

last

public String last()

saveFirst

public void saveFirst(RangeChangeEvent event)

Remember the "first" row for the table. If we didn't do this, there wouldn't be any issue as we page from row to row within this page. The problem comes when we return to this folder (after showing a message, for example). There ought to be a better solution to this problem.

performDelete

public void performDelete(javax.faces.event.ActionEvent event)