September 2012 - arquillian-issues

[JBoss JIRA] (ARQ-817) arquillian-weld-container does not build on Maven Default Profile

by Andrew Rubinger (JIRA)

Andrew Rubinger created ARQ-817: ----------------------------------- Summary: arquillian-weld-container does not build on Maven Default Profile Key: ARQ-817 URL: https://issues.jboss.org/browse/ARQ-817 Project: Arquillian Issue Type: Bug Security Level: Public (Everyone can see) Reporter: Andrew Rubinger Assignee: Andrew Rubinger The current configuration assumes that the JBoss Nexus repo is enabled: {code}[ERROR] Failed to execute goal on project arquillian-weld-se-embedded-1.1: Could not resolve dependencies for project org.jboss.arquillian.container:arquillian-weld-se-embedded-1.1:jar:1.0.0.Final-SNAPSHOT: Could not find artifact org.jboss.weld:weld-core:jar:1.1.1.Final in central (http://repo.maven.apache.org/maven2) -> [Help 1]{code} Probably we could go for an upgrade of Weld here anyway, which has been proxied to Maven Central. -- 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

11 years, 8 months

2
6
0 / 0

[JBoss JIRA] (ARQ-819) Wrong criteria used for supplying Weld with WebArchiveClassLoader

by Andrew Rubinger (JIRA)

Andrew Rubinger created ARQ-819: ----------------------------------- Summary: Wrong criteria used for supplying Weld with WebArchiveClassLoader Key: ARQ-819 URL: https://issues.jboss.org/browse/ARQ-819 Project: Arquillian Issue Type: Bug Security Level: Public (Everyone can see) Reporter: Andrew Rubinger Assignee: Andrew Rubinger Currently the decision to use WebArchiveClassLoader instead of ShrinkWrapClassLoader is based on type-checking the archive for instanceof WebArchive. Because a user may switch to another archive view before returning the archive, it's better to run by the spec-approved definition of a WAR file as denoted by the ".war" suffix. -- 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

11 years, 8 months

2
7
0 / 0

[JBoss JIRA] (ARQ-890) WeldEEMockContainer does not clean up resources if the deployment failsw

by Jozef Hartinger (JIRA)

Jozef Hartinger created ARQ-890: ----------------------------------- Summary: WeldEEMockContainer does not clean up resources if the deployment failsw Key: ARQ-890 URL: https://issues.jboss.org/browse/ARQ-890 Project: Arquillian Issue Type: Bug Security Level: Public (Everyone can see) Components: Weld Containers Affects Versions: weld_1.0.0.CR3 Reporter: Jozef Hartinger If container.startContainer() at WeldEEMockContainer:98 throws an exception, WeldEEMockContainer.undeploy is never called. This leads to memory and thread leaks during test runs. -- 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

11 years, 8 months

2
5
0 / 0

[JBoss JIRA] (ARQ-1124) Prepare Arquillian iOS Alpha1 release

by Karel Piwko (JIRA)

Karel Piwko created ARQ-1124: -------------------------------- Summary: Prepare Arquillian iOS Alpha1 release Key: ARQ-1124 URL: https://issues.jboss.org/browse/ARQ-1124 Project: Arquillian Issue Type: Task Security Level: Public (Everyone can see) Components: Extension - iOS Affects Versions: ios_1.0.0.next Reporter: Karel Piwko Assignee: Jan Papousek Prepare first release of integration layer for iOS emulators/devices. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 8 months

2
3
0 / 0

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

by Ralph Abbink (JIRA)

Ralph Abbink created ARQ-1122: --------------------------------- Summary: 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 Security Level: Public (Everyone can see) Components: WebLogic Containers Affects Versions: 1.0.2.Final Environment: Weblogic 12c Reporter: Ralph Abbink Assignee: Vineet Reynolds 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 is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 8 months

2
5
0 / 0

[JBoss JIRA] Created: (ARQ-468) Automatically add test super classes for OSGi

by Thomas Diesler (JIRA)

Automatically add test super classes for OSGi --------------------------------------------- Key: ARQ-468 URL: https://issues.jboss.org/browse/ARQ-468 Project: Arquillian Issue Type: Enhancement Security Level: Public (Everyone can see) Components: OSGi Containers Reporter: Thomas Diesler Assignee: Thomas Diesler Super classes should be added automatically and work as the injection target for the OSGi enricher -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 8 months

1
3
0 / 0

[JBoss JIRA] (ARQGRA-190) Support initializing Page Objects declared with generic types

by Juraj Húska (JIRA)

