I have had to supply an extra format String as follows: /** The patterns used for parsing dates */ private static final String[] DATE_PATTERNS = { PATTERN_RFC1123, PATTERN_RFC1036, PATTERN_ASCTIME, "EEE, dd-MMM-yyyy HH:mm:ss z", "EEE, dd-MMM-yyyy HH-mm-ss z", "EEE, dd MMM yy HH:mm:ss z", "EEE dd-MMM-yyyy HH:mm:ss z", "EEE dd MMM yyyy HH:mm:ss z", "EEE dd-MMM-yyyy HH-mm-ss z", "EEE dd-MMM-yy HH:mm:ss z", "EEE dd MMM yy HH:mm:ss z", "EEE,dd-MMM-yy HH:mm:ss z", "EEE,dd-MMM-yyyy HH:mm:ss z", "EEE, dd-MM-yyyy HH:mm:ss z", // Extra for non-compliant site "dd-MMM-yyyy HH:mm:ss zzz" }; to the DateParser class and produce my own build, as the DateParser does not seem to provide pluggability for non-compliant sites. Can anyone tell me when this situation may change so I no longer have to produce a one-man code fork?
C Johnson --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]