ode-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Håkon Sagehaug <hakon.sageh...@uni.no>
Subject Re: Extracting fault messages using the instance api
Date Fri, 28 Oct 2011 06:55:44 GMT
Hi,

The soap fault looks like this

<soapenv:Body>
 <soapenv:Fault>
    <faultcode>soapenv:Server</faultcode>
    <faultstring>URI is not absolute</faultstring>
   <detail />
</soapenv:Fault>
</soapenv:Body>

So I guess it's not recorded, are there any other ways of getting the fault
message out of the Instance mgnt? Can I do something  if I catch the fault?

cheers, Håkon

On 27 October 2011 20:28, Waruna Ranasinghe <warunapww@gmail.com> wrote:

> Hi Hakon,
>
> IIRC, Fault message get saves only if the soap fault contains an
> application
> specific fault, that means only if there are content in the <details>
> element.
>
> Thanks,
> Waruna
>
> 2011/10/26 Håkon Sagehaug <hakon.sagehaug@uni.no>
>
> > Hi all,
> >
> > We have a service on top of ode InstanceMgnt api for extracting messages
> > exchanged in a bpel process, basically calling #getCommunication and
> refine
> > the result a bit. All works fine when the process runs fine, but if one
> of
> > the services , for some reason, throws a soap fault I cat seem to get
> this
> > fault message "out". I see it in the logs. If I do a #getInstance I can
> see
> > that is has a failure, but have not figured out how to get the soap fault
> > message. So wondering if it is possible, to do this?
> >
> > cheers, Håkon
> >
>
>
>
> --
> -----------------------------------------------------
> Regards,
> Waruna Ranasinghe
>
> www.wso2.com - "Lean . Enterprise . Middleware"
>
> blog: http://warunapw.blogspot.com
> twitter: http://twitter.com/warunapww
> http://lk.linkedin.com/in/waruna
> www.facebook.com/waruna.ranasinghe
>

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