[arquillian-issues] [JBoss JIRA] (ARQ-725) Refactor the WebLogicContainer implementation to a stateful implementation, to improve performance
Vineet Reynolds (JIRA)
jira-events at lists.jboss.org
Mon Jan 16 02:59:18 EST 2012
[ https://issues.jboss.org/browse/ARQ-725?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Vineet Reynolds updated ARQ-725:
--------------------------------
Description: Currently, the {{WebLogicContainer}} class does not store any state across archive deployments and undeployments. New instances of the {{WebLogicJMXClient}} class are created on every deployment and undeployment of archives. Internally, a new classloader is also created for every deployment and undeployment. This tends to increase the time elapsed for a deployment, before it is made available for execution of Arquillian tests. A refactoring is therefore proposed wherein the {{WebLogicContainer}} class would create only one reference to the {{WebLogicJMXClient}} class, and reuse it throughout the lifecycle of the container. (was: Currently, the {{WebLogiContainer}} class does not store any state across archive deployments and undeployments. New instances of the {{WebLogicJMXClient}} class are created on every deployment and undeployment of archives. Internally, a new classloader is also created for every deployment and undeployment. This tends to increase the time elapsed for a deployment, before it is made available for execution of Arquillian tests. A refactoring is therefore proposed wherein the {{WebLogicContainer}} class would create only one reference to the {{WebLogicJMXClient}} class, and reuse it throughout the lifecycle of the container.)
> Refactor the WebLogicContainer implementation to a stateful implementation, to improve performance
> --------------------------------------------------------------------------------------------------
>
> Key: ARQ-725
> URL: https://issues.jboss.org/browse/ARQ-725
> Project: Arquillian
> Issue Type: Enhancement
> Security Level: Public(Everyone can see)
> Components: WebLogic Containers
> Reporter: Vineet Reynolds
> Assignee: Vineet Reynolds
>
> Currently, the {{WebLogicContainer}} class does not store any state across archive deployments and undeployments. New instances of the {{WebLogicJMXClient}} class are created on every deployment and undeployment of archives. Internally, a new classloader is also created for every deployment and undeployment. This tends to increase the time elapsed for a deployment, before it is made available for execution of Arquillian tests. A refactoring is therefore proposed wherein the {{WebLogicContainer}} class would create only one reference to the {{WebLogicJMXClient}} class, and reuse it throughout the lifecycle of the 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
More information about the arquillian-issues
mailing list