[arquillian-issues] [JBoss JIRA] (ARQ-138) Implement a remote Weblogic Server container

[Vineet Reynolds (Issue Comment Edited) (JIRA)]

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

Vineet Reynolds edited comment on ARQ-138 at 10/21/11 8:48 PM:
---------------------------------------------------------------

An initial _pre-alpha-quality_ version of the remote WLS integration is available in the [ARQ-138 branch of my GitHub repo|https://github.com/VineetReynolds/arquillian-container-weblogic/tree/ARQ-138]. The eventual release will be pushed upstream.

There are a few points to be noted with respect to the current version:
* CDI Injection might simply not be possible under WLS 10.3.5 (or 10.3.x). A deployment of the ShrinkWrap exported archive with Weld Servlet results in the Servlet complaining of an unsupported environment. This might need to be tracked as a separate issue (possibly in the WELD project).
* I settled for using {{Weblogic.Deployer}} to deploy the ShrinkWrap exported archive. Although this needs to be launched as a separate application, it appears to be most reasonable way to programatically deploy artifacts to WLS from Java. The other options included:
** usage of WLST, with Arquillian-specific Jython scripts.
** usage of WLS supplied classes, that are not licensed under ASL2, and hence not present in any public Maven repo.
* JMX is also used to obtain information about the runtime servers and deployments. There is a twist here - using the JDK/JRE classes alone requires usage of the IIOP protocol to connect to the MBean server. This appeared to be problematic in my setup, and I opted to have users of this integration provide the location of the WebLogic Server installation; the {{wljmxclient.jar}} and it's dependencies from the WLS installation are then loaded by a {{URLClassLoader}}. A local WLS installation was anyway required for deploying artifacts (considering all of the cases for programmatic deployment), so we don't seem to be burdening users by requiring a WLS installation for deployment against local and remote WLS servers.

                
      was (Author: vineet.reynolds):
    An initial _pre-alpha-quality_ version of the remote WLS integration is available in the [ARQ-138 branch of my GitHub repo|https://github.com/VineetReynolds/arquillian-container-weblogic/tree/ARQ-138]. The eventual release will be pushed upstream.

There are a few points to be noted with respect to the current version:
* CDI Injection might simply not be possible under WLS 10.3.5 (or 10.3.x). A deployment of the ShrinkWrap exported archive with Weld Servlet results in the Servlet complaining of an unsupported environment. This might need to be tracked as a separate issue (possibly in the WELD project).
* I settled for using {{Weblogic.Deployer}} to deploy the ShrinkWrap exported archive. Although this needs to be launched as a separate application, it appears to be most reasonable way to programatically deploy artifacts to WLS from Java. The other options included:
 * usage of WLST, with Arquillian-specific Jython scripts.
 * usage of WLS supplied classes, that are not licensed under ASL2, and hence not present in any public Maven repo.
* JMX is also used to obtain information about the runtime servers and deployments. There is a twist here - using the JDK/JRE classes alone requires usage of the IIOP protocol to connect to the MBean server. This appeared to be problematic in my setup, and I opted to have users of this integration provide the location of the WebLogic Server installation; the {{wljmxclient.jar}} and it's dependencies from the WLS installation are then loaded by a {{URLClassLoader}}. A local WLS installation was anyway required for deploying artifacts (considering all of the cases for programmatic deployment), so we don't seem to be burdening users by requiring a WLS installation for deployment against local and remote WLS servers.

                  
> Implement a remote Weblogic Server container
> --------------------------------------------
>
>                 Key: ARQ-138
>                 URL: https://issues.jboss.org/browse/ARQ-138
>             Project: Arquillian
>          Issue Type: Feature Request
>          Components: WebLogic Containers
>    Affects Versions: 1.0.0.Alpha1
>            Reporter: Dan Allen
>            Assignee: Vineet Reynolds
>            Priority: Optional
>              Labels: weblogic
>             Fix For: 1.1.0.CR1
>
>
> We have interest from the community in contributing container support for a remote Weblogic Server. This issue will track the progress of the contribution.
> Note: The proper abbreviation for Weblogic Server is wls

--
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