[AXIOM-320] Allow StAXSOAPModelBuilder to fallback to XML infoset if the document is not SOAP

• Type: Improvement
• Status: Reopened
• Priority: Minor
• Resolution: Unresolved
• Assignee: Unassigned
• Reporter: Andreas Veithen
• Created: 20/Dec/08 21:20
• Updated: 23/Oct/16 14:30

Description

Currently, StAXOMBuilder can only be used to build an XML infoset, while StAXSOAPModelBuilder can only be used to build a SOAP infoset model. However in some cases it is impossible to determine beforehand whether a document or message is SOAP or plain XML. To handle this case with the current version of Axiom, the only available strategy is to start processing the document with one of the two builders and restart the processing with the other if the document doesn't match the type of builder. The proposal is to modify StAXSOAPModelBuilder so that it (optionally) falls back to plain XML if it detects that the document element is not a SOAP envelope. This should be feasible since StAXSOAPModelBuilder extends StAXOMBuilder.

Issue Links

• is related to: AXIS2-4184 SOAP Message Body Based dispatcher does not work without SOAPAction