[arquillian-issues] [JBoss JIRA] Commented: (ARQ-171) ServletMethodExecutor should get context path from container

[Aslak Knutsen (JIRA)]

    [ https://jira.jboss.org/browse/ARQ-171?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12534308#action_12534308 ] 

Aslak Knutsen commented on ARQ-171:
-----------------------------------

This falls under the sharing of metadata between the container and arquillian, and separating the protocols from the container.

https://jira.jboss.org/browse/ARQ-153
https://jira.jboss.org/browse/ARQ-125

> ServletMethodExecutor should get context path from container
> ------------------------------------------------------------
>
>                 Key: ARQ-171
>                 URL: https://jira.jboss.org/browse/ARQ-171
>             Project: Arquillian
>          Issue Type: Bug
>          Components: Test Protocol SPIs and Implementation
>    Affects Versions: 1.0.0.Alpha2
>            Reporter: Dan Allen
>
> While working on the JSR 88 container implementation, I noticed that ServletMethodExecutor is using the hard-coded context path "/test" to communicate with the application to invoke the ArquillianServletRunner. I think that the context path is something that the container implementation should be passing to the ServletMethodExecutor in the deploy() method.
> This assumption poses a particular problem in the JSR 88 container. When a WAR is deployed using JSR 88, the module is assigned a random name, and hence a random context path. Since there is no way to override the context path "/test" used by the ServletMethodExecutor, it fails to communicate with the server.
> The ServletMethodExecutor constructor should be changed to take the context path as the second parameter. All the container implementations will need to be updated accordingly.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira