[jboss-jira] [JBoss JIRA] Reopened: (BPEL-286) SOAP Communication Exceptions should be catchable inside the process

[Alejandro Guizar (JIRA)]

     [ 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