I am out of the office until 2013/10/08.
I can check mail occasionally. Anything urgent call my cell phone
+(86)13681200955. Thanks!
Note: This is an automated response to your message "Re: CXF support for
HATEOAS" sent on 10/02/2013 0:19:45.
This is the only notification you will receive wh
Hi, any idea why this may be failing?
Thanks,
SearchCondition searchCondition =
searchContext.getCondition(Study.class);
SearchConditionVisitor> visitor
= new JPATypedQueryVisitor(entityManager, Study.class);
58 searchCondition.accept(visitor); // this
Hi,
Thanks for the info.I think I can use this, have seen the info on CXF +
using these classes to include the urls.I think I can use these to add the
resource's links in the response.
And that is what I needed.
On Mon, Sep 30, 2013 at 4:05 AM, Sergey Beryozkin wrote:
> Hi
>
> On 27/09/13 22:09,
Hi Mandy
In this case, an exception is thrown from a custom CXF out interceptor
(not part of the out JAX-RS chain) and as we discussed earlier, the
mapping of such exceptions is not supported in earlier CXF versions, but
only starting from CXF 2.7.8 (see the link I posted in another message).
I've actually merged it to CXF 2.7.x, but made the in fault mapping
optional so as not to affect the existing in fault interceptors if any:
https://cwiki.apache.org/confluence/display/CXF20DOC/JAX-RS+Basics#JAX-RSBasics-MappingexceptionsthrownfromCXFinterceptors
Cheers, Sergey
On 28/09/13 21:28
Hi Dan,
Thanks for your response.
To help answer point (1) below, I regenerated the Java artifacts from the WSDL
again. This involved using the same WSDL as previously but this time, the
targetNamespace was set correctly in the service endpoint interface and I was
able to invoke the web service
