Bug 1384132

Summary: [GSS](6.4.z) Double namespaces in JAXB generated XML when using Jboss provided JAXB (jaxb-impl-2.2.5.redhat-9)
Product: [JBoss] JBoss Enterprise Application Platform 6 Reporter: Lei Yu <leiyu>
Component: jbossasAssignee: Petr Jurak <pjurak>
Status: CLOSED NOTABUG QA Contact:
Severity: medium Docs Contact:
Priority: medium    
Version: 6.4.2CC: bmaxwell, cdolphy, fnasser, jason.greene, leiyu, pjurak
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2017-02-20 16:23:33 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description Lei Yu 2016-10-12 15:38:38 UTC
Description of problem:

The generated xml using the JAXB shipped with JBoss 6.4.x has double namespace for response: <Response:Response, i.e

<MetaData xmlns=...>
    ...
    <Response:Response xmlns:Response=...>
       ...
    </Response:Response>
</MetaData>

Version-Release number of selected component (if applicable):

jaxb-impl-2.2.5.redhat-9

How reproducible:

Always, for both windows and Linux.


Actual results:

<MetaData xmlns=...>
    ...
    <Response:Response xmlns:Response=...>
       ...
    </Response:Response>
</MetaData>

Expected results:

<MetaData xmlns=...>
    ...
    <Response xmlns:Response=...>
       ...
    </Response>
</MetaData>

Additional info:

Can the JAXB version in EAP 6.4.x be upgraded to 2.2.11?

Comment 3 Chris Dolphy 2016-10-26 16:19:34 UTC
Although the output is awkward, it's not invalid.  If something parsing this has issues, then it's an invalid XML parser.

Comment 11 Brad Maxwell 2017-02-20 16:23:33 UTC
Closing as not a bug, if we get a reproducer we can reopen/revisit