Could you test it with one of the latest releases (CXF 3.2.6 / 3.1.16) in
case it's a bug that has been subsequently fixed?
Colm.
On Fri, Sep 14, 2018 at 3:06 PM Bertrand TROLARD
wrote:
> Hi,
>
> I got a problem with a REST service when I use CXF 3.x, it's working
> fine with CXF 2.7.
> "No
Hi Colm,
I got an error when I try to install the rutime with Eclipse
--
Java Virtual Machine Launcher
Could not find the main class:
org.apache.cxf.tools.wsdlto.WSDLToJava. Program will exit.
--
It's under Windows 10.
I'll see if I can find an
Hi,
I got a problem with a REST service when I use CXF 3.x, it's working
fine with CXF 2.7.
"No message body writer has been found for class java.lang.Integer"
Response-Code: 500
Content-Type: text/plain
Headers: {Content-Type=[plain/text], Date=[Fri, 14 Sep 2018 13:41:18 GMT]}
Payload: No
Hi,
For the problem with the runtime, Eclipse was configured to use JVM 1.6
by default, it's Ok now with JVM 1.8.
The same function on the web-service but the return valeu is a String
instead of an int and it works.
@POST
@Path("/state0/")
public *String
Ah, then I am fine. I thought that it *should* work but I am doing something
wrong.
So, I simply get the username from Spring Security that "wraps" the whole
service call orchestration.
Thanks a lot
Stephan
-Ursprüngliche Nachricht-
Von: Colm O hEigeartaigh
Gesendet: Donnerstag,
Hi Jens,
OK well it should be straightforward to do both of those things with a CXF
interceptor. If there were some public/official documentation we could
consider adding it to CXF.
Colm.
On Thu, Sep 13, 2018 at 3:24 PM Jens wrote:
> Hi Colm,
>
> at the moment I only have (confidential)
Hi James,
Looks as inconsistency on the first view.
Could you invest a bit more efforts and check how Jersey behaves in this case?
Regards,
Andrei.
> -Original Message-
> From: James Carman [mailto:ja...@carmanconsulting.com]
> Sent: Donnerstag, 13. September 2018 00:51
> To:
So, I wrote a simple filter to test this out on Jersey and it also does NOT
split the headers:
@Provider
public class DumpHeadersFilter implements ContainerRequestFilter {
@Context
private HttpHeaders httpHeaders;
@Override
public void filter(ContainerRequestContext requestContext)
Hi Colm,
yes, that's what I did now.
I'm actually not sure whether the way to use this stuff with SOAP is some
sort of standard or just a one-off project with a home-grown authentication
scheme.
In case I do get something official and public I'll let you know.
Cheers,
Jens
coheigea wrote
>