Juraj Húska created ARQGRA-190: ---------------------------------- Summary: Support initializing Page Objects declared with generic types Key: ARQGRA-190 URL: https://issues.jboss.org/browse/ARQGRA-190 Project: Arquillian Graphene Issue Type: Feature Request Components: core Affects Versions: 2.0.0.Alpha2 Reporter: Juraj Húska Assignee: Juraj Húska When using @Page annotation to initialize Page Object in this way: {code} public abstract class AbstractWebDriverTest<P extends AbstractPage> extends Arquillian { @Page public P page; } {code} I am getting this: {code} java.lang.RuntimeException: Can not initialise Page Object! at org.jboss.arquillian.graphene.enricher.ComponentObjectsEnricher.initializePageObjectFields(ComponentObjectsEnricher.java:106) at org.jboss.arquillian.graphene.enricher.ComponentObjectsEnricher.enrich(ComponentObjectsEnricher.java:64) at org.jboss.arquillian.test.impl.TestInstanceEnricher.enrich(TestInstanceEnricher.java:52) at org.jboss.arquillian.container.test.impl.ClientTestInstanceEnricher.enrich(ClientTestInstanceEnricher.java:51) at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) at org.jboss.arquillian.core.impl.EventContextImpl.invokeObservers(EventContextImpl.java:99) at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:81) at org.jboss.arquillian.container.test.impl.client.ContainerEventController.createContext(ContainerEventController.java:142) at org.jboss.arquillian.container.test.impl.client.ContainerEventController.createBeforeContext(ContainerEventController.java:124) at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88) at org.jboss.arquillian.test.impl.TestContextHandler.createTestContext(TestContextHandler.java:89) at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88) at org.jboss.arquillian.test.impl.TestContextHandler.createClassContext(TestContextHandler.java:75) at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88) at org.jboss.arquillian.test.impl.TestContextHandler.createSuiteContext(TestContextHandler.java:60) at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88) at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:135) at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:115) at org.jboss.arquillian.test.impl.EventTestRunnerAdaptor.before(EventTestRunnerAdaptor.java:95) at org.jboss.arquillian.testng.Arquillian.arquillianBeforeTest(Arquillian.java:130) at org.apache.maven.surefire.testng.TestNGExecutor.run(TestNGExecutor.java:178) at org.apache.maven.surefire.testng.TestNGXmlTestSuite.execute(TestNGXmlTestSuite.java:92) at org.apache.maven.surefire.testng.TestNGProvider.invoke(TestNGProvider.java:96) at org.apache.maven.surefire.util.ReflectionUtils.invokeMethodWithArray(ReflectionUtils.java:189) at org.apache.maven.surefire.booter.ProviderFactory$ProviderProxy.invoke(ProviderFactory.java:165) at org.apache.maven.surefire.booter.ProviderFactory.invokeProvider(ProviderFactory.java:85) at org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:113) at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:75) {code} It is caused with this line in PageFragmentEnricher: {code} Class declaredClass = Class.forName(i.getGenericType().toString().split(" ")[1]); {code} I need support for Page Objects declared with generic type. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 8 months

3
10
0 / 0

[JBoss JIRA] (ARQ-996) Provide an Arquillian Bundle suitable for Fedora

by Thomas Diesler (JIRA)

Thomas Diesler created ARQ-996: ---------------------------------- Summary: Provide an Arquillian Bundle suitable for Fedora Key: ARQ-996 URL: https://issues.jboss.org/browse/ARQ-996 Project: Arquillian Issue Type: Task Security Level: Public (Everyone can see) Components: OSGi Containers Reporter: Thomas Diesler Assignee: Thomas Diesler akurtakov: the thing that is totally unacceptable is using prebuild jars during fedora builds -- 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

11 years, 8 months

3
9
0 / 0

[JBoss JIRA] (ARQ-997) Provide Arquillian Core functionality as OSGi Bundle

by Thomas Diesler (JIRA)

Thomas Diesler created ARQ-997: ---------------------------------- Summary: Provide Arquillian Core functionality as OSGi Bundle Key: ARQ-997 URL: https://issues.jboss.org/browse/ARQ-997 Project: Arquillian Issue Type: Sub-task Security Level: Public (Everyone can see) Components: Base Implementation, OSGi Containers Reporter: Thomas Diesler Assignee: Thomas Diesler (10:06:40 AM) tdiesler: mgoldmann, lets talk about the individual sub task. Embedded ARQ Core functionality for example. Instead of embedding the jars arq-osgi could include the *.class files. I suppose that is equally unacceptable, right? (10:07:22 AM) akurtakov: tdiesler: if they are not built from source yes (10:07:27 AM) mgoldmann: yes, classes are unpcettable too, you can embed what you just build (arq-osgi jars) (10:08:19 AM) tdiesler: mgoldmann, but arq core was build by some other process - noi? (10:08:53 AM) mgoldmann: yes, so we cannot embed it (10:09:13 AM) mgoldmann: but we can bundle arq-core in a jar at the time of building arq-core (10:09:15 AM) tdiesler: mgoldmann, that process could make an aggregated bundle that arq-osgi could use (i.e. import packages from) -- 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

11 years, 8 months

2
2
0 / 0

[JBoss JIRA] (ARQ-998) Provide an OSGi bundles for javax.inject

by Thomas Diesler (JIRA)

Thomas Diesler created ARQ-998: ---------------------------------- Summary: Provide an OSGi bundles for javax.inject Key: ARQ-998 URL: https://issues.jboss.org/browse/ARQ-998 Project: Arquillian Issue Type: Sub-task Security Level: Public (Everyone can see) Components: OSGi Containers Reporter: Thomas Diesler Assignee: Thomas Diesler -- 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

11 years, 8 months

1
2
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

arquillian-issues September 2012