The default CXFRS model is about the Camel CXFRS processor doing a match
and recording the relevant info such as the path, method, etc for the
custom processors to follow and react as needed.
Additionally, it has a performInvocation flag where you can get it
actually invoking on the concrete ser
Hello ,
Thank you very much - but how can I process this requests in the end ?
@POST
@Path("/createRequest1")
@Produces("application/json")
public void request1(VistaraInboundModel inboundModel)
and
@POST
@Path("/createRequest2")
@Produces("application/json")
public void request2(Vista
Hi
I guess it would be more of a Camel specific issue. I believe in the
CXFRS case the method selection is implicit.
Though what is quite relevant to the CXF list is that if you indeed
meant to have request1() and request2() methods have the same JAXRS
annotations then there will be no predi
Hello ,
I have another question if is possible please .
If I had cxf:rsServer register like this
and
And in the com.xxx.service.InboundService I had two methods like this :
@POST
@Path("/createIncident1")
@Produces("application/json")
public void request1(Inbo
Hello ,
I have another question if is possible please .
If I had cxf:rsServer register like this
and
And in the com.xxx.service.InboundService I had two methods like this :
@POST
@Path("/createIncident")
@Produces("application/json")
public void request1(VistaraInbo
Hi,
thx for reply.
With the following Policy definition it works.
http://schemas.xmlsoap.org/ws/2005/07/securitypolicy";
xmlns:wsp="http://schemas.xmlsoap.org/ws/2004/09/policy";
xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd";
wsu:Id="BiPROAuthSecur
The error is caused by the fact that you are manually adding the
WSS4JInInterceptor to the CXF in-interceptor list in
WebServiceConfiguration. You only do this when you don't have a
WS-SecurityPolicy. For the policy case, CXF will set up the interceptors
for you automatically.
Note that when you r
Could you use a separate embedded Jetty instance in your rest service
configuration? Like the tests in CXF do, for example:
https://github.com/apache/cxf/blob/master/systests/rs-security/src/test/resources/org/apache/cxf/systest/jaxrs/security/oidc/oidc-server.xml#L50
Colm.
On Mon, Mar 6, 2017 a
Please help, this problem only occurs against WCF webservices, also please
let me know how to enable debug logging on CXF library to troubleshoot the
issue to find the root cause?
Thanks,
Deepak
On Feb 27, 2017 5:11 PM, "Deepak Kumar" wrote:
> Any help would be greatly appreciated. We are setti
