Thank you very much, I'll try it.
On 21/05/15 18:03, Sergey Beryozkin wrote:
Hi
Might be some confusion on my part.
The debugging is easy:
- download DOSGI 1.6 source
- before starting Karaf do something like this:
export JAVA_OPTS="-Xdebug -Xnoagent -Djava.compiler=NONE
-Xrunjdwp:transport=
Hi
The demo build produces a war - so just copy that to Tomcat and it
should work
HTH, Sergey
On 21/05/15 15:47, Nicolas Paris wrote:
Hi !
After successful testing some samples (spring_security), my goal is to
moove it from jetty to tomcat 1.7.
According to the documentation, I can deploy the
That's awesome - the MDC based logging will help a lot on making the logs
indexable with elasticsearch/logstash w/o having to grok a lot.
2015-05-14 20:22 GMT+02:00 Daniel Kulp :
>
> > On May 14, 2015, at 3:11 AM, David Karlsen
> wrote:
> >
> > Thank you very much for the answer!
> > And is ther
Hi
Might be some confusion on my part.
The debugging is easy:
- download DOSGI 1.6 source
- before starting Karaf do something like this:
export JAVA_OPTS="-Xdebug -Xnoagent -Djava.compiler=NONE
-Xrunjdwp:transport=dt_socket,server=y,suspend=y,address=5005"
- start Karaf - it will be suspend
Colm, Thanks!
From: coheigea [via CXF] [mailto:ml-node+s547215n5757458...@n5.nabble.com]
Sent: Tuesday, May 19, 2015 12:43 PM
To: boca2608
Subject: Re: CXF 3.0.4 server cannot receive message from TLS1.0 client
I've added a new way of including protocols for the next release:
https://is
Hi !
After successful testing some samples (spring_security), my goal is to
moove it from jetty to tomcat 1.7.
According to the documentation, I can deploy the services with spring
(since I think I will use spring secu in my project)
What are the steps to modify the sample spring_security to be d
I was able to get it working by following option 2 - I rewrote the
initialization code to use the CXF classes directly. Thanks for the advice!
-Original Message-
From: Daniel Kulp [mailto:dk...@apache.org]
Sent: Tuesday, May 19, 2015 4:15 PM
To: users@cxf.apache.org; Roll, Kevin
Subject
On 21/05/15 13:42, Sergey Beryozkin wrote:
On 21/05/15 09:11, Borja Miñano wrote:
No, I didn't.
I have tried now, but the same occurs, it seems that this property is
ignored. I tried now with:
props.put("service.exported.interfaces", "*");
props.put("service.exported.configs",
On 21/05/15 09:11, Borja Miñano wrote:
No, I didn't.
I have tried now, but the same occurs, it seems that this property is
ignored. I tried now with:
props.put("service.exported.interfaces", "*");
props.put("service.exported.configs", "org.apache.cxf.ws");
props.put("or
Hello,
started working a new project (new to me, the project exists for a
while) and I've a contract last (not my choice, only have to live with
it) CXF WebService here running on a Tomcat with Spring. In this
WebService's Interface there is a method like this...
@WebResult(name = "return", partN
No, I didn't.
I have tried now, but the same occurs, it seems that this property is
ignored. I tried now with:
props.put("service.exported.interfaces", "*");
props.put("service.exported.configs", "org.apache.cxf.ws");
props.put("org.apache.cxf.ws.httpservice.context", "/S
11 matches
Mail list logo
