]
Alejandro Guizar resolved BPEL-222.
-----------------------------------
Resolution: Done
Introduced the SoapFaultWriter hierarchy.
soap fault message production fails under jbossws 1.0.3 and above
-----------------------------------------------------------------
Key: BPEL-222
URL:
http://jira.jboss.com/jira/browse/BPEL-222
Project: JBoss jBPM BPEL
Issue Type: Task
Security Level: Public(Everyone can see)
Components: Engine
Reporter: Alejandro Guizar
Assigned To: Alejandro Guizar
Fix For: jBPM BPEL 1.1 beta 3
Because of a change in the saaj implementation first introduced in jbossws 1.0.3, jbpm
bpel can no longer use the same code to produce a fault message under both the old and the
new services stack.
The proposed solution is to introduce a class hierarchy for creating fault messages
modeled after the Strategy pattern. This hierarchy encapsulates the different ways a fault
message is created. Two strategies exist at this time:
a) The default strategy adds a soap:Fault element with a call to SOAPBody.addFault().
This is what a developer does normally. This should work on most stacks, including
JBossWS. It does *not* work under the old Axis-based stack used JBoss AS 4.0.3 and
earlier.
b) The backwards compatibility strategy adds a soap:Fault with a call to
SOAPBody.addChildElement("Fault", prefix, SOAPConstants.URI_NS_SOAP_ENVELOPE).
Altough JBossWS4EE allows to add a SOAPFault, the marshaling code is broken and no detail
element gets written.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: