Dan Allen created ARQ-1205: ------------------------------ Summary: Expose a resolver in the SPI to lookup the deploymentUrl easily from an extension Key: ARQ-1205 URL: https://issues.jboss.org/browse/ARQ-1205 Project: Arquillian Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Base Implementation Affects Versions: 1.0.3.Final Reporter: Dan Allen Priority: Minor Story: *In order* to initialize clients to conveniently access URLs in the deployed application *As an* extension writer *I want* to be able to use an SPI to calculate the deployment URL (consistent with the [URLResourceProvider|http://docs.jboss.org/arquillian/aggregate/1.0.3.Fina...]) Scenarios: *Given* that I need to access the deployment URL from an extension *When* I invoke a public SPI method that resolves the deployment URL : *And* the test case only has one deployment *Then* the SPI method should return the URL to that deployment *Given* that I need to access the deployment URL from an extension *When* I invoke a public SPI method that resolves the deployment URL : *And* the test case has multiple deployments : *And* I specify a string-based deployment name as an argument *Then* the SPI method should return the URL to that deployment Rationale: Extensions may need access to the deploymentUrl for setting up resources, such as a client. However, there is quite a bit of logic necessary to resolve the deploymentUrl properly, especially when multiple deployments are in use. Therefore, I propose adding an SPI that exposes the logic in the URLResourceProvider. Here's a rough sketch of the SPI: {code} public interface DeploymentURLResolver { public URL resolveURL(); public URL resolveURL(String deploymentName); } {code} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira