You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Many tests are done to have the root context of a war file, but this it not valid in some frameworks like Helidon, where there is no such context root.
We can see that explicitly sets the context root with the war name.
It would be really helpful for Helidon developers if TCKs takes the context root in this other way (as it is already done in rest/jaxrs-tck/src/main/java/ee/jakarta/tck/ws/rs/spec/client/exceptions/ClientExceptionsIT.java):
@ArquillianResource
private URL baseUrl;
In this way the web container will provide the context root and we get rid of this issue in Helidon.
The text was updated successfully, but these errors were encountered:
My assumption is this was because that's how the tests were and it was minimal effort to get them migrated to Arquillian based tests. However, using the URL, or URI, injection is the correct way to do it.
Many tests are done to have the root context of a war file, but this it not valid in some frameworks like Helidon, where there is no such context root.
Any JAXRSClientIT contains the next 2 things:
We can see that explicitly sets the context root with the war name.
It would be really helpful for Helidon developers if TCKs takes the context root in this other way (as it is already done in
rest/jaxrs-tck/src/main/java/ee/jakarta/tck/ws/rs/spec/client/exceptions/ClientExceptionsIT.java
):In this way the web container will provide the context root and we get rid of this issue in Helidon.
The text was updated successfully, but these errors were encountered: