You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ode.apache.org by "Gary Brown (JIRA)" <ji...@apache.org> on 2009/08/27 18:56:59 UTC
[jira] Created: (ODE-658) BPEL process does not catch fault when
SOAP faultstring contains a qname associated with the fault name
BPEL process does not catch fault when SOAP faultstring contains a qname associated with the fault name
-------------------------------------------------------------------------------------------------------
Key: ODE-658
URL: https://issues.apache.org/jira/browse/ODE-658
Project: ODE
Issue Type: Bug
Components: Axis2 Integration
Affects Versions: 2.0
Reporter: Gary Brown
I have two BPEL processes (Store and CreditAgency), the CreditAgency
throwing a fault back to the Store. In ODE 1.3.3 this works fine, but
when I deploy the same processes to ODE 2.0-Beta2, the Store process
fails to catch the fault. It results in an exception - I guess because
it considers the fault unhandled.
We have also tried using a JAX-WS service implementation of the
CreditAgency. When the faultstring contains the qname for the fault, the
ODE 2.0-Beta2 Store process fails to catch it - but when the faultstring
is any arbitrary text it works fine - I assume because it uses the fault
details to determine the fault to be caught.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (ODE-658) BPEL process does not catch fault when
SOAP faultstring contains a qname associated with the fault name
Posted by "Tammo van Lessen (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/ODE-658?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Tammo van Lessen updated ODE-658:
---------------------------------
Fix Version/s: 2.0-beta3
(was: 1.3.5)
Affects Version/s: 2.0-beta2
(was: 2.0)
> BPEL process does not catch fault when SOAP faultstring contains a qname associated with the fault name
> -------------------------------------------------------------------------------------------------------
>
> Key: ODE-658
> URL: https://issues.apache.org/jira/browse/ODE-658
> Project: ODE
> Issue Type: Bug
> Components: Axis2 Integration
> Affects Versions: 2.0-beta2
> Reporter: Gary Brown
> Fix For: 2.0-beta3
>
> Attachments: creditAgency.zip, store.zip
>
>
> I have two BPEL processes (Store and CreditAgency), the CreditAgency
> throwing a fault back to the Store. In ODE 1.3.3 this works fine, but
> when I deploy the same processes to ODE 2.0-Beta2, the Store process
> fails to catch the fault. It results in an exception - I guess because
> it considers the fault unhandled.
> We have also tried using a JAX-WS service implementation of the
> CreditAgency. When the faultstring contains the qname for the fault, the
> ODE 2.0-Beta2 Store process fails to catch it - but when the faultstring
> is any arbitrary text it works fine - I assume because it uses the fault
> details to determine the fault to be caught.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (ODE-658) BPEL process does not catch fault when
SOAP faultstring contains a qname associated with the fault name
Posted by "Tammo van Lessen (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/ODE-658?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Tammo van Lessen updated ODE-658:
---------------------------------
Fix Version/s: 1.3.5
> BPEL process does not catch fault when SOAP faultstring contains a qname associated with the fault name
> -------------------------------------------------------------------------------------------------------
>
> Key: ODE-658
> URL: https://issues.apache.org/jira/browse/ODE-658
> Project: ODE
> Issue Type: Bug
> Components: Axis2 Integration
> Affects Versions: 2.0
> Reporter: Gary Brown
> Fix For: 1.3.5
>
> Attachments: creditAgency.zip, store.zip
>
>
> I have two BPEL processes (Store and CreditAgency), the CreditAgency
> throwing a fault back to the Store. In ODE 1.3.3 this works fine, but
> when I deploy the same processes to ODE 2.0-Beta2, the Store process
> fails to catch the fault. It results in an exception - I guess because
> it considers the fault unhandled.
> We have also tried using a JAX-WS service implementation of the
> CreditAgency. When the faultstring contains the qname for the fault, the
> ODE 2.0-Beta2 Store process fails to catch it - but when the faultstring
> is any arbitrary text it works fine - I assume because it uses the fault
> details to determine the fault to be caught.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (ODE-658) BPEL process does not catch fault when
SOAP faultstring contains a qname associated with the fault name
Posted by "Gary Brown (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/ODE-658?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Gary Brown updated ODE-658:
---------------------------
Attachment: store.zip
creditAgency.zip
The BPEL processes.
> BPEL process does not catch fault when SOAP faultstring contains a qname associated with the fault name
> -------------------------------------------------------------------------------------------------------
>
> Key: ODE-658
> URL: https://issues.apache.org/jira/browse/ODE-658
> Project: ODE
> Issue Type: Bug
> Components: Axis2 Integration
> Affects Versions: 2.0
> Reporter: Gary Brown
> Attachments: creditAgency.zip, store.zip
>
>
> I have two BPEL processes (Store and CreditAgency), the CreditAgency
> throwing a fault back to the Store. In ODE 1.3.3 this works fine, but
> when I deploy the same processes to ODE 2.0-Beta2, the Store process
> fails to catch the fault. It results in an exception - I guess because
> it considers the fault unhandled.
> We have also tried using a JAX-WS service implementation of the
> CreditAgency. When the faultstring contains the qname for the fault, the
> ODE 2.0-Beta2 Store process fails to catch it - but when the faultstring
> is any arbitrary text it works fine - I assume because it uses the fault
> details to determine the fault to be caught.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.