- For Managers: 8 Ways to Build Trust, 3 to Break It
- Real leaders make space for others to shine. So true and the word "space" is quite meaningful.
- Team Trap #5: Withholding Information
- The Blame Game
From Christopher Avery :
JSF can call a getter more than once per request.
For example in the following JSF file :
<html> <body> <h:dataTable var="car" value="#{carService.cars}"> <h:column> <f:facet name="header"> Model </f:facet> <h:outputText value="#{car.model}"/> </h:column> <h:column> <f:facet name="header"> Year </f:facet> <h:outputText value="#{car.year}"/> </h:column> <h:column> <f:facet name="header"> Manufacturer </f:facet> <h:outputText value="#{car.manufacturer}"/> </h:column> </h:dataTable> </body> </html>
13:39:40 DEBUG : CarService.getCars:17 - qtp17489534-18
13:39:40 DEBUG : CarService.getCars:17 - qtp17489534-18
13:39:40 DEBUG : CarService.getCars:17 - qtp17489534-18
A getter obviously returns a value. This value can be a bean property or a calculated value.
If the value is calculated, this can potentially be a problem.
I googled a bit and found some workarounds.
For me, the last workaround is the best one because you do not have to modify the view.
And thanks to Spring, it's quite simple to add AOP with a few annotations.