February 2011 - arquillian-issues

[JBoss JIRA] Created: (ARQ-353) Remove DeploymentScanner disabling

by Aslak Knutsen (JIRA)

Remove DeploymentScanner disabling ---------------------------------- Key: ARQ-353 URL: https://issues.jboss.org/browse/ARQ-353 Project: Arquillian Issue Type: Feature Request Components: JBoss Containers Reporter: Aslak Knutsen Fix For: 1.0.0.Beta1 The HDScanner / ProfileService redeploy issue has been fixed in JBoss AS 6.0 Final. Remove the old stop/start of HDScanner in the JBoss 6.0 Remote Container. New ProfileServiceClient API could be used to minimize the dep chain: dependency> <groupId>org.jboss.jbossas</groupId> <artifactId>jboss-as-profileservice-client</artifactId> <version>6.0.0-SNAPSHOT</version> <type>pom</type> <scope>test</scope> </dependency> -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 10 months

2
5
0 / 0

[JBoss JIRA] Created: (ARQ-340) mappedName and lookup attributes are ignored for @EJB in jections into test cases, forcing a naming convention on implementations

by Radai Rosenblatt (JIRA)

mappedName and lookup attributes are ignored for @EJB in jections into test cases, forcing a naming convention on implementations --------------------------------------------------------------------------------------------------------------------------------- Key: ARQ-340 URL: https://jira.jboss.org/browse/ARQ-340 Project: Arquillian Issue Type: Bug Components: Runtime Enricher SPI Affects Versions: 1.0.0.Alpha4 Environment: JRE 1.6.0.21 windows xp jboss embedded 6 Reporter: Radai Rosenblatt suppose i have an interface called BeanInterface, which is a local interface implemented a class called BeanImplementation. then, in my test case, i have the following in ijected field: @EJB(mappedName = "java:global/test/BeanImplementation/local") private BeanInterface bean; this will fail because the enricher does not bother looking at the annotation attributes. specifically, as can be seen in EJBInjectionEnricher.java line 102, the code does not pass the Field itself to the lookup method, only its name. the lookup method then proceeds to try several JNDI naming alternatives (line 137). this means that production classes are forced to adhere to the naming conventions used by arquillian code or tests fail. the code in question could take into account the mappedName and/or lookup attributes of @EJB to allow developers to specify the JNDI name for the lookup. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 10 months

4
7
0 / 0

[JBoss JIRA] Created: (ARQ-309) Allow configuration to specify an OpenEJB configuration resources (openejb.xml)

by Dan Allen (JIRA)

Allow configuration to specify an OpenEJB configuration resources (openejb.xml) ------------------------------------------------------------------------------- Key: ARQ-309 URL: https://jira.jboss.org/browse/ARQ-309 Project: Arquillian Issue Type: Feature Request Components: OpenEJB Containers Affects Versions: 1.0.0.Alpha4 Reporter: Dan Allen Priority: Minor Implement the feature described in the OpenEJB FAQ for supplying a custom configuration file. http://openejb.apache.org/faq.html Create an openejb.xml file in any directory* that gets added to your test classpath. Then in your test case do this: protected void setUp() throws Exception { Properties properties = new Properties(); properties.setProperty(Context.INITIAL_CONTEXT_FACTORY, "org.apache.openejb.client.LocalInitialContextFactory"); URL config = this.getClass().getClassLoader().getResource("openejb.xml"); properties.setProperty("openejb.configuration", config.toExternalForm()); initialContext = new InitialContext(properties); } * The name of this file could be an Arquillian container configuration property. -- 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

13 years, 10 months

2
3
0 / 0

[JBoss JIRA] Created: (ARQ-215) Configuration should support loading of Configuration data for extensions/frameworks

by Aslak Knutsen (JIRA)

Configuration should support loading of Configuration data for extensions/frameworks ------------------------------------------------------------------------------------ Key: ARQ-215 URL: https://jira.jboss.org/browse/ARQ-215 Project: Arquillian Issue Type: Feature Request Components: Configuration Reporter: Aslak Knutsen Extensions / frameworks might need access to Configuration options. The Configuration should support dynamic loading of Configuration data for extensions as for Containers. e.g. <?xml version="1.0" encoding="UTF-8"?> <arquillian xmlns="http://jboss.com/arquillian" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:coverage="urn:arq:org.jboss.arquillian.framework.cobertura"> <coverage:extension> <coverage:sourceFolder>src/main/java</coverage:sourceFolder> </coverage:extension> </arquillian> -- 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

13 years, 10 months

2
7
0 / 0

[JBoss JIRA] Created: (ARQ-281) NPE when JBOSS_HOME isn't set

by Pete Muir (JIRA)

