[arquillian-issues] [JBoss JIRA] (ARQ-453) Support Apache HTTPD as a DeployableContainer in Managed mode

[Stefan Miklosovic (JIRA)]

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

Stefan Miklosovic edited comment on ARQ-453 at 6/29/14 7:09 PM:
----------------------------------------------------------------

[~ozizka]

I am willing to code this adapter since with the existence of Arquillian Spacelift project it should be easy, however I do not know how to deal with these problems:

1) In case of managed container, this container has to exist prior to test execution so Apache server has to be installed somewhere in file system. When you take out-of-box installation of http server (e.g. in Fedora) you  have to have root permissions to copy some files to /var/www. However, when you run a test, you do not have these write permissions. You would have to somehow manually tweak them before and it is just error prone approach.

Starting and stopping of HTTPD server needs root as well.

2) In case you would take HTTP server with you in container adapter itself, you would have to compile it in advance with some prefix (1) but you do not know in advance how this prefix should look like. And you would have to potentially take into consideration various architectures when compiling (x86_64, i686 ... you name it)

(1) https://httpd.apache.org/docs/2.4/install.html#configure


was (Author: smikloso):
[~ozizka]

I am willing to code this adapter since with the existence of Arquillian Spacelift project it should be easy, however I do not know how to deal with these problems:

1) In case of managed container, this container has to exist prior to test execution so Apache server has to be installed somewhere in file system. When you take out-of-box installation of http server (e.g. in Fedora) you  have to have root permissions to copy some files to /var/www. However, when you run a test, you do not have these write permissions. You would have to somehow manually tweak them before and it is just error prone approach.

2) In case you would take HTTP server with you in container adapter itself, you would have to compile it in advance with some prefix (1) but you do not know in advance how this prefix should look like. And you would have to potentially take into consideration various architectures when compiling (x86_64, i686 ... you name it)

(1) https://httpd.apache.org/docs/2.4/install.html#configure

> Support Apache HTTPD as a DeployableContainer in Managed mode
> -------------------------------------------------------------
>
>                 Key: ARQ-453
>                 URL: https://issues.jboss.org/browse/ARQ-453
>             Project: Arquillian
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>          Components: Apache HTTPD Containers
>            Reporter: Ondrej Zizka
>             Fix For: httpd_1.0.0.next
>
>
> The DeployableContainer interface provided by Arquillian offer a simple abstraction over something that you can setup, start or stop. In addition it can support deploy and undeploy. 
> The same logic can be applied to pure services, e.g. Mail, Database or FTP servers.
> The Apache HTTPD server adapter is a DeployableContainer implementation that control the lifecycle of a local Apache HTTP Server. The Adapter support adding additional HTTPD configuration during setup, and rely on calling out to the command line when starting and stopping the server. The Adapter work with both Windows and Linux based systems.



--
This message was sent by Atlassian JIRA
(v6.2.6#6264)