cxf-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Daniel Kulp (JIRA)" <j...@apache.org>
Subject [jira] Resolved: (CXF-2374) Handle possible number format exception when reading primitive param
Date Mon, 03 Aug 2009 20:03:14 GMT

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

Daniel Kulp resolved CXF-2374.
------------------------------

       Resolution: Fixed
    Fix Version/s: 2.2.4
         Assignee: Daniel Kulp

> Handle possible number format exception when reading primitive param
> --------------------------------------------------------------------
>
>                 Key: CXF-2374
>                 URL: https://issues.apache.org/jira/browse/CXF-2374
>             Project: CXF
>          Issue Type: Bug
>          Components: REST
>            Reporter: Jorge L. Williams
>            Assignee: Daniel Kulp
>            Priority: Minor
>             Fix For: 2.2.4
>
>         Attachments: 0001-Handle-possible-number-format-exception-when-reading.patch
>
>
> We ran into this issue in JAX-RS:   A request to something like /path/
> to/{id} where {id} is expected to be an integer would throw a
> NumberFormatException in the case where we send something other than
> an integer (/path/to/bla, for example).  The NumberFormatException
> didn't find its way to our ExceptionMapper and resulted in an XMLFault
> being serialized which is wrong.
> The attached patch fixes things for us.  We simply capture the NFE and
> resend it as a WebApplicationException -- we send a  404 when we're
> dealing with path params and 400 otherwise.  The patch is against the
> current trunk but honestly we've really only tested against 2.2.2 --
> since that's what we're using :-)

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message