> @@ -51,7 +51,17 @@ public void endElement(String uri, String name, String
> qName) {
> if (qName.equals("ETag")) {
> this.currentETag = currentOrNull(currentText);
> } else if (qName.equals("LastModified")) {
> - this.currentLastModified =
> dateParser.iso8601DateParse(currentOrNull(currentText));
> + try {
> + this.currentLastModified = dateParser
> + .iso8601DateParse(currentOrNull(currentText));
> + } catch (IllegalArgumentException orig) {
> + try {
> + this.currentLastModified = dateParser
> + .iso8601SecondsDateParse(currentOrNull(currentText));
@andrewgaul Also just as a note, this patch follows the sentiments here -
https://github.com/jclouds/jclouds/pull/105#issuecomment-22520277. Config
option might work but one would likely turn it on all the time as it is unclear
when a provider might generate this (evidently valid) date format. I cannot
seem to find any documentation that states the 8601 format timestamps should be
in.
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds/pull/456/files#r15431251
