Hello Colm,
Thanks for replying.
I want both for creation and verification and also both for the method (using
WS-SecurityPolicy or not).
Best Regards.
-Original Message-
From: Colm O hEigeartaigh [mailto:cohei...@apache.org]
Sent: lundi 8 juin 2015 15:32
To: users@cxf.apache.org
Subjec
I am making a Web Service call using CXF 2.7.8 where the response consists
of a 302 response-code with header information but no SOAP payload. When
the ReadHeadersInterceptor attempts to parse the response, the following
exception is thrown:
Caused by: javax.xml.stream.XMLStreamException: ParseErr
Hi,
I am working on a project which is developed using Play Framework. The
project needs to interact with a number of third party SOAP services. It is
very important for the system to be scalable by design and should allow
high number of concurrent requests. I understand that this can be achieved
Hi,
More easy way to start your ServerLifeCycleListener is using
META-INF/cxf/bus-extensions.txt.
Here is example:
https://github.com/apache/cxf/blob/master/rt/ws/security/src/main/resources/META-INF/cxf/bus-extensions.txt
https://github.com/apache/cxf/blob/master/rt/ws/security/src/main/java/or
Sounds interesting.
Do you mean this one?
https://github.com/logstash/log4j-jsonevent-layout
Christian
Am 09.06.2015 um 16:34 schrieb Oliver Wulff:
Hi there
I'm working to use logstash-forwarder to feed log data to a central logstash
server which processes the messages and sends it to Elasti
It looks like WebLogic or another Interceptor is blocking the execution of
my interceptor. If I send weblogics username and password then it will pass
and run my interceptor.
Regards,
Néstor
On Tue, Jun 9, 2015 at 5:59 AM, Colm O hEigeartaigh
wrote:
> I tested the following and it does result
Hi there
I'm working to use logstash-forwarder to feed log data to a central logstash
server which processes the messages and sends it to ElasticSearch.
I recommend to use the JSON layout in log4j to avoid additional parsing on
logstash side (no grok filter required).
HTH
Oli
_
On 09/06/2015 15:17, Sergey Beryozkin wrote:
Hi Francesco
See https://issues.apache.org/jira/browse/CXF-6447,
So you'd be able to optimize the signature if still preferred, the
server code would stay completely portable, though only CXF proxies
would likely to work with such signatures in the
Hi Francesco
See https://issues.apache.org/jira/browse/CXF-6447,
So you'd be able to optimize the signature if still preferred, the
server code would stay completely portable, though only CXF proxies
would likely to work with such signatures in the short term at least
Thanks, Sergey
On 08/06/
Hi
I've just fixed for 3.0.6-SNAPSHOT:
https://issues.apache.org/jira/browse/CXF-6446
Have a look please if it does work for you
Cheers, Sergey
On 08/06/15 11:20, Sergey Beryozkin wrote:
Hi
Thanks for reporting this issue, I'll take care of it in time for the
next release.
FYI, it is also p
Should be fixed now.
Btw. you can easily test the fix by compiling the changed logging
feature bundle from source and use it instead of the original one. It
should be otherwise compatible with CXF 3.x.
Christian
On 09.06.2015 10:04, David Karlsen wrote:
Yes it's great - however I stumbled ov
Hi
Please ask such questions on the users list,
FYI, on the client side you can experiment with JAX-RS 2.0 Client API or
configure CXF HttpConduit directly, see HttpConduit info:
http://cxf.apache.org/docs/client-http-transport-including-ssl-support.html
on the server you can get TlsSessionInfo f
What do you want to clarify exactly and what is not working?
2015-05-28 16:04 GMT+02:00 Pablo Caballero :
> Hi cxf folks!
>
> We have some applications using cxf (2.2.10) as client to consume
> (different) web services.
> Once in a while we have a method invocation that take more time than time
>
I tested the following and it does result in a Basic Auth header being
created:
((BindingProvider)port).getRequestContext().put(BindingProvider.USERNAME_PROPERTY,
"alice");
((BindingProvider)port).getRequestContext().put(BindingProvider.PASSWORD_PROPERTY,
"clarinet");
It sounds like the problem i
Sorry, I can't help you. The issues appear to be specific to websphere +
the SAAJ/XML dependencies that are used.
Colm.
On Tue, Jun 9, 2015 at 9:07 AM, Christian Thiel wrote:
> Hi Colm,
>
> thanks for your response and fixing the NPE in Santuario.
>
> I was finally successful to run the service
Hi,
take a look at cxf's transform feature here
http://cxf.apache.org/docs/transformationfeature.html#TransformationFeature-Replacingtextcontent
you need there
this will map the original invalid fault from the server into the
following valid fault so that it can be accepted by the cxf client
SOA
Hi
Sure, in this case create a JAX-RS Application implementation and
register it as a 'javax.ws.rs.Application' parameter. This custom
Application can configure RequestDispatcherProvider in the code
HTH, Sergey
On 09/06/15 06:03, Voss, Marko wrote:
Hi Sergey,
thank you very much for your
Sure.
The new LoggingFeature can be added to services like the old one. So
using this you already have the new meta data in slf4j log events.
There currently is no ready to use elastic search integration outside of
OSGi. It could be achieved either by creating a Log4j appender or a
LogSender
Yes it's great - however I stumbled over a snag when using it with a camel
transport: https://issues.apache.org/jira/browse/CXF-6436
2015-06-08 17:46 GMT+02:00 Christian Schneider :
> Since version 3.1.0 there is a new request logging feature in CXF. I just
> wrote a blog entry about it and thou
On 08/06/2015 17:46, Christian Schneider wrote:
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
Hi Christian,
the new logging feature looks
20 matches
Mail list logo
