On 30/10/15 17:06, Sergey Beryozkin wrote:
Hi
Right now you can control it like this, it is captured in
http://cxf.apache.org/docs/jax-rs-search.html#JAX-RSSearch-Capturingthequeries,
and the follow up sections, but I guess it would help to have a table...
- register ExceptionMapper and let the
Hi
Right now you can control it like this, it is captured in
http://cxf.apache.org/docs/jax-rs-search.html#JAX-RSSearch-Capturingthequeries,
and the follow up sections, but I guess it would help to have a table...
- register ExceptionMapper and let the client
know about it in a more readable
I'm using the JPATypedQuery visitor to fetch data from the database based on
the FIQL query.
My Entity called 'DocumentRequest' has a property 'suppliercode' with getter
and setters.
I capture the Searchcondition from the SearchContext like this:
SearchCondition condition =
searchContext.getCondi
Hmm, looks like a Feature can be directly registered with the server
too. Apparently TCKs do not enforce that...
It can actually be registered on the server with CXF indirectly, from
DynamicFeature - so what you can do right now is to register a
DynamicFeature impl that will simply set a Kathars
Hi
You can register it as a JAX-RS provider, in
jaxrs:server/jaxrs:providers, though I'm presuming
you should implement
https://jax-rs-spec.java.net/nonav/2.0-rev-a/apidocs/javax/ws/rs/container/DynamicFeature.html
To be honest I'm actually not sure if 'Feature', as opposed to
'DynamicFeatur
All,
I currently have an Apache CXF application into which I am trying to integrate
this library http://katharsis.io/ for the purposes of serializing objects into
json-api compliant payloads.
The documentation here http://katharsis.io/#jax-rs states that it can be
integrated with jax-rs env
Yes Sergey will let you know.
Thanks
On Thu, Oct 29, 2015 at 5:20 PM, Sergey Beryozkin [via CXF] <
ml-node+s547215n5762379...@n5.nabble.com> wrote:
> I've updated the existing Failover test to POST a body:
>
> http://git-wip-us.apache.org/repos/asf/cxf/commit/0c7f3e16
>
> works fine in the maste
Hi,
I have a same problem.
Could you let me know how to use the class WSProxy in this example ?
Thanks,
--
View this message in context:
http://cxf.547215.n5.nabble.com/CXF-Service-Routing-to-Remote-Server-tp5713087p5762419.html
Sent from the cxf-user mailing list archive at Nabble.com.
I checked the code there.
if
(msg.getContextualProperty(org.apache.cxf.message.Message.REQUEST_URL)
!= null) {
audiences.add((String)msg.getContextualProperty(org.apache.cxf.message.Message.REQUEST_URL));
}
So this adds the request URI as audience. Unfortunately there
The list of restrictions is set in
WSS4JInInterceptor.configureAudienceRestriction(SoapMessage msg, RequestData
reqData)
Thank you!
--
View this message in context:
http://cxf.547215.n5.nabble.com/Using-JMS-URI-as-a-SAML-audience-restriction-tp5762392p5762408.html
Sent from the cxf-user mai
I think the historical reason is that the endpoint URI for jms used to
be "jms://" for all endpoints. So it did not mean anything.
Today this is different. So it makes sense to provide the URI.
Unfortunately I have no idea where in the code this is done. If you can
point me to the place where t
Hi
See
http://git-wip-us.apache.org/repos/asf/cxf/commit/8dc621b1
Cheers, Sergey
On 27/10/15 08:01, Andrew Holland wrote:
Hi,
When using the org.apache.cxf.transport.servlet.CXFNonSpringServlet inside
an embedded jetty server the servlet is doing multiple JNDI lookups per
request via the
org.
Hi,
I'm using CXF 3.1.3 with JMS transport and SAML. For all incoming messages
SAML audience restriction check fails on provider side.
In my case SAML assertion contains only one audience restriction string, the
JMS URI of the endpoint, like this one:
jms:jndi:dynamicQueues/example.queue?jndiI
13 matches
Mail list logo