NPE when JBOSS_HOME isn't set ----------------------------- Key: ARQ-281 URL: https://jira.jboss.org/browse/ARQ-281 Project: Arquillian Issue Type: Bug Components: JBoss Containers Affects Versions: 1.0.0.Alpha3 Reporter: Pete Muir org.jboss.arquillian.impl.event.FiredEventException: java.lang.NullPointerException at org.jboss.arquillian.impl.event.MapEventManager.fire(MapEventManager.java:68) at org.jboss.arquillian.impl.context.AbstractEventContext.fire(AbstractEventContext.java:115) at org.jboss.arquillian.impl.EventTestRunnerAdaptor.beforeSuite(EventTestRunnerAdaptor.java:62) at org.jboss.arquillian.junit.Arquillian.<init>(Arquillian.java:89) at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39) at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27) at java.lang.reflect.Constructor.newInstance(Constructor.java:513) at org.junit.internal.builders.AnnotatedBuilder.buildRunner(AnnotatedBuilder.java:31) at org.junit.internal.builders.AnnotatedBuilder.runnerForClass(AnnotatedBuilder.java:24) at org.junit.runners.model.RunnerBuilder.safeRunnerForClass(RunnerBuilder.java:57) at org.junit.internal.builders.AllDefaultPossibilitiesBuilder.runnerForClass(AllDefaultPossibilitiesBuilder.java:29) at org.junit.runners.model.RunnerBuilder.safeRunnerForClass(RunnerBuilder.java:57) at org.junit.internal.requests.ClassRequest.getRunner(ClassRequest.java:24) at org.eclipse.jdt.internal.junit4.runner.JUnit4TestReference.<init>(JUnit4TestReference.java:32) at org.eclipse.jdt.internal.junit4.runner.JUnit4TestClassReference.<init>(JUnit4TestClassReference.java:25) at org.eclipse.jdt.internal.junit4.runner.JUnit4TestLoader.createTest(JUnit4TestLoader.java:41) at org.eclipse.jdt.internal.junit4.runner.JUnit4TestLoader.loadTests(JUnit4TestLoader.java:31) at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:452) at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:683) at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.run(RemoteTestRunner.java:390) at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.main(RemoteTestRunner.java:197) Caused by: java.lang.NullPointerException at org.jboss.jbossas.servermanager.ServerManager.getJavaEndorsedDirs(ServerManager.java:260) at org.jboss.jbossas.servermanager.ServerController.getEndorsedDirsProperty(ServerController.java:212) at org.jboss.jbossas.servermanager.ServerController.getStartCommandLine(ServerController.java:191) at org.jboss.jbossas.servermanager.ServerController.startServer(ServerController.java:101) at org.jboss.jbossas.servermanager.ServerManager.startServer(ServerManager.java:163) at org.jboss.arquillian.container.jbossas.managed_6.JBossASLocalContainer.start(JBossASLocalContainer.java:84) at org.jboss.arquillian.impl.handler.ContainerStarter.callback(ContainerStarter.java:52) at org.jboss.arquillian.impl.handler.ContainerStarter.callback(ContainerStarter.java:41) at org.jboss.arquillian.impl.event.MapEventManager.fire(MapEventManager.java:63) ... 21 more -- 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

13 years, 10 months

3
7
0 / 0

[JBoss JIRA] Created: (ARQ-342) Application/Module name of the form "jsr88-851802189695127335 instead of archive name, eg "test"

by Jesse Hutton (JIRA)

Application/Module name of the form "jsr88-851802189695127335 instead of archive name, eg "test" ------------------------------------------------------------------------------------------------ Key: ARQ-342 URL: https://jira.jboss.org/browse/ARQ-342 Project: Arquillian Issue Type: Bug Reporter: Jesse Hutton -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 10 months

2
3
0 / 0

[JBoss JIRA] Created: (ARQ-359) Support testing against remote JBoss AS on different hostname / machine

by Dan Allen (JIRA)

