Fair point, but when we switch to the new trunk and introduce the new
API which bring the standard analogs it is becoming problematic to
support multiple code artifacts meaning the same thing, it creates a
certain 'noise' which may not be really appreciated :-)
Sergey
On 20/11/13 20:25, Jason Wang wrote:
Thanks Sergey, replaced my old reference to the new ones now they work. It
would be nice if those old ones got marked as @deprecated and left
untouched for backward compatibility.
CHeers
On Wed, Nov 20, 2013 at 11:00 PM, Sergey Beryozkin <[email protected]>wrote:
Hi Jason
On 20/11/13 04:37, Jason Wang wrote:
Hi all,
I just asked the same question in a different mail thread. But it was
off-topic. So I am bringing it up as a new question.
I found my code no longer compiles with CXF 2.7.0~. It worked happily with
2.6.*.
The compiling error were: can not resolve
org.apache.cxf.jaxrs.client.ClientWebApplicationException
or
org.apache.cxf.jaxrs.client.ServerWebApplicationException
So, just wondering if anyone here knows why they are gone from 2.7.0??
They existed in the cxf-rt-frontend-jaxrs-2.6.9.jar file.
Yes they were removed in CXF 2.7.0, I believe it is documented.
In CXF 2.7.x the code needs to catch WebApplicationException or any of its
new subclasses, see the exceptions section at
https://jax-rs-spec.java.net/nonav/2.0/apidocs/index.html
The client side exceptions can be caught with ClientException (which is in
2.0 m10 which CXF 2.7.x depends upon) and ProcessingException &
ResponseProcessingException in CXF 3.0 (2.0 final API)
Sergey
Many thanks,
Jason
--
Sergey Beryozkin
Talend Community Coders
http://coders.talend.com/
Blog: http://sberyozkin.blogspot.com
