Vassilis,
Thank you for the input, I resolved this already thanks to Sergey - you
simply have to cleanup really all JaxRS annotations from the
implementing class/methods/parameters etc., then it is working as desired!
I accidentally left the @QueryParam at the last parameter and that
caused th
I can't really help because I have a spring configuration xml for SOAP
services not REST.
In case you can draw any parallels or just rule out this path of
debugging here how it looks like:
serviceClass="com.biovista.lib.ws.iface.BEAService"
service
Hi
On 18/08/16 16:02, J. Fiala wrote:
Sergey,
Sorry I found the cause - one of the parameters were still annotated.
So if the method/parameters are all clean, it works as expected (it's
also possible to have a mix - any clean or fully annotated method at the
implementing class works as expected)
Sergey,
Sorry I found the cause - one of the parameters were still annotated.
So if the method/parameters are all clean, it works as expected (it's
also possible to have a mix - any clean or fully annotated method at the
implementing class works as expected).
So if there is any annotation on
So let me double check, are you saying of you have
@Path("/helloWorld")
public interface HelloWorldResource {
@GET
@Produces("application/json")
@Path("/find")
String sayHello(@QueryParam("name") String name);
}
public class HelloWorldServiceImpl implements HelloWorldResource {
Hi,
I defined the implementing class in the spring configuration (as spring
always require to define the implementing class - changing to the
interface will result in
"org.springframework.beans.BeanInstantiationException - Specified class
is an interface"):
and then defined in the jaxrs:s
Hi,
jumping in and trying a lucky shot...
Is your packaging information correct? Maybe you have specified the impl
class and not the interface on the config file...
Vassilis
On 08/18/2016 05:01 PM, J. Fiala wrote:
That's exactly what I would like to do - if I remove the annotations
fro
That's exactly what I would like to do - if I remove the annotations
from the implementing class methods, they vanish from the WADL.
Best regards,
Johannes
Am 18.08.2016 um 15:54 schrieb Sergey Beryozkin:
It's invalid per the JAX-RS spec - see its annotation inheritance
section, you can not h
It's invalid per the JAX-RS spec - see its annotation inheritance
section, you can not have JAX-RS annotations spread over the interface
and impl, just keep them all on the interface
Cheers, Sergey
On 18/08/16 14:18, J. Fiala wrote:
Sure:
Interface (generated using wadl2java):
@Path("/helloW
Sure:
Interface (generated using wadl2java):
@Path("/helloWorld")
public interface HelloWorldResource {
@GET
@Produces("application/json")
@Path("/find")
String sayHello(@QueryParam("name") String name);
}
// @Path is read from the interface correctly
public class HelloWorldSe
Can you prototype here an interface and an impl class please
thanks, Sergey
On 18/08/16 12:11, J. Fiala wrote:
Hi,
No, that has nothing to do with Swagger, I'm only working with the
generated WADL here.
The @Path-annotation on the implementing class can be removed, here
picking up from the int
Hi,
No, that has nothing to do with Swagger, I'm only working with the
generated WADL here.
The @Path-annotation on the implementing class can be removed, here
picking up from the interface works correctly.
However, if I remove @GET/@Path/@Consumes/@Produces from the method in
the implemen
Hmm is it somehow related to that Swagger related issue ? The interface
annotation inheritance works just fine in CXF as far as I know, as far
as enabling JAX-RS endpoints is concerned
Note we've seen users reporting Swagger2feature can not handle it but a
user has just confirmed that it worke
Currently annotations in the interface are not parsed by CXF (e.g.
@Path, @GET, @Produces, @Consumes etc.), it will only read from the
implementing API class.
This is especially annoying if wadl2java is used to generate the API
interfaces automatically.
To make it work, one has to manually add
14 matches
Mail list logo
