Great, one less call to hungry TextProvider😉.
Passes my tests, and screen wise, for me, each formatter matches exactly
struts.date.formatter=dateTimeFormatter
struts.date.formatter=simpleDateFormatter
##
Checking my beans, all of my dates are of type java.sql.Timestamp
(datetime on mariadb)
On class
Date.end(Writer writer, String body)
matches java.util.Date
Object dateObject = findValue(name);
if (dateObject instanceof java.util.Date) {
date = ((java.util.Date) dateObject).toInstant().atZone(tz);
}
I don't have any LocalDateTime (java.time) fields to test (would use
myBean.getMyDate().toLocalDateTime() as MyDate is Timestamp and then use
the java.time classes, dates now have become messy🙁).
On 21/02/2022 18:32, Lukasz Lenart wrote:
pon., 21 lut 2022 o 09:29 Greg Huber <gregh3...@gmail.com> napisał(a):
When using branch : WW-5016-uses-proper-format
struts.date.formatter=simpleDateFormatter
I get lots of these warnings
2022-02-21 08:21:36,677 WARN
com.opensymphony.xwork2.util.AbstractLocalizedTextProvider
AbstractLocalizedTextProvider:findDefaultText - Missing key
[struts.date.format] in bundles [[ApplicationResources,
org/apache/struts2/struts-messages,
com/opensymphony/xwork2/xwork-messages]]!
I don't have a struts.date.format property.
Good catch, fixed! Can you try again?
Regards
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@struts.apache.org
For additional commands, e-mail: dev-h...@struts.apache.org
