|
[
Permlink
| « Hide
]
Tom Fennelly added a comment - 14/Sep/07 07:01 AM - edited
Pavel, you may already have figured this out yourself, but you can work around this in the short term by implementing your own decoder impl (a modified version of CalendarDecoder perhaps) and specifying it manually in the config. If you do this, please contribute back a patch.
I have created my own calendar decoder called MyCalendarDecoder. Unfortunatelly I was not able to reuse any code from CalendarDecoder because fields "format" and "decoder" are private (I would need that field to be protected). So I have used "copy and paste" style.
That's great Pavel. Thanks.
Will get this into the main codeline ASAP. Committed revision 422.
Added languageCode and country code as optional configuration parameters. Sorry Dan... there's a TimeZone issue with the test on this. Setting the Locale doesn't effect the TimeZone... it still comes back as the local TimeZone, causing the test to fail for me (coz I'm GMT and not CET).
Reopening this as I suspect a bug.
Committed with revsion : 513
Updated the tests, I hade created an invalid locale previously which just happened to let the test pass. |
|||||||||||||||||||||||||||||||||||||||||||||||