[jira] [Updated] (CXF-5072) Add capability in Jettison to default the namespace

["Tom Stark (JIRA)" <ji...@apache.org>]

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

Tom Stark updated CXF-5072:
---------------------------

    Attachment: apache-cxf-issue.zip
    
> Add capability in Jettison to default the namespace
> ---------------------------------------------------
>
>                 Key: CXF-5072
>                 URL: https://issues.apache.org/jira/browse/CXF-5072
>             Project: CXF
>          Issue Type: Improvement
>          Components: JAXB Databinding
>    Affects Versions: 2.5.2
>            Reporter: Tom Stark
>         Attachments: apache-cxf-issue.zip
>
>
> 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":{"user-role.name":"admin"},"user.username":"fred","user.first-name":"Fred", "user.last-name":"Person"}}
> What is preferable is:
> {"user.user":{"user-role.user-role":{"name":"admin"},"username":"fred","first-name":"Fred", "last-name":"Person"}}
> 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 is:
> {"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: http://www.atlassian.com/software/jira