[JBoss JIRA] Created: (BPEL-286) SOAP Communication Exceptions should be catchable inside the process
2:43 p.m.
SOAP Communication Exceptions should be catchable inside the process
--------------------------------------------------------------------
Key: BPEL-286
URL: http://jira.jboss.com/jira/browse/BPEL-286
Project: JBoss jBPM BPEL
Issue Type: Feature Request
Security Level: Public (Everyone can see)
Components: Engine
Affects Versions: jBPM BPEL 1.1 beta 3
Environment: jBPM BPEL 1.1 beta 3
Reporter: Sebastian Cao
Assigned To: Alejandro Guizar
Fix For: jBPM BPEL 1.1 GA
It'll be very valuable if Web Services exceptions due to communications or socket
exceptions can be trapped inside the bpel process using <catch> and <catch
all> besides being reported as Java Exceptions by the WS Stack.
--
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
6:15 a.m.
New subject: [JBoss JIRA] Resolved: (BPEL-286) SOAP Communication Exceptions should be catchable inside the process
[ http://jira.jboss.com/jira/browse/BPEL-286?page=all ]
Alejandro Guizar resolved BPEL-286.
-----------------------------------
Resolution: Done
jBPM BPEL now raises SOAP exceptions thrown during web service invocations as a BPEL fault
named jbpm:invocationFailure.
Note that said exceptions cover both transport-level errors (e.g. dropped connections) and
application-level errors (e.g. malformed SOAP messages). Since SAAJ does not differentiate
between the two, we cannot do it either.
SOAP Communication Exceptions should be catchable inside the process
--------------------------------------------------------------------
Key: BPEL-286
URL: http://jira.jboss.com/jira/browse/BPEL-286
Project: JBoss jBPM BPEL
Issue Type: Feature Request
Security Level: Public(Everyone can see)
Components: Engine
Affects Versions: jBPM BPEL 1.1 beta 3
Environment: jBPM BPEL 1.1 beta 3
Reporter: Sebastian Cao
Assigned To: Alejandro Guizar
Fix For: jBPM BPEL 1.1 GA
It'll be very valuable if Web Services exceptions due to communications or socket
exceptions can be trapped inside the bpel process using <catch> and <catch
all> besides being reported as Java Exceptions by the WS Stack.
--
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
8:56 p.m.
New subject: [JBoss JIRA] Reopened: (BPEL-286) SOAP Communication Exceptions should be catchable inside the process
[ http://jira.jboss.com/jira/browse/BPEL-286?page=all ]
Alejandro Guizar reopened BPEL-286:
-----------------------------------
Reopening because two-way invocations that result in SOAP communication exceptions do
raise a fault, but later encounter a null reference:
java.lang.NullPointerException
at
org.jbpm.bpel.integration.jms.JmsIntegrationService.replaceMessageType(JmsIntegrationService.java:217)
at
org.jbpm.bpel.integration.jms.JmsIntegrationService.invoke(JmsIntegrationService.java:185)
at org.jbpm.bpel.integration.def.InvokeAction.execute(InvokeAction.java:76)
SOAP Communication Exceptions should be catchable inside the process
--------------------------------------------------------------------
Key: BPEL-286
URL: http://jira.jboss.com/jira/browse/BPEL-286
Project: JBoss jBPM BPEL
Issue Type: Feature Request
Security Level: Public(Everyone can see)
Components: Engine
Affects Versions: jBPM BPEL 1.1 beta 3
Environment: jBPM BPEL 1.1 beta 3
Reporter: Sebastian Cao
Assigned To: Alejandro Guizar
Fix For: jBPM BPEL 1.1 GA
It'll be very valuable if Web Services exceptions due to communications or socket
exceptions can be trapped inside the bpel process using <catch> and <catch
all> besides being reported as Java Exceptions by the WS Stack.
--
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
9:29 p.m.
New subject: [JBoss JIRA] Updated: (BPEL-286) SOAP Communication Exceptions should be catchable inside the process
[ http://jira.jboss.com/jira/browse/BPEL-286?page=all ]
Alejandro Guizar updated BPEL-286:
----------------------------------
Fix Version/s: jBPM BPEL 1.1.1
(was: jBPM BPEL 1.1 GA)
Affects Version/s: jBPM BPEL 1.1 GA
(was: jBPM BPEL 1.1 beta 3)
SOAP Communication Exceptions should be catchable inside the process
--------------------------------------------------------------------
Key: BPEL-286
URL: http://jira.jboss.com/jira/browse/BPEL-286
Project: JBoss jBPM BPEL
Issue Type: Feature Request
Security Level: Public(Everyone can see)
Components: Engine
Affects Versions: jBPM BPEL 1.1 GA
Environment: jBPM BPEL 1.1 beta 3
Reporter: Sebastian Cao
Assigned To: Alejandro Guizar
Fix For: jBPM BPEL 1.1.1
It'll be very valuable if Web Services exceptions due to communications or socket
exceptions can be trapped inside the bpel process using <catch> and <catch
all> besides being reported as Java Exceptions by the WS Stack.
--
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
3:43 a.m.
New subject: [JBoss JIRA] Resolved: (BPEL-286) SOAP Communication Exceptions should be catchable inside the process
[ http://jira.jboss.com/jira/browse/BPEL-286?page=all ]
Alejandro Guizar resolved BPEL-286.
-----------------------------------
Resolution: Done
NPE has been addressed.
SOAP Communication Exceptions should be catchable inside the process
--------------------------------------------------------------------
Key: BPEL-286
URL: http://jira.jboss.com/jira/browse/BPEL-286
Project: JBoss jBPM BPEL
Issue Type: Feature Request
Security Level: Public(Everyone can see)
Components: Engine
Affects Versions: jBPM BPEL 1.1 GA
Environment: jBPM BPEL 1.1 beta 3
Reporter: Sebastian Cao
Assigned To: Alejandro Guizar
Fix For: jBPM BPEL 1.1.1
It'll be very valuable if Web Services exceptions due to communications or socket
exceptions can be trapped inside the bpel process using <catch> and <catch
all> besides being reported as Java Exceptions by the WS Stack.
--
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
6646
days inactive
6844
days old
4 comments
2 participants
participants (2)
-
Alejandro Guizar (JIRA) -
Sebastian Cao (JIRA)