You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@commons.apache.org by bu...@apache.org on 2004/02/10 22:36:50 UTC

DO NOT REPLY [Bug 26827] - DateLocaleConverter is not thread-safe

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=26827>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=26827

DateLocaleConverter is not thread-safe





------- Additional Comments From rdonkin@apache.org  2004-02-10 21:36 -------
hmmm....

i take it that you are referring to:

<code>
public class DateLocaleConverter extends BaseLocaleConverter {

    // ----------------------------------------------------- Instance Variables

    /** All logging goes through this logger */
    private static Log log = LogFactory.getLog(DateLocaleConverter.class);

    /** The Date formatter */
    private SimpleDateFormat formatter = getPattern(pattern, locale);
</code>

right?

i'm not convinced by your assertion that this is not thread safe. i think that constructors are by their 
nature non-reentrant (for an instance) and effectively act as if the method (and any called either directly 
or indirectly from within a constructor) is synchronized.

of course, i'd be happy to be proved wrong if you can supply a solid reference or a good test case 
demonstrating the problem.

---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org