January 2015 - arquillian-issues - Jboss List Archives

[JBoss JIRA] (ARQ-1760) Replace the WebLogic.Deployer deployment mechanism with JMX for WLS 12.1.2 and higher

by Aslak Knutsen (JIRA)

[ https://issues.jboss.org/browse/ARQ-1760?page=com.atlassian.jira.plugin.s... ] Aslak Knutsen closed ARQ-1760. ------------------------------ > Replace the WebLogic.Deployer deployment mechanism with JMX for WLS 12.1.2 and higher > ------------------------------------------------------------------------------------- > > Key: ARQ-1760 > URL: https://issues.jboss.org/browse/ARQ-1760 > Project: Arquillian > Issue Type: Feature Request > Components: WebLogic Containers > Affects Versions: wls_1.0.0.Alpha2 > Reporter: Vineet Reynolds > Assignee: Vineet Reynolds > Fix For: wls_1.0.0.Alpha3 > > > Replace the error prone WebLogic.Deployer based deployment mechanism with the JMX based deployer for WLS 12.1.2 (and higher version of WLS). The older deployment mechanism would however need to be in use for older versions of WLS since they do not have support for JMX based deployment of applications. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ARQ-1172) Implement an embedded WebLogic Server container

by Aslak Knutsen (JIRA)

[ https://issues.jboss.org/browse/ARQ-1172?page=com.atlassian.jira.plugin.s... ] Aslak Knutsen closed ARQ-1172. ------------------------------ > Implement an embedded WebLogic Server container > ----------------------------------------------- > > Key: ARQ-1172 > URL: https://issues.jboss.org/browse/ARQ-1172 > Project: Arquillian > Issue Type: Feature Request > Components: WebLogic Containers > Reporter: Vineet Reynolds > Assignee: Vineet Reynolds > Priority: Minor > Fix For: wls_1.0.0.Alpha3 > > > WebLogic Server 12c supports EJB 3.1 and is hence expected to support testing of EJBs in an embedded container, at a minimum. > This feature request is to investigate implementation of the embedded Arquillian container for WLS 12c in particular. Support for an embedded mode of operation for WLS 10.3.x is to be investigated, and may be implemented if supported by Oracle (as documentated APIs or similar). -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ARQ-1173) Remove the javaHome configuration property for the WLS containers

by Aslak Knutsen (JIRA)

[ https://issues.jboss.org/browse/ARQ-1173?page=com.atlassian.jira.plugin.s... ] Aslak Knutsen closed ARQ-1173. ------------------------------ > Remove the javaHome configuration property for the WLS containers > ----------------------------------------------------------------- > > Key: ARQ-1173 > URL: https://issues.jboss.org/browse/ARQ-1173 > Project: Arquillian > Issue Type: Enhancement > Components: WebLogic Containers > Reporter: Vineet Reynolds > Assignee: Vineet Reynolds > Priority: Minor > Fix For: wls_1.0.0.Alpha3 > > > The javaHome property in the {{CommonWebLogicConfiguration}} class is and never was utilized by the container. Remove the property to avoid confusing users of it's purpose. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ARQ-784) The wlsHome property of the WebLogic containers should default to a pre-defined environment variable

by Aslak Knutsen (JIRA)

[ https://issues.jboss.org/browse/ARQ-784?page=com.atlassian.jira.plugin.sy... ] Aslak Knutsen closed ARQ-784. ----------------------------- > The wlsHome property of the WebLogic containers should default to a pre-defined environment variable > ---------------------------------------------------------------------------------------------------- > > Key: ARQ-784 > URL: https://issues.jboss.org/browse/ARQ-784 > Project: Arquillian > Issue Type: Enhancement > Components: WebLogic Containers > Affects Versions: wls_1.0.0.Alpha1, wls_1.0.0.Alpha2 > Reporter: Vineet Reynolds > Assignee: Vineet Reynolds > Fix For: wls_1.0.0.Alpha3 > > > The `wlsHome` property does not have a default value at present, and users are expected to specify this in arquillian.xml; a system property could be used in arquillian.xml, but this would require Surefire or the test-execution environment to pass an existing environment variable as a system property. > It would useful to default this to the `WL_HOME` environment variable to preserve the intent of the property. However, we could consider using the `WLS_HOME` environment variable (this points to the `WL_HOME/server` directory) since all usages refer to resources in the server sub-directory. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ARQ-1122) ServletRuntime lookup only returns servlets of first web application found

by Aslak Knutsen (JIRA)

[ https://issues.jboss.org/browse/ARQ-1122?page=com.atlassian.jira.plugin.s... ] Aslak Knutsen updated ARQ-1122: ------------------------------- Fix Version/s: wls_1.0.0.Alpha3 (was: wls_1.0.0.next) > ServletRuntime lookup only returns servlets of first web application found > -------------------------------------------------------------------------- > > Key: ARQ-1122 > URL: https://issues.jboss.org/browse/ARQ-1122 > Project: Arquillian > Issue Type: Enhancement > Components: WebLogic Containers > Affects Versions: 1.0.2.Final > Environment: Weblogic 12c > Reporter: Ralph Abbink > Assignee: Vineet Reynolds > Priority: Minor > Fix For: wls_1.0.0.Alpha3 > > > After enriching our regular maven built .ear i noticed the following exception: {noformat}ArquillianServletRunner not found. Could not determine ContextRoot from ProtocolMetadata, please contact DeployableContainer developer.{noformat} > It appears the lookup for servletRuntimes only returns the servlets of the first web application in the deployment. In our .ear we have several web modules and the first one found wasn't the module i enriched using Arquillian. > {code:title=WebLogicJMXClient.java} > private ObjectName[] findServletRuntimes(ObjectName wlServerRuntime, String deploymentName) throws Exception > { > ObjectName[] applicationRuntimes = (ObjectName[]) connection.getAttribute(wlServerRuntime, "ApplicationRuntimes"); > for(ObjectName applicationRuntime: applicationRuntimes) > { > String applicationName = (String) connection.getAttribute(applicationRuntime, "Name"); > if(applicationName.equals(deploymentName)) > { > ObjectName[] componentRuntimes = (ObjectName[]) connection.getAttribute(applicationRuntime, "ComponentRuntimes"); > for(ObjectName componentRuntime : componentRuntimes) > { > String componentType = (String) connection.getAttribute(componentRuntime, "Type"); > if (componentType.toString().equals("WebAppComponentRuntime")) > { > ObjectName[] servletRuntimes = (ObjectName[]) connection.getAttribute(componentRuntime, "Servlets"); > return servletRuntimes; > } > } > } > } > throw new DeploymentException( > "The deployment details were not found in the MBean Server. Possible causes include:\n" > + "1. The deployment failed. Review the admin server and the target's log files.\n" > + "2. The deployment succeeded partially. The deployment must be the Active state. Instead, it might be in the 'New' state.\n" > + " Verify that the the admin server can connect to the target(s), and that no firewall rules are blocking the traffic on the admin channel."); > } > {code} > {code:title="Returning all servlets found" WebLogicJMXClient.java} > private List<ObjectName> findServletRuntimes(ObjectName wlServerRuntime, String deploymentName) throws Exception > { > ObjectName[] applicationRuntimes = (ObjectName[]) connection.getAttribute(wlServerRuntime, "ApplicationRuntimes"); > for(ObjectName applicationRuntime: applicationRuntimes) > { > String applicationName = (String) connection.getAttribute(applicationRuntime, "Name"); > if(applicationName.equals(deploymentName)) > { > List<ObjectName> servletRuntimes = new ArrayList<ObjectName>(); > ObjectName[] componentRuntimes = (ObjectName[]) connection.getAttribute(applicationRuntime, "ComponentRuntimes"); > for(ObjectName componentRuntime : componentRuntimes) > { > String componentType = (String) connection.getAttribute(componentRuntime, "Type"); > if (componentType.toString().equals("WebAppComponentRuntime")) > { > servletRuntimes.addAll(Arrays.asList((ObjectName[]) connection.getAttribute(componentRuntime, "Servlets"))); > } > } > return servletRuntimes; > } > } > throw new DeploymentException( > "The deployment details were not found in the MBean Server. Possible causes include:\n" > + "1. The deployment failed. Review the admin server and the target's log files.\n" > + "2. The deployment succeeded partially. The deployment must be the Active state. Instead, it might be in the 'New' state.\n" > + " Verify that the the admin server can connect to the target(s), and that no firewall rules are blocking the traffic on the admin channel."); > } > } > {code} -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ARQ-1172) Implement an embedded WebLogic Server container

by Aslak Knutsen (JIRA)

[ https://issues.jboss.org/browse/ARQ-1172?page=com.atlassian.jira.plugin.s... ] Aslak Knutsen updated ARQ-1172: ------------------------------- Fix Version/s: wls_1.0.0.Alpha3 (was: wls_1.0.0.next) > Implement an embedded WebLogic Server container > ----------------------------------------------- > > Key: ARQ-1172 > URL: https://issues.jboss.org/browse/ARQ-1172 > Project: Arquillian > Issue Type: Feature Request > Components: WebLogic Containers > Reporter: Vineet Reynolds > Assignee: Vineet Reynolds > Priority: Minor > Fix For: wls_1.0.0.Alpha3 > > > WebLogic Server 12c supports EJB 3.1 and is hence expected to support testing of EJBs in an embedded container, at a minimum. > This feature request is to investigate implementation of the embedded Arquillian container for WLS 12c in particular. Support for an embedded mode of operation for WLS 10.3.x is to be investigated, and may be implemented if supported by Oracle (as documentated APIs or similar). -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ARQ-1133) Upgrade to Arquillian core 1.0.2.Final for WebLogic Containers

by Aslak Knutsen (JIRA)

[ https://issues.jboss.org/browse/ARQ-1133?page=com.atlassian.jira.plugin.s... ] Aslak Knutsen updated ARQ-1133: ------------------------------- Fix Version/s: wls_1.0.0.Alpha3 (was: wls_1.0.0.next) > Upgrade to Arquillian core 1.0.2.Final for WebLogic Containers > --------------------------------------------------------------- > > Key: ARQ-1133 > URL: https://issues.jboss.org/browse/ARQ-1133 > Project: Arquillian > Issue Type: Component Upgrade > Components: WebLogic Containers > Affects Versions: wls_1.0.0.Alpha2 > Reporter: Vineet Reynolds > Assignee: Vineet Reynolds > Fix For: wls_1.0.0.Alpha3 > > > Update the WebLogic containers to Arquillian Core 1.0.2.Final. > This is more to ensure that the tests for the container adapter can use the {{Testable}} API to define the archive to test. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ARQ-785) Implement a managed WebLogic Server container

by Aslak Knutsen (JIRA)

[ https://issues.jboss.org/browse/ARQ-785?page=com.atlassian.jira.plugin.sy... ] Aslak Knutsen updated ARQ-785: ------------------------------ Fix Version/s: wls_1.0.0.Alpha3 (was: wls_1.0.0.next) > Implement a managed WebLogic Server container > --------------------------------------------- > > Key: ARQ-785 > URL: https://issues.jboss.org/browse/ARQ-785 > Project: Arquillian > Issue Type: Feature Request > Components: WebLogic Containers > Reporter: Vineet Reynolds > Assignee: Vineet Reynolds > Priority: Minor > Fix For: wls_1.0.0.Alpha3 > > > Currently, we have support for remote WebLogic Server containers. We ought to explore the possibility of bringing in support for managed WebLogic Server containers, via the use of startWebLogic/startManagedWebLogic and stopWebLogic/stopManagedWebLogic scripts. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ARQ-1173) Remove the javaHome configuration property for the WLS containers

by Aslak Knutsen (JIRA)

[ https://issues.jboss.org/browse/ARQ-1173?page=com.atlassian.jira.plugin.s... ] Aslak Knutsen updated ARQ-1173: ------------------------------- Fix Version/s: wls_1.0.0.Alpha3 (was: wls_1.0.0.next) > Remove the javaHome configuration property for the WLS containers > ----------------------------------------------------------------- > > Key: ARQ-1173 > URL: https://issues.jboss.org/browse/ARQ-1173 > Project: Arquillian > Issue Type: Enhancement > Components: WebLogic Containers > Reporter: Vineet Reynolds > Assignee: Vineet Reynolds > Priority: Minor > Fix For: wls_1.0.0.Alpha3 > > > The javaHome property in the {{CommonWebLogicConfiguration}} class is and never was utilized by the container. Remove the property to avoid confusing users of it's purpose. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ARQ-1184) Use wljmxclient.jar instead of weblogic.jar in the searchpath of the WebLogic JMX client

by Aslak Knutsen (JIRA)

[ https://issues.jboss.org/browse/ARQ-1184?page=com.atlassian.jira.plugin.s... ] Aslak Knutsen updated ARQ-1184: ------------------------------- Fix Version/s: wls_1.0.0.Alpha3 (was: wls_1.0.0.next) > Use wljmxclient.jar instead of weblogic.jar in the searchpath of the WebLogic JMX client > ---------------------------------------------------------------------------------------- > > Key: ARQ-1184 > URL: https://issues.jboss.org/browse/ARQ-1184 > Project: Arquillian > Issue Type: Enhancement > Components: WebLogic Containers > Reporter: Vineet Reynolds > Assignee: Vineet Reynolds > Fix For: wls_1.0.0.Alpha3 > > > The {{WebLogicJMXLibClassLoader}} currently loads classes from weblogic.jar instead of using the documented. This was done during resolution of ARQ-725 to avoid initialization of a Java SecurityManager, but this is a bad idea in retrospect considering that the use of weblogic.jar may be unsupported and that internal details of WebLogic Server may change in the future. > Therefore, the default search path for the {{WebLogicJMXLibClassLoader}} would be changed from weblogic.jar to wljmxclient.jar. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 2 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

arquillian-issues January 2015