|
Home > Archive > WebSphere Portal Server > April 2007 > Difference in setting actions in Page Code or Backing Bean vs
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
Difference in setting actions in Page Code or Backing Bean vs
|
|
|
| This is related to jsr168 jsf portlet.
Normally when we associate an action with a command button the corresponding
action or method defination is put in the page code class.
However if we want we can create our own Java bean ,maked it managed bean and put the action in it and make accordingly changes to the button.
Example
<hx:commandExButton type="submit" value="Submit" id="button1"
styleClass="commandExButton" action="#{sampleManagedBean.actionForDate}"></hx:commandExButton>
I want to know what is the difference in terms of life management , or performance or anything else in putting these in either place.
I mean what are the ups and downs or advanatge and limitation of either approach.
| |
| yurykats 2007-04-24, 1:24 pm |
| There's no difference. A bean is a bean, a method is a method. The only advantage pagecode offers is the integreation with Quick Edit View in RAD, if you are using this view, it will be creating the method in pagecode.
| |
|
| thanks for the update yury
|
|
|
|
|