[AXIOM-122] The sequence of events produced by OMStAXWrapper with inlineMTOM=false is inconsistent

• Type: Bug
• Status: Closed
• Priority: Minor
• Resolution: Fixed
• Affects Version/s: 1.2.8
• Fix Version/s: 1.2.9
• Assignee: Andreas Veithen
• Reporter: Andreas Veithen
• Created: 06/Jul/09 20:53
• Updated: 27/Mar/11 11:43
• Resolved: 12/Jul/09 13:28

Description

The inlineMTOM=false mode in OMStAXWrapper (introduced by WSCOMMONS-344) only works in a consistent way if the underlying StAX stream comes from an MTOM/XOP message, but not if the underlying stream uses the IS_DATA_HANDLERS_AWARE extension. Indeed:

• If the OMStAXWrapper is generating events from the Axiom tree (because caching is enabled or the tree has already been built), then the change in WSCOMMONS-344 makes sure that an XOP:Include element is returned for optimized binary content.
• On the other hand, if caching is disabled and the Axiom tree has not been built, OMStAXWrapper delegates to the underlying stream reader. If there is optimized binary content, it will be represented as a CHARACTERS event instead of an XOP:Include element (as in inlineMTOM=true mode).

Since this issue only occurs if inlineMTOM=false (which is not the default) and the underlying stream uses the IS_DATA_HANDLERS_AWARE extension (which is generally only the case for a stream coming from another Axiom tree or generated by a databinding framework), this issue is less serious than WSCOMMONS-485.

Issue Links

• blocks: AXIOM-255 The sequence of events produced by OMStAXWrapper for XOP:Include is inconsistent
• relates to: AXIOM-202 OMStaXWrapper Does Not Support Optimized OMText as an XOP:Include