Hi Sergey,
thank you very much for your input. Ok I want to try the
RequestDispatcherProvider, but how do I setup this one with the following
structure to call the setResourcePaths?
RestfulApp
org.apache.cxf.jaxrs.servlet.CXFNonSpringJaxrsServlet
jaxrs
Hi
I created a web service with an interceptor for Basic Authentication:
public class BasicAuthorizationInterceptor extends SoapHeaderInterceptor {
protected static final Logger logger =
LoggerFactory.getLogger(BasicAuthorizationInterceptor.class);
private WhitePagesBf whitePagesBf;
Since version 3.1.0 there is a new request logging feature in CXF. I
just wrote a blog entry about it and thought this might be interesting
for people on this list.
http://www.liquid-reality.de/x/AoDT
Christian
--
Christian Schneider
http://www.liquid-reality.de
Open Source Architect
http://
Hi Colm.
I can't get access to server side. I only develop the client.
Thanks and best regards.
El 08/06/15 a las 15:28, Colm O hEigeartaigh escribió:
What is the stacktrace of the exception on the service side? Is it in
code that you wrote or in CXF/WSS4J?
Colm.
On Mon, Jun 8, 2015 at 2:
Hi Aki.
The problem is that i don't get access to server side.
Can i avoid this error with namespace?
Thanks and best regards.
El 08/06/15 a las 15:26, Aki Yoshida escribió:
The error message says your server is returning an invalid SOAP fault
(the wsse prefix is not bound).
It should be retur
Sounds good, thanks for the confirmation,
Sergey
On 08/06/15 13:10, axelr wrote:
Hi Sergey,
I am sorry, my fault! Because I am not sure whether I got your point, I had
a more detailed look in the stack trace:
The exception is thrown by a different bean 'customerBean' not the
jaxrs-client:client
The short answer is yes. Do you want to change the creation of the
Timestamp or the verification? Using WS-SecurityPolicy or not?
Colm.
On Fri, Jun 5, 2015 at 7:24 PM, COURTAULT Francois <
francois.courta...@gemalto.com> wrote:
> Hello everyone,
>
> Is it possible using cxf api, to control the a
How do I access the WebApplicationContext?
I did this in my code:
@Resource
private WebServiceContext wsContext;
The code gets executed when I deploy the WAR, but wsContext is null.
On Sun, Jun 7, 2015 at 6:31 PM, André Costa Lima
wrote:
> Hi,
>
> You can set publish=false in jaws:endpoint.
What is the stacktrace of the exception on the service side? Is it in code
that you wrote or in CXF/WSS4J?
Colm.
On Mon, Jun 8, 2015 at 2:26 PM, Aki Yoshida wrote:
> The error message says your server is returning an invalid SOAP fault
> (the wsse prefix is not bound).
> It should be returning
The error message says your server is returning an invalid SOAP fault
(the wsse prefix is not bound).
It should be returning something like ...wsse:InvalidSecurityToken
and your CXF client is complaining about it.
2015-06-08 12:51 GMT+02:00 "Ángel L. García Sánchez" :
> Hi.
>
> I'm developin
Hi Sergey,
I am sorry, my fault! Because I am not sure whether I got your point, I had
a more detailed look in the stack trace:
The exception is thrown by a different bean 'customerBean' not the
jaxrs-client:client bean (customerService). I was confused by the similar
name.
So everything works as
Hi.
I'm developing a web service client with Apache CXF 3.1.0 (also test
with 2.7.16). When the soap message validation fails on server I get a
soap fault like this:
Payload:
xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/";>wsse:InvalidSecurityTokenSe
ha proporcionado un token de
Hi
Thanks for reporting this issue, I'll take care of it in time for the
next release.
FYI, it is also possible to prepare a WADL document at the build time
and there one can depend on the actual on the more robust JavaDoc API to
get the doc collected:
http://cxf.apache.org/docs/jaxrs-serv
Hi
It does work with Spring itself managing the actual injection, based on
the stack trace, you write the code yourself by directly requesting a
jaxrs:client bean.
Try to do create a bean like CustomerServiceProxy with a property
'customerService' set in Spring to refer to jaxrs:client, and
Sorry, that will not work with the proxies as they won't be able to
resolve the {key} :-), with webclients only...
I wonder if we can explore your idea on the client side and try to
resolve a variable if the body bean is available...I'll try to
experiment a bit later on
Thanks, Sergey
On 0
Hi Francesco,
By the way, it is fine to have something like this:
@PUT
@Path("{key}")
public void update(ResourceTo bean) {}
That can actually be the optimal signature, if the bean contains the key
then it can be taken from the bean and if not - then from UriInfo by
analyzing the path value.
Hi Sergey,
thanks for your response.
On 08/06/2015 11:16, Sergey Beryozkin wrote:
Hi Francesco
Sure, you can try:
@PUT
@Consumes({ MediaType.APPLICATION_XML, MediaType.APPLICATION_JSON })
void update(@NotNull ResourceTO resourceTO);
Omitting the extra @Path completely and getting the key out
Hello,
We're currently using CXF 3.0.4 and it seems there is a bug in generating WADL
when JDK 8 is used: method javadocs are not being added to WADL.
It happens because Javadoc format has been changed in Java 8. Now in Javadoc
HTML files methods look like < a name="getCountries--"> instead of <
Hi Francesco
Sure, you can try:
@PUT
@Consumes({ MediaType.APPLICATION_XML, MediaType.APPLICATION_JSON })
void update(@NotNull ResourceTO resourceTO);
Omitting the extra @Path completely and getting the key out of
ResourceTo bean:
PUT /resources
1
given that the key is available the
19 matches
Mail list logo
