Programmatically looking up the value of @ArquillianResources


In the rest extension, we have a small problem in that the URL is directly provided by looking up the HTTPContext to determine the value. This works, but if for some reason the URL generated is intended to be different (e.g. we’re running in docker, or on a remote server) this doesn’t work. I figure one way to fix this is to look up what the container would return as the URL, and have REST delegate to that.

The look up of the resource happens at

I don’t want to duplicate this logic, but if it makes sense to I will.

Would it make sense to have core provide a service for arbitrary ArquillianResource lookup?


I think I answered this in twitter right?