You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cxf.apache.org by "Sergey Beryozkin (JIRA)" <ji...@apache.org> on 2015/09/01 11:30:45 UTC
[jira] [Commented] (CXF-6573) AccessToken doesn't serialize with
snake-case
[ https://issues.apache.org/jira/browse/CXF-6573?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14725062#comment-14725062 ]
Sergey Beryozkin commented on CXF-6573:
---------------------------------------
Sorry, not sure what you mean. AccessTokenService has @Produces("application/json"), JAXB is not expected to be involved here. OAuthJSONProvider writes the token response.
Can you clarify please ?
> AccessToken doesn't serialize with snake-case
> ---------------------------------------------
>
> Key: CXF-6573
> URL: https://issues.apache.org/jira/browse/CXF-6573
> Project: CXF
> Issue Type: Wish
> Components: JAX-RS Security
> Affects Versions: 3.1.2
> Reporter: Karl von Randow
> Priority: Minor
>
> The org.apache.cxf.rs.security.oauth2.common.AccessToken class doesn't declare and JAXB (or other) annotations to influence how it is serialized. So it uses the default serialization style of the JAXB context.
> In my case this is camel case.
> This means that the AccessToken response from the AccessTokenService uses camel case. The OAuth docs _appear_ (I'm not a scholar of them) to indicate that it should be snake case.
> Is that true? Is this a thing? Would it be something you'd consider, adding `@XmlElement(name = "token_key")` annotations? That would be a breaking change for existing users...
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)