You are viewing a plain text version of this content. The canonical link for it is here.

Posted to commits@wicket.apache.org by "SoulSpirit (JIRA)" <ji...@apache.org> on 2012/10/25 16:19:12 UTC

[jira] [Updated] (WICKET-4839) DateConverter should be thread-safe

     [ https://issues.apache.org/jira/browse/WICKET-4839?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

SoulSpirit updated WICKET-4839:
-------------------------------

    Attachment: quickstart.zip

The attacched project demonstrates that instances of DateFormat managed by org.apache.wicket.util.convert.converter.DateConverter are shared between different requests and different sessions, thus DateConverter should be thread-safe.

The application writes to the console the instance number of the DateFormat instance used by DateConverter, and it's clear it doesn't change refreshing the page or running a different HTTP session, provided the Locale assigned by Wicket to the user doesn't change.

                
> DateConverter should be thread-safe
> -----------------------------------
>
>                 Key: WICKET-4839
>                 URL: https://issues.apache.org/jira/browse/WICKET-4839
>             Project: Wicket
>          Issue Type: Bug
>          Components: wicket
>    Affects Versions: 1.4.19, 6.2.0
>            Reporter: SoulSpirit
>         Attachments: quickstart.zip
>
>
> Please consider the linked issue WICKET-4833.
> I had to open a new issue because I cannot attach the quickstart project I've prepared to a closed issue.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira