ode-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Alexis Midon" <mi...@intalio.com>
Subject Re: Fault exchange between bpel processes
Date Fri, 24 Oct 2008 00:24:06 GMT
It seems to me that your issue and the jira ODE-401 are very similar.
and I think Karthick is baking a patch.

https://issues.apache.org/jira/browse/ODE-401

Alexis


On Thu, Oct 23, 2008 at 8:28 AM, Dalys Sebastian
<sebastian_dalys@yahoo.com>wrote:

> Hi Matthieu,
>
> Thank you for your response. To better troubleshoot this problem, I went
> and created test process samples that would easily reproduce the problem.
>
> In this sample, there are 5 files: The first 2 files implement the
> WSFaultThrower process that just throws a fault. The next 2 files implement
> the WSFaultInvoker process that invokes the WSFaultThrower process. This
> process then should catch the fault thrown by WSFaultThrower and then
> rethrow a new fault to the client.
>
> WSFaultThrower.wsdl
> WSFaultThrower.bpel
> WSFaultInvoker.wsdl
> WSFaultInvoker.bpel
> deploy.xml
>
> I could reproduce the problem by creating soap-ui projects that could
> invoke both services separately. When I invoke FaultThrower service, it just
> throws a standard soap fault to me. But when I invoke WSFaultInvoker, it
> just times out instead of throwing a fault as well.
>
> Please let me know if I am doing something wrong.
>
> Thanks,
> Dalys
>
>
>
> --- On Wed, 10/22/08, Matthieu Riou <matthieu@offthelip.org> wrote:
>
> > From: Matthieu Riou <matthieu@offthelip.org>
> > Subject: Re: Fault exchange between bpel processes
> > To: user@ode.apache.org, sebastian_dalys@yahoo.com
> > Date: Wednesday, October 22, 2008, 10:20 AM
> > On Tue, Oct 21, 2008 at 9:57 PM, Dalys Sebastian
> > <sebastian_dalys@yahoo.com>wrote:
> >
> > > Hi everyone,
> > >
> > > I have 2 bpel processes running within the same folder
> > under
> > > WEB-INF/processes. My first bpel calls my second bpel
> > via an invoke activity
> > > and the second bpel throws a soap standard fault. But,
> > my first bpel process
> > > cannot catch it.
> > >
> > > In my first bpel, I have set:
> > > <ext:failureHandling
> > xmlns:ext="http://ode.apache.org/activityRecovery">
> > >
> > <ext:faultOnFailure>true</ext:faultOnFailure>
> > > </ext:failureHandling>
> > >
> > > I tested the operation of my second bpel via soap-ui
> > and I can see that it
> > > correctly returns a soap-fault. The soap-fault looks
> > exactly like the
> > > specifications and is a standard soap fault.
> > >
> > > But, when the same operation of the second bpel is
> > called by my first bpel,
> > > the fault cannot be caught by the first bpel. I have a
> > catchAll inserted in
> > > the invoke activity to catch the fault. Could anyone
> > please help out? (I am
> > > using ode 1.2)
> > >
> >
> > Could you provide your whole deployment so I can have a
> > look at it and
> > eventually reproduce the problem?
> >
> > Thanks,
> > Matthieu
> >
> >
> > >
> > > Thanks,
> > > Dalys
> > >
> > >
> > >
> > >
> > > __________________________________________________
> > > Do You Yahoo!?
> > > Tired of spam?  Yahoo! Mail has the best spam
> > protection around
> > > http://mail.yahoo.com
> > >
>
>
>
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message