[ https://jira.jboss.org/browse/ARQ-138?page=com.atlassian.jira.plugin.syst... ] Aslak Knutsen reassigned ARQ-138: --------------------------------- Assignee: Alejandro Montenegro -- 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

[ https://jira.jboss.org/browse/ARQ-138?page=com.atlassian.jira.plugin.syst... ] Aslak Knutsen updated ARQ-138: ------------------------------ Fix Version/s: 1.0.0.Beta1 (was: 1.0.0.Alpha4) -- 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

[ https://issues.jboss.org/browse/ARQ-138?page=com.atlassian.jira.plugin.sy... ] Aslak Knutsen updated ARQ-138: ------------------------------ Fix Version/s: 1.1.0.CR1 (was: 1.0.0.Beta1) -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/ARQ-138?page=com.atlassian.jira.plugin.sy... ] Aslak Knutsen reassigned ARQ-138: --------------------------------- Assignee: Vineet Reynolds (was: Alejandro Montenegro) -- 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

[ https://issues.jboss.org/browse/ARQ-138?page=com.atlassian.jira.plugin.sy... ] 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...]. 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...]. 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. -- 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

[ https://issues.jboss.org/browse/ARQ-138?page=com.atlassian.jira.plugin.sy... ] Work on ARQ-138 stopped by Vineet Reynolds. -- 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

[ https://issues.jboss.org/browse/ARQ-138?page=com.atlassian.jira.plugin.sy... ] George Gastaldi commented on ARQ-138: ------------------------------------- I tested the pull request and it´s working fine on WLS 10.3.5. Go for it ! :) -- 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

[ https://issues.jboss.org/browse/ARQ-138?page=com.atlassian.jira.plugin.sy... ] Aslak Knutsen updated ARQ-138: ------------------------------ Status: Resolved (was: Pull Request Sent) Resolution: Done pushed upstream -- 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

[ https://issues.jboss.org/browse/ARQ-138?page=com.atlassian.jira.plugin.sy... ] Vineet Reynolds commented on ARQ-138: ------------------------------------- The GitHub pull request URL is invalid after the project was renamed. [This GitHub URL|https://github.com/arquillian/arquillian-container-wls/pull/1] ought to be used instead, in case anyone needs it for future reference. -- 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