Then the problem might be that the logging module does not follow the
fault path. If that is so, then that is a bug in loging module.
Thanks,
Samisa...
Sérgio Gomes wrote:
Hi Samisa,
Yes I have, the little snippet I posted above is from the log (it gets
sent to the console).
--Sérgio
---
On
Hi Samisa,
Yes I have, the little snippet I posted above is from the log (it gets
sent to the console).
--Sérgio
---
On Fri, Dec 19, 2008 at 02:30, Samisa Abeysinghe wrote:
> Have you engaged logging module?
>
> Samisa...
>
> Sérgio Gomes wrote:
>>
>> Bump. Has anyone come across this issue bef
Have you engaged logging module?
Samisa...
Sérgio Gomes wrote:
Bump. Has anyone come across this issue before?
--Sérgio
---
On Tue, Dec 16, 2008 at 16:48, Sérgio Gomes wrote:
Hi there,
Looks like every time I get a SOAP fault back from a service, using my
Axis2/C client (ADB generated s
Bump. Has anyone come across this issue before?
--Sérgio
---
On Tue, Dec 16, 2008 at 16:48, Sérgio Gomes wrote:
> Hi there,
>
> Looks like every time I get a SOAP fault back from a service, using my
> Axis2/C client (ADB generated stubs), the log comes out empty, e.g.:
>
> [Tue Dec 16 16:37:47 2
Hi there,
Looks like every time I get a SOAP fault back from a service, using my
Axis2/C client (ADB generated stubs), the log comes out empty, e.g.:
[Tue Dec 16 16:37:47 2008] [info] Input message: http://schemas.xmlsoap.org/soap/envelope/";
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
