[arquillian-issues] [JBoss JIRA] (ARQGRA-483) @Location might use the Wrong URL when used with Warp

[Aslak Knutsen (JIRA)]

Aslak Knutsen created ARQGRA-483:
------------------------------------

             Summary: @Location might use the Wrong URL when used with Warp 
                 Key: ARQGRA-483
                 URL: https://issues.jboss.org/browse/ARQGRA-483
             Project: Arquillian Graphene
          Issue Type: Bug
          Components: integration
    Affects Versions: 2.1.0.Alpha2
            Reporter: Aslak Knutsen


Both Graphene and Warp attempt to override the default Core URLResourceProvider.

Warp has the ProxyURLProvider and Graphene the CustomizableURLResourceProvider.

When both Graphene and Warp is on classpath it becomes unpredictable who will actually win.

Technically the two URLs used here could be different:

{code}
@ArquillianResource
private URL baseURL;
	
@Test @RunAsClient
public void shouldBeAbleToStoreConference(@InitialPage ConferencePage page) throws Exception {
}
{code}

BaseURL could be proxied and the URL used by InitialPage not, or the other way around.

Graphene sets up it's ContextRootStore with which ever URL was provided last; 
https://github.com/arquillian/arquillian-graphene/blob/master/impl/src/main/java/org/jboss/arquillian/graphene/location/ContextRootStoreInitializer.java#L54

Core will do the opposite, which ever comes first. 

When Graphene resolves the 'non-proxied' URL, Warp will eventually time out waiting for a reply as it never got to setup and sync.



--
This message was sent by Atlassian JIRA
(v6.4.11#64026)