[jboss-jira] [JBoss JIRA] Updated: (BPEL-222) soap message creation fails under jbossws 1.0.3 and above

[Alejandro Guizar (JIRA)]

     [ http://jira.jboss.com/jira/browse/BPEL-222?page=all ]

Alejandro Guizar updated BPEL-222:
----------------------------------

      Component/s: Engine
    Fix Version/s: jBPM BPEL 1.1 beta 3

> soap message creation 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 create 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 of type SOAPFault. This is what a developer normally would do. 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 element of type SOAPElement. Altough jboss ws4ee allows to add a SOAPFault, the marshaling code is broken and no detail entry gets written.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira