It seems that f:convertDateTime is caching the various parameters such as
timezone, pattern etc... In other words they are loaded the first time the
page is created and never reloaded again even if they are specified as an EL
expression.
For example:
h:outputText value=#{backendBean.time}
.
Worth to include Trinidad ;-)
On Fri, Oct 3, 2008 at 2:44 AM, Sam Witty [EMAIL PROTECTED] wrote:
It seems that f:convertDateTime is caching the various parameters such as
timezone, pattern etc... In other words they are loaded the first time
the
page is created and never reloaded again
If you have the following code:
h:h:outputText#{someBean.user.firstName}/h:outputText
h:h:outputText#{someBean.user.lastName}/h:outputText
h:h:outputText#{someBean.user.age}/h:outputText
and if SomeBean.user() is a call to the db then every one of the above
expressions will cause a trip to the
Yes I absolutely agree, it has to be configurable in some way. It just seems
like such a common issue that I was hoping there was a general solution.
The ELResolver route will certainly work, though as you pointed out it will
have to be some sort of annotation which will look and feel hacky,
Issue Type: Bug
Components: ExtensionsFilter
Affects Versions: 1.1.6, 1.1.7-SNAPSHOT
Reporter: Sam Witty
Priority: Minor
If the servlet mapping is expressed in the following way:
servlet-mapping
servlet-nameFaces Servlet/servlet-name
[
https://issues.apache.org/jira/browse/TOMAHAWK-3?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12614198#action_12614198
]
Sam Witty commented on TOMAHAWK-3:
--
This is still broken in the latest version MyFaces