Support testing against remote JBoss AS on different hostname / machine ----------------------------------------------------------------------- Key: ARQ-359 URL: https://issues.jboss.org/browse/ARQ-359 Project: Arquillian Issue Type: Feature Request Components: JBoss Containers Affects Versions: 1.0.0.Alpha4 Reporter: Dan Allen Support testing against remote JBoss AS on different hostname / machine. Even though it's possible to configure the remote JBoss AS adapter to point to another address, tests fail because of a reverse lookup error in the JBoss AS server invoker. Assuming hostname is "envy", the following exception occurs during test deployment: Caused by: java.lang.RuntimeException: java.io.IOException: Can not get connection to server. Problem establishing socket connection for InvokerLocator [socket://envy: 10234/] at org.jboss.profileservice.management.client.upload.StreamingDeploymentTarget.transferDeployment(StreamingDeploymentTarget.java:286) at org.jboss.profileservice.management.client.upload.StreamingDeploymentTarget.distribute(StreamingDeploymentTarget.java:106) at org.jboss.profileservice.management.client.upload.DeploymentProgressImpl.distribute(DeploymentProgressImpl.java:178) at org.jboss.profileservice.management.client.upload.DeploymentProgressImpl.run(DeploymentProgressImpl.java:83) at org.jboss.arquillian.container.jbossas.remote_6.JBossASRemoteContainer.deploy(JBossASRemoteContainer.java:144) ... 21 more Caused by: java.io.IOException: Can not get connection to server. Problem establishing socket connection for InvokerLocator [socket://envy:10234/] at org.jboss.remoting.stream.StreamHandler.read(StreamHandler.java:382) at org.jboss.vfs.VFSUtils.copyStream(VFSUtils.java:426) at org.jboss.vfs.VFSUtils.copyStream(VFSUtils.java:406) at org.jboss.profileservice.repository.artifact.CopyStreamArtifactTransformer.transform(CopyStreamArtifactTransformer.java:59) at org.jboss.profileservice.repository.artifact.file.MutableFileArtifactRepository.addArtifact(MutableFileArtifactRepository.java:92) at org.jboss.profileservice.repository.artifact.file.MutableFileArtifactRepository.addArtifact(MutableFileArtifactRepository.java:46) at org.jboss.profileservice.plugins.deploy.actions.DeploymentDistributeAction.doPrepare(DeploymentDistributeAction.java:108) at org.jboss.profileservice.management.actions.AbstractTwoPhaseModificationAction.prepare(AbstractTwoPhaseModificationAction.java:101) at org.jboss.profileservice.management.ModificationSession.prepare(ModificationSession.java:87) at org.jboss.profileservice.management.AbstractActionController.internalPerfom(AbstractActionController.java:234) at org.jboss.profileservice.management.AbstractActionController.performWrite(AbstractActionController.java:213) at org.jboss.profileservice.management.AbstractActionController.perform(AbstractActionController.java:150) at org.jboss.profileservice.plugins.deploy.AbstractDeployHandler.addDeployment(AbstractDeployHandler.java:133) at org.jboss.profileservice.management.upload.remoting.DeployHandlerDelegate.distribute(DeployHandlerDelegate.java:68) at org.jboss.profileservice.management.upload.remoting.DeployHandler.handleStream(DeployHandler.java:200) at org.jboss.profileservice.management.upload.remoting.DeployHandler.handleStream(DeployHandler.java:55) at org.jboss.remoting.ServerInvoker.handleInternalInvocation(ServerInvoker.java:1809) This may depend on an upstream problem in JBoss AS. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 11 months

3
7
0 / 0

[JBoss JIRA] Updated: (ARQAJO-17) fix JQueryLocator.getNthOccurence and .getNthChild() methods to return proper values

by Lukas Fryc (JIRA)

[ https://issues.jboss.org/browse/ARQAJO-17?page=com.atlassian.jira.plugin.... ] Lukas Fryc updated ARQAJO-17: ----------------------------- Fix Version/s: 1.0.0.Alpha2 > fix JQueryLocator.getNthOccurence and .getNthChild() methods to return proper values > ------------------------------------------------------------------------------------ > > Key: ARQAJO-17 > URL: https://issues.jboss.org/browse/ARQAJO-17 > Project: Arquillian Ajocado > Issue Type: Bug > Environment: richfaces-selenium:1.5.0.Final > Reporter: Lukas Fryc > Assignee: Lukas Fryc > Fix For: 1.0.0.Alpha2 > > > The getNthChild internally uses :nth-child jQuery selector, but it isn't proper meaning for such operation. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 11 months

1
0
0 / 0

[JBoss JIRA] Updated: (ARQAJO-14) Harden FailureLoggingTestListener againts SeleniumException failures

by Lukas Fryc (JIRA)

[ https://issues.jboss.org/browse/ARQAJO-14?page=com.atlassian.jira.plugin.... ] Lukas Fryc updated ARQAJO-14: ----------------------------- Fix Version/s: 1.0.0.Alpha2 > Harden FailureLoggingTestListener againts SeleniumException failures > -------------------------------------------------------------------- > > Key: ARQAJO-14 > URL: https://issues.jboss.org/browse/ARQAJO-14 > Project: Arquillian Ajocado > Issue Type: Feature Request > Reporter: Lukas Fryc > Assignee: Lukas Fryc > Fix For: 1.0.0.Alpha2 > > > When selenium fails to run command in failure logging listener, all next test cases fails due to fail of listener. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 11 months

1
0
0 / 0

[JBoss JIRA] Updated: (ARQAJO-11) Replace selenium.keyDown(String) with selenium.keyDown(KeyCode)

by Lukas Fryc (JIRA)

[ https://issues.jboss.org/browse/ARQAJO-11?page=com.atlassian.jira.plugin.... ] Lukas Fryc updated ARQAJO-11: ----------------------------- Fix Version/s: 1.0.0.Alpha2 > Replace selenium.keyDown(String) with selenium.keyDown(KeyCode) > --------------------------------------------------------------- > > Key: ARQAJO-11 > URL: https://issues.jboss.org/browse/ARQAJO-11 > Project: Arquillian Ajocado > Issue Type: Enhancement > Reporter: Lukas Fryc > Assignee: Lukas Fryc > Fix For: 1.0.0.Alpha2 > > > Currently, keyDown and similar methods accepts String JavaScript key codes. > It will be better to accept enumeration or extensible enumeration instead. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 11 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

arquillian-issues February 2011