JBoss EAP中的Rest Client的NoClassDefFoundError

Question

I produce EAR sample App with REST client and deploy it on my notebook (JBoss EAP 6.3.0 with standalone configuration and binded any-address for public domain). Following code is responsibility for producing REST response:

@Stateless
@Path("/users/list")
public class ListUsersREST {

    @GET
    @Produces("text/html")
    public String getUsersList() {
        return "TEST";
    }

}

It's work fine through POSTMAM. Probably this part of my example doesn't need any help.

And now... I work on my second app deployed on my desktop (JBoss and configuration the same). I have dependecies for JAVAEE7 API with contain JAVAX.WS.RS.* API. I'm trying to connect to this REST client and get response (like through POSTMAN):

@Stateless
@Local(EJBTest.class)
public class EJBTestBean implements EJBTest {

    @Override
    public void getRestResponse() {
        Client client = ClientBuilder.newClient();
        WebTarget target = client.target("http://192.168.0.2:8080/demo/rest/users/list");
        Response response = target.request(MediaType.TEXT_HTML).get();

        String value = response.readEntity(String.class);
        int status = response.getStatus();
        response.close();
        client.close();
        System.out.println("REST RESPONSE: " + value);
        System.out.println("REST Status: " + status);
    }

}

...and this piece of code doesn't work. I don't know why...

I'm getting the same Exception all the time...

Caused by: java.lang.NoClassDefFoundError: javax/ws/rs/client/ClientBuilder

I was searching on google and trying many solution like

1. adding dependecies all reasteasy jar to aplication (WEB-INF/lib)
2. adding reasteasy jars to ${JBOSS_HOME}/standalone/lib
3. changing standalone.xml
4. running jboss with standalone-full.xml configuration

but with no effects... Please tell me what is going on. What am I doing wrong?

Answer 1

JBoss EAP 6 is Java EE 6 and you're deploying an app that requires Java EE 7. The JAX-RS client is only in Java EE 7. This should work if you tried your deployments on WildFly .

The reason you're dependencies don't seem to work is the server will us it's own JAX-RS dependencies over your own. You could potentially exclude the JAX-RS subsystem from your deployment which may work. You probably wouldn't be able to use JAX-RS endpoints though, only the client.

Your best bet though is to use Java EE 7 container, which WildFly 8 is.