Dan,
It would seem that the line of least resistance is to make [] work like
List.
-Original Message-
From: Daniel Kulp [mailto:[EMAIL PROTECTED]
Sent: Friday, October 19, 2007 1:13 PM
To: cxf-user@incubator.apache.org
Cc: Benson Margulies
Subject: Re: JAXB + JAX-WS + faults
: JAXB + JAX-WS + faults
On Friday 19 October 2007, Benson Margulies wrote:
Should we reduce the logging noisiness of this process?
That's a good question. I can definitely see taking the stack trace
off
of it. That's just scary to users. I'd probably change the message
to:
Exception
: Daniel Kulp [mailto:[EMAIL PROTECTED]
Sent: Friday, October 19, 2007 1:01 PM
To: cxf-user@incubator.apache.org
Cc: Benson Margulies
Subject: Re: JAXB + JAX-WS + faults
Benson,
This is a sideaffect of the fixes we did for the Aegis faults with
the JAX-WS frontend. By making
Benson,
This is a sideaffect of the fixes we did for the Aegis faults with the
JAX-WS frontend. By making the WebFaultOutInterceptor delegate up to
the normal fault handling, the databinding gets a crack at trying to
write the fault.
In 2.0.2, if the exception didn't have an @WebFault,
Should we reduce the logging noisiness of this process?
-Original Message-
From: Daniel Kulp [mailto:[EMAIL PROTECTED]
Sent: Friday, October 19, 2007 1:01 PM
To: cxf-user@incubator.apache.org
Cc: Benson Margulies
Subject: Re: JAXB + JAX-WS + faults
Benson
@incubator.apache.org
Cc: Benson Margulies
Subject: Re: JAXB + JAX-WS + faults
Well, the issue is that the system is working as designed, however,
it
may not be working as the user THINKS it is designed.
For example, if I create an exception like:
public class FooException extends Exception
Since moving to the latest 2.0.3 snapshot, I'm getting an exception when
marshalling a fault declared on a 'throws' clause. No @WebFault. This
didn't happen with 2.0.2 afaik.
WARNING: Exception occurred while writing fault.
org.apache.cxf.interceptor.Fault: Marshalling Error:
