[arquillian-issues] [JBoss JIRA] (ARQ-540) Support @ArquillianResource URL for in-container test cases

[Aslak Knutsen (JIRA)]

     [ https://issues.jboss.org/browse/ARQ-540?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Aslak Knutsen resolved ARQ-540.
-------------------------------
    Fix Version/s: 1.1.9.Final
                       (was: 2.0.0.Beta1)
         Assignee: Aslak Knutsen
       Resolution: Done


pushed upstream https://github.com/arquillian/arquillian-core/commit/a6aae69ba50e233813416647ed501eda6ad6701f

> Support @ArquillianResource URL for in-container test cases
> -----------------------------------------------------------
>
>                 Key: ARQ-540
>                 URL: https://issues.jboss.org/browse/ARQ-540
>             Project: Arquillian
>          Issue Type: Enhancement
>    Affects Versions: 1.0.0.CR2
>            Reporter: Ian Brandt
>            Assignee: Aslak Knutsen
>             Fix For: 1.1.9.Final
>
>
> From [IRC|http://echelog.matzon.dk/logs/browse/jbosstesting/1312408800]:
> {quote}
> [2:13pm] ianbrandt: aslak, Should @ArquillianResource injection work for in-container test cases?  It works fine when I try it for an as-client test, but when I do the same in-container the org.jboss.arquillian.container.test.impl.enricher.resource.URLResourceProvider.protocolMetadata.get() is null, so no context URL.  I verified the container is returning a non-null ProtocolMetaData from deploy(...).
> [2:15pm] aslak: ianbrandt, no it currently doesn't work
> [2:16pm] aslak: ianbrandt, it probably should, but i'm not sure we have the info incontianer without doing a callback to the client..
> [2:16pm] aslak: ianbrandt, but then we don't know which deployment we are when incontianer, so we have a little problem there..
> [2:17pm] ianbrandt: aslak, Ah, okay.
> [2:17pm] aslak: no wait we do
> [2:18pm] aslak: the Protocol is executed within a DeploymentScope/ContainerScope, so when it gets the callback, it has the correct context..
> [2:18pm] aslak: we tho need OperatesOnDeployment support for that tho, cuz you possible want to inject URLs not to your self, but to another deployment on possible another contianer that you should invoke from incontainer
> [2:19pm] aslak: so from incontianer on dep 1, we can do @ArqRes @OperatesOnDep("dep2") URL url;
> [2:23pm] ianbrandt: aslak, Makes sense.  It's a little more than I could take on at the moment.  I was just augmenting the Tomcat tests to show @ArqRes usage.  I'll skip it for shouldBeAbleToInvokeServletInDeployedWebApp, and JIRA+Wiki the limitation.
> {quote}



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)