That's what I was trying to avoid - find different solutions for each case.
Cause I might even just do ${myDateField} and I would expect it to be formatted
as I need.
Since the project is already deployed I don't want to go through each case and
occurrence to check if it is using valid format. I was looking for a
quick/smart fix.
Anyway that doesn't seem possible at least not now.
Thanks for helping.
-------- Оригинално писмо --------
От: Lance Java lance.j...@googlemail.com
Относно: Re: Global setting for date format
До: users@tapestry.apache.org
Изпратено на: Сряда, 2012, Септември 5 17:45:13 EEST
> For example in beandisplay component
You will need to contribute a BeanBlockContribution to
BeanBlockOverrideSource. This will require you to create a page which
contains the block that you would like to use instead (the override).
eg:
MyPage.java
@Environmental
@Property
private PropertyOutputContext context;
MyPage.tml
AppModule.java
public static void
contributeBeanBlockOverrideSource(Configuration
configuration {
configuration.add(new DisplayBlockContribution(DataTypeConstants.DATE,
"MyPage", "myDate"));
}
--
View this message in context:
http://tapestry.1045711.n5.nabble.com/Global-setting-for-date-format-tp5716054p5716065.html
Sent from the Tapestry - User mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
For additional commands, e-mail: users-h...@tapestry.apache.org
