[SWS-929] Fix namespace prefix handling with StreamingPayload Created: 15/Dec/15  Updated: 15/Dec/15  Resolved: 15/Dec/15

Status: Closed
Project: Spring Web Services
Component/s: None
Affects Version/s: 2.2.3
Fix Version/s: 2.2.4

Type: Bug Priority: Minor
Reporter: Greg Turnquist Assignee: Greg Turnquist
Resolution: Complete Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified


 Description   

The getName() method in JaxbStreamingPayload doesn't report the actual
namespace prefix that is later generated by the writeTo method. With
Axiom 1.2.13 that didn't cause problems, but 1.2.14 is less lenient,
causing an error as described in AXIOM-463.

This change:

  • Updates the StreamingPayload documentation to specify that the
    namespace prefix in the QName returned by getName() has no significance
    (which is effectively how things are currently).
  • Updates AxiomSoapBody so that it Axiom is aware that the namespace
    prefix of the created OMSourcedElement is unknown.
  • Modifies the unit test for setStreamingPayload so that it uses a
    StreamingPayload with a prefix mismatch.

Generated at Thu Dec 14 17:05:46 UTC 2017 using JIRA 6.4.14#64029-sha1:ae256fe0fbb912241490ff1cecfb323ea0905ca5.