You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cxf.apache.org by "Daniel Kulp (Updated) (JIRA)" <ji...@apache.org> on 2012/01/23 19:38:40 UTC

[jira] [Updated] (CXF-4055) Parameter Handler not Invoked if Constructor or Static Methods Succeed

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

Daniel Kulp updated CXF-4055:
-----------------------------

    Fix Version/s:     (was: 2.5.2)
    
> Parameter Handler not Invoked if Constructor or Static Methods Succeed
> ----------------------------------------------------------------------
>
>                 Key: CXF-4055
>                 URL: https://issues.apache.org/jira/browse/CXF-4055
>             Project: CXF
>          Issue Type: Bug
>          Components: JAX-RS
>    Affects Versions: 2.5.1
>            Reporter: Jonathan Haber
>            Priority: Minor
>              Labels: injectionutils, jaxrs, parameterhandler, queryparam
>   Original Estimate: 3h
>  Remaining Estimate: 3h
>
> My reading of InjectionUtils suggests that when performing type conversion, custom parameter handlers appear to be the last resort. If the object has a single-string constructor or a static valueOf/fromString method and any of these succeed, custom parameter handlers will not be invoked. 
> This is causing issues in our application where users are able to define their own date formats and the string values are passed as query parameters. We implemented ParameterHandler<Date> and in the fromString body parse the string value according to the specific user's date format. But depending on the date format, the String constructor of java.util.Date may or may not throw an exception depending on the specific date format. If it does not succeed, our parameter handler is reached and all is well. But if it does "succeed" this date will be used by CXF and our parameter handler is never reached (This is a problem because even if the constructor doesn't throw an exception, the date is usually parsed incorrectly and represents the wrong date).

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira