January 2011 - arquillian-issues - Jboss List Archives

[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, 1 month

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, 2 months

3
7
0 / 0

[JBoss JIRA] Created: (ARQ-307) In an EAR deployment, allow the customization of test.war

by Marius Bogoevici (JIRA)

In an EAR deployment, allow the customization of test.war --------------------------------------------------------- Key: ARQ-307 URL: https://jira.jboss.org/browse/ARQ-307 Project: Arquillian Issue Type: Feature Request Affects Versions: 1.0.0.Alpha4 Reporter: Marius Bogoevici In an EAR deployment, the test.war attached by arquillian replaces a test.war configuration provided by the user. Ideally, it should be possible to allow test writers to attach artifacts to it. -- 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, 3 months

2
1
0 / 0

[JBoss JIRA] Created: (ARQ-176) Create integration tests for all CDI related deployment scenarios

by Aslak Knutsen (JIRA)

Create integration tests for all CDI related deployment scenarios ----------------------------------------------------------------- Key: ARQ-176 URL: https://jira.jboss.org/browse/ARQ-176 Project: Arquillian Issue Type: Task Components: Integration Test Suite Reporter: Aslak Knutsen Create a deployment integration test suite for all possible CDI related deployment types. EJB, WAR, JAR etc. -- 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, 3 months

1
2
0 / 0

[JBoss JIRA] Created: (ARQ-104) TestEnrichment TestCase injection null in @Before

by Aslak Knutsen (JIRA)

TestEnrichment TestCase injection null in @Before ------------------------------------------------- Key: ARQ-104 URL: https://jira.jboss.org/jira/browse/ARQ-104 Project: Arquillian Issue Type: Bug Components: Runtime Enricher SPI Affects Versions: 1.0.0.Alpha1 Reporter: Aslak Knutsen Assignee: Aslak Knutsen Fix For: 1.0.0.Alpha2 Injection is done in the @Test cycle, should be moved to @Before cycle so one can setup injected resources before test is executed. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 3 months

2
5
0 / 0

[JBoss JIRA] Created: (ARQ-358) Should be able to disable specific Enrichers

by Aslak Knutsen (JIRA)

Should be able to disable specific Enrichers -------------------------------------------- Key: ARQ-358 URL: https://issues.jboss.org/browse/ARQ-358 Project: Arquillian Issue Type: Feature Request Components: Runtime Enricher SPI Affects Versions: 1.0.0.Alpha4 Reporter: Aslak Knutsen In some cases you don't want the other enrichers to jump in and resolve things. e.g. in a CDI test suite, @EJB injections should only be handled by CDI, not the EJBEnricher as well if CDI fails (that might be the test) -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 3 months

1
0
0 / 0

[JBoss JIRA] Created: (ARQ-354) Support manual install/uninstall of rules

by Aslak Knutsen (JIRA)

Support manual install/uninstall of rules ----------------------------------------- Key: ARQ-354 URL: https://issues.jboss.org/browse/ARQ-354 Project: Arquillian Issue Type: Feature Request Components: Extension - Byteman Reporter: Aslak Knutsen Priority: Minor The byteman integration should piggyback on the infrastructure given by the Deployer API and open for manual installation of rules during test execution. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 4 months

1
0
0 / 0

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

by Aslak Knutsen (JIRA)

[ https://issues.jboss.org/browse/ARQ-353?page=com.atlassian.jira.plugin.sy... ] Aslak Knutsen updated ARQ-353: ------------------------------ Description: 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.Final</version> <type>pom</type> <scope>provided</scope> </dependency> was: 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> > 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.Final</version> > <type>pom</type> > <scope>provided</scope> > </dependency> -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 4 months

1
0
0 / 0

[JBoss JIRA] Updated: (ARQ-349) Create a Protocol processor SPI for modifying the final deployment generated by the DeploymentPackager

by Aslak Knutsen (JIRA)

[ https://issues.jboss.org/browse/ARQ-349?page=com.atlassian.jira.plugin.sy... ] Aslak Knutsen updated ARQ-349: ------------------------------ Summary: Create a Protocol processor SPI for modifying the final deployment generated by the DeploymentPackager (was: Create a Protocol processor SPI for modifying the Protocol create final deployment) > Create a Protocol processor SPI for modifying the final deployment generated by the DeploymentPackager > ------------------------------------------------------------------------------------------------------- > > Key: ARQ-349 > URL: https://issues.jboss.org/browse/ARQ-349 > Project: Arquillian > Issue Type: Feature Request > Components: Packaging Enricher SPI > Reporter: Aslak Knutsen > > In some cases we need to modify the Protocol generated Deployment. > In the case of CDI, it's BeanManagers are hierarchical, a BeanManager created for a ejb-jar in a ear is not visible to a war unless the war also contains a beans.xml. When using the Servlet Protocol, a war is added without a beans.xml since the protocol it self is unaware of CDI, and Beans are never injected into the testcase. > DeploymentProcessor.process(TestClass relevant class, TestDeployment auxAndApplicationArchives, Archive<?> finalDeployment); > https://issues.jboss.org/browse/WELD-709 -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 4 months

1
0
0 / 0

[JBoss JIRA] Created: (ARQ-106) AfterSuite event is never called with JUnit

by Aslak Knutsen (JIRA)

AfterSuite event is never called with JUnit ------------------------------------------- Key: ARQ-106 URL: https://jira.jboss.org/jira/browse/ARQ-106 Project: Arquillian Issue Type: Bug Components: Test Harness Integration Affects Versions: 1.0.0.Alpha1 Reporter: Aslak Knutsen Currently using a JVM Shutdown hook to call AfterSuite. This is never called. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 4 months

2
12
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

arquillian-issues January 2011