[arquillian-issues] [JBoss JIRA] (ARQ-322) Implement a GlassFish 3.1 managed container adapter

[Dan Allen (JIRA)]

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

Dan Allen updated ARQ-322:
--------------------------

              Summary: Implement a GlassFish 3.1 managed container adapter  (was: Implement a GlassFish 3 managed container)
    Affects Version/s: glassfish_1.0.0.CR2
                           (was: 1.0.0.Alpha4)
             Priority: Major  (was: Minor)
          Description: To round out the GlassFish support, we need a managed container adapter (see the JBoss AS managed container).  (was: To round out the GlassFish support, we need a managed container (see the JBoss AS managed container).)


I've implemented a working prototype of the container adapter. It's functional and validated by tests. There is still work remaining to make it release ready.

* review code and clean it up (feel free to refactor anything)
* ear deployment does not return context path in ProtocolMetaData (see ear test)
* add support for JVM flags (use property javaJvmArguments)
* add support for custom debug port (use property debugPort)
* add support for deploying glassfish-resources.xml (requires custom cleanup, may need to file separate issue)

It's also worrisome how much code is copy-paste from the 3.1 remote container. Consider creating a common module that is shared between them.
                
> Implement a GlassFish 3.1 managed container adapter
> ---------------------------------------------------
>
>                 Key: ARQ-322
>                 URL: https://issues.jboss.org/browse/ARQ-322
>             Project: Arquillian
>          Issue Type: Feature Request
>          Components: GlassFish Containers
>    Affects Versions: glassfish_1.0.0.CR2
>            Reporter: Dan Allen
>
> To round out the GlassFish support, we need a managed container adapter (see the JBoss AS managed container).

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira