cxf-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sergey Beryozkin (JIRA)" <>
Subject [jira] [Resolved] (CXF-5072) Add capability in Jettison to default the namespace
Date Sun, 09 Jun 2013 18:13:20 GMT


Sergey Beryozkin resolved CXF-5072.

    Resolution: Won't Fix
      Assignee: Sergey Beryozkin
> Add capability in Jettison to default the namespace
> ---------------------------------------------------
>                 Key: CXF-5072
>                 URL:
>             Project: CXF
>          Issue Type: Improvement
>          Components: JAX-RS, JAXB Databinding
>    Affects Versions: 2.5.2
>            Reporter: Tom Stark
>            Assignee: Sergey Beryozkin
>         Attachments:
> When using Jettison, it would be preferable to configure Jettison to allow for the namespace
to be the same as what was last used.  For example, attached is a simple user object that
has a long namespace name.  I can use Jettison to alias the namespace to something shorter
but I still need to fully-qualify all members of the user object in JSON for Jettison to properly
marshal all of the fields to the java object.
> For example:
> {"user.user":{"user-role.user-role":{"":"admin"},"user.username":"fred","user.first-name":"Fred",
> What is preferable is:
> {"user.user":{"user-role.user-role":{"name":"admin"},"username":"fred","first-name":"Fred",
> In this case, the beginning of a new namespace is used for objects that need it.  After
the object is defined, the namespace reverts to the previous namespace.
> Output is fine since the "ignoreNamespace" strips all namespaces and the resulting JSON
> {"user":{"user-role":{"name":"admin"},"username":"fred","first-name":"Fred","last-name":"Person"}}
> Note that the attachments have been edited to remove proprietary information and probably
will not compile by themselves.

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:

View raw message