[
https://issues.apache.org/jira/browse/CXF-6287?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14358432#comment-14358432
]
Sergey Beryozkin edited comment on CXF-6287 at 3/12/15 10:14 AM:
-----------------------------------------------------------------
No problems, I've commented too.
By the way, can you experiment with Jersey 2.0 Client API ? What do they do
with respect to handling such enums ?
was (Author: sergey_beryozkin):
No problems, I've commented too.
By the way, can you experiment with Jersey 2.0 Client API ? What do they do
with respect handling such enums ?
> JAX-RS client should use Enum.value() instead of toString()
> -----------------------------------------------------------
>
> Key: CXF-6287
> URL: https://issues.apache.org/jira/browse/CXF-6287
> Project: CXF
> Issue Type: Improvement
> Components: JAX-RS
> Affects Versions: 3.0.4
> Reporter: Dhiraj Bokde
> Assignee: Sergey Beryozkin
> Priority: Minor
> Fix For: NeedMoreInfo
>
>
> A JAX-RS endpoints that uses an JAXB enumeration as a parameter marshals it
> using {{toString()}} instead of its {{public String value()} method.
> This results in invalid values being marshaled for values, such as
> {{STATUS_UPDATE}} instead of {{status-update}}.
> This requires writing a custom enumeration ParamConverterProvider. Since all
> JAXB enumerations follow standard method patterns for marshaling {{public
> String value()}} and unmarshaling {{public static T fromValue(String
> value)}}, they should be handled by CXF by default.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)