-
1. Re: JAX-RS 2.0 client works properly but returns HTTP 404 when executing with Arquillian
simplex-software May 15, 2017 10:14 AM (in response to simplex-software)I'm replying to my own post. It seems that, as a matter of fact, Arquillian for Websphere is not able to use the information in the IBM extension files and, hence, the deployed WAR url uses the maven ${project.artifactId} as context-root.
So, I added to following to my Arquillian test:
@ArquillianResource
private URL baseURL;
Now, I'm using baseURL to compose the JAX-RS endpoint but I'm experiencing another exception:
org.jboss.arquillian.test.spi.ArquillianProxyException: javax.ws.rs.client.ResponseProcessingException : Problem with reading the data, class be.alphacredit.services.esign.model.QuickSignRootResource, ContentType: application/json. [Proxied because : Original exception caused: class java.io.NotSerializableException: org.apache.cxf.jaxrs.impl.ResponseImpl]
The exactly same code works properly when ran in a plain JUnit test, once that the WAR has been deployed using the WAS maven plugin.
Any idea of what could be wrong here ? By the way, I'm using here org.jboss.arquillian.container:arquillian-was-remote-8.5:1.0.0.Final-SNAPSHOT. This to be used with WebSphere 8.5.5? Is there any WebSphere 9.0 Arquillian plugin ?
Kind regards,
Nicolas