Hi,
Could you post the onwire message?
Also in your test code
} catch (AddNumbersException_Exception e) {
System.out.println(e.getFaultInfo().getInfo());
}
is the e.getFaultInfo return AddNumbersException instance?
－－－－－－－－－－－－－
Freeman(Yue) Fang
Red Hat, Inc.
FuseSource is now part of Red Hat
Web: http://fusesource.com | http://www.redhat.com/
Twitter: freemanfang
Blog: http://freemanfang.blogspot.com
http://blog.sina.com.cn/u/1473905042
weibo: http://weibo.com/u/1473905042
On 2012-10-17, at 下午1:21, iris ding wrote:
> Hi FreeMan,
>
> Thanks a lot for your comments.
>
> Define the faultbean works. But now the issue is as per jax-ws 2.2 spec, we
> can leave it to let JAX-WS runtime generate for you automatically. ALso, per
> the spec, faultBean="xxx" is optional in @webFault
>
> So it seems there is a bug in CXF for handling below situation:
> the exception class does not have getFaultInfo() defined && there is no
> faultBean="xxx" is optional in @webFault annotation.
>
> Is this a bug for CXF?
>
> Thanks!
>
>
>
> --
> View this message in context:
> http://cxf.547215.n5.nabble.com/Webfault-tp5716784p5716793.html
> Sent from the cxf-user mailing list archive at Nabble.com.
