February 2012 - arquillian-issues

[JBoss JIRA] (ARQ-648) Implement @ArquillianResource Map<URL> for multi-container configuration.

by Ondrej Zizka (Created) (JIRA)

Implement @ArquillianResource Map<URL> for multi-container configuration. ------------------------------------------------------------------------- Key: ARQ-648 URL: https://issues.jboss.org/browse/ARQ-648 Project: Arquillian Issue Type: Feature Request Security Level: Public (Everyone can see) Reporter: Ondrej Zizka Would work like @ArquillianResource URL url; Only would fill all container infos. Key would be container's qualifier. -- 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

12 years, 10 months

6
5
0 / 0

[JBoss JIRA] (ARQ-753) ShrinkWrapClassLoader does not find service provider in WAR

by Aslak Knutsen (JIRA)

[ https://issues.jboss.org/browse/ARQ-753?page=com.atlassian.jira.plugin.sy... ] Aslak Knutsen updated ARQ-753: ------------------------------ Status: Resolved (was: Pull Request Sent) Assignee: Martin Kouba Fix Version/s: weld_1.0.0.Final Resolution: Done pushed upstream > ShrinkWrapClassLoader does not find service provider in WAR > ----------------------------------------------------------- > > Key: ARQ-753 > URL: https://issues.jboss.org/browse/ARQ-753 > Project: Arquillian > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Weld Containers > Affects Versions: weld_1.0.0.CR3 > Reporter: Martin Kouba > Assignee: Martin Kouba > Fix For: weld_1.0.0.Final > > > I ran into this issue when working with *Arquillian* and *Weld EE 1.1 Embedded container* (that uses ShrinkWrapClassLoader under the hood). ShrinkWrap correctly builds web archive with CDI extension (using org.jboss.shrinkwrap.api.container.ManifestContainer.addAsServiceProvider(Class<?>, Class<?>...); this was also discussed in SHRINKWRAP-266). > Output: > {code} > test.war > /WEB-INF/ > /WEB-INF/classes/ > /WEB-INF/classes/META-INF/ > /WEB-INF/classes/META-INF/services/ > /WEB-INF/classes/META-INF/services/javax.enterprise.inject.spi.Extension > {code} > However no extensions are found. *org.jboss.shrinkwrap.api.classloader.ShrinkWrapClassLoader* probably does not find any resource when looking for "META-INF/services/javax.enterprise.inject.spi.Extension". > Note that I'm not quite sure whether it's ShrinkWrapClassLoader or WeldEEMockContainer issue. -- 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

12 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ARQ-753) ShrinkWrapClassLoader does not find service provider in WAR

by Aslak Knutsen (JIRA)

[ https://issues.jboss.org/browse/ARQ-753?page=com.atlassian.jira.plugin.sy... ] Aslak Knutsen moved SHRINKWRAP-369 to ARQ-753: ---------------------------------------------- Project: Arquillian (was: ShrinkWrap) Key: ARQ-753 (was: SHRINKWRAP-369) Affects Version/s: weld_1.0.0.CR3 (was: 1.0.0-beta-3) Component/s: Weld Containers (was: api) Security: Public > ShrinkWrapClassLoader does not find service provider in WAR > ----------------------------------------------------------- > > Key: ARQ-753 > URL: https://issues.jboss.org/browse/ARQ-753 > Project: Arquillian > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Weld Containers > Affects Versions: weld_1.0.0.CR3 > Reporter: Martin Kouba > > I ran into this issue when working with *Arquillian* and *Weld EE 1.1 Embedded container* (that uses ShrinkWrapClassLoader under the hood). ShrinkWrap correctly builds web archive with CDI extension (using org.jboss.shrinkwrap.api.container.ManifestContainer.addAsServiceProvider(Class<?>, Class<?>...); this was also discussed in SHRINKWRAP-266). > Output: > {code} > test.war > /WEB-INF/ > /WEB-INF/classes/ > /WEB-INF/classes/META-INF/ > /WEB-INF/classes/META-INF/services/ > /WEB-INF/classes/META-INF/services/javax.enterprise.inject.spi.Extension > {code} > However no extensions are found. *org.jboss.shrinkwrap.api.classloader.ShrinkWrapClassLoader* probably does not find any resource when looking for "META-INF/services/javax.enterprise.inject.spi.Extension". > Note that I'm not quite sure whether it's ShrinkWrapClassLoader or WeldEEMockContainer issue. -- 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

12 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ARQ-696) Last test's standard output is not recorded - probably missing flush() ?

by Ondrej Zizka (Created) (JIRA)

Last test's standard output is not recorded - probably missing flush() ? ------------------------------------------------------------------------ Key: ARQ-696 URL: https://issues.jboss.org/browse/ARQ-696 Project: Arquillian Issue Type: Bug Security Level: Public (Everyone can see) Components: Base Implementation Affects Versions: 1.0.0.CR5 Reporter: Ondrej Zizka When a suite of tests is run, the last test's stdout is not stored in ...-output.txt. It's always the last test, whichever it happens to be. It seems like Arquillian forgets to call a flush or something, and Surefire, not having anything in buffer, creates an empty file. Steps to reproduce with JBoss AS 7: -- 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

12 years, 10 months

5
4
0 / 0

[JBoss JIRA] (ARQ-747) Arquillian Extension Persistence - DB cleanup does not work with Maven Archetype

by david meier (JIRA)

david meier created ARQ-747: ------------------------------- Summary: Arquillian Extension Persistence - DB cleanup does not work with Maven Archetype Key: ARQ-747 URL: https://issues.jboss.org/browse/ARQ-747 Project: Arquillian Issue Type: Bug Security Level: Public (Everyone can see) Components: Integration Test Suite Affects Versions: persistence_1.0.0.Alpha3 Environment: Eclipse JavaEE IDE for Web Developers, Indigo SR1 Win7 x64 Java 1.7.0-b147 jboss-as-web-7.0.2.Final Reporter: david meier You can easily reproduce it yourself, based on maven archetypes. After executing steps to reproduce: Actual result: if method testRegister() is executed before testProducer(), then the latter fails. Because getMembers() does return a list of size == 1. Expected result: as the DB is to be cleaned after each test, the getMembers() method should be empty and both tests should verify. -- 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

12 years, 10 months

3
5
0 / 0

[JBoss JIRA] (ARQ-690) Verify ability to run under a security manager (evt. create a policy file)

by Ondrej Zizka (Created) (JIRA)

Verify ability to run under a security manager (evt. create a policy file) -------------------------------------------------------------------------- Key: ARQ-690 URL: https://issues.jboss.org/browse/ARQ-690 Project: Arquillian Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Base Implementation, JBoss Containers Affects Versions: 1.0.0.CR6 Reporter: Ondrej Zizka Assignee: Aslak Knutsen Verify whether Arquillian is able to run under security manager. Presumably, we need to create a security policy file for arquillian. Test with JBoss AS7 testsuite, using -Dsecurity.manager [ -Dsecurity.policy=<path>] - see https://docs.jboss.org/author/display/AS71/AS+7+Integration+Testsuite+Use... . -- 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

12 years, 10 months

3
5
0 / 0

[JBoss JIRA] Created: (ARQ-347) Seam 2 integration

by Michael Schuetz (JIRA)

Seam 2 integration ------------------ Key: ARQ-347 URL: https://issues.jboss.org/browse/ARQ-347 Project: Arquillian Issue Type: Feature Request Reporter: Michael Schuetz This needs to be done: * create framework-integration * implement AuxiliaryArchiveAppender * implement TestEnricher -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 10 months

7
15
0 / 0

[JBoss JIRA] (ARQ-746) Run tests on different containers, stopping and starting them between tests (with automatic grouping).

by Ondrej Zizka (JIRA)

Ondrej Zizka created ARQ-746: -------------------------------- Summary: Run tests on different containers, stopping and starting them between tests (with automatic grouping). Key: ARQ-746 URL: https://issues.jboss.org/browse/ARQ-746 Project: Arquillian Issue Type: Feature Request Security Level: Public (Everyone can see) Affects Versions: 1.0.0.CR5 Reporter: Ondrej Zizka Assignee: Aslak Knutsen Tests would have {{@ContainerInstance("InstanceName")}}. As Arquillian would run these tests, it would stop the currently running container and start the other one. {code:java} @TestCase @ContainerInstance("InstanceFoo") class TestsToBeRunOnFooTestCase { ... } @TestCase @ContainerInstance("InstanceBar") class TestsToBeRunOnBarTestCase { ... } @TestCase @ContainerInstance("InstanceFoo") class TestsToBeRunOnFoo2TestCase { ... } {code} With this setup, Arq would: * start InstanceFoo * run TestsToBeRunOnFooTestCase * run TestsToBeRunOnFoo2TestCase * stop InstanceFoo * start InstanceBar * run TestsToBeRunOnBarTestCase. * stop InstanceBar To optimize a bit, Arquillian could order the test to group them by instance name. -- 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

12 years, 10 months

1
1
0 / 0

[JBoss JIRA] (ARQ-745) @RestoreASConfigAfterTest to make a snapshot before test and reload it after.

by Ondrej Zizka (JIRA)

Ondrej Zizka created ARQ-745: -------------------------------- Summary: @RestoreASConfigAfterTest to make a snapshot before test and reload it after. Key: ARQ-745 URL: https://issues.jboss.org/browse/ARQ-745 Project: Arquillian Issue Type: Feature Request Security Level: Public (Everyone can see) Reporter: Ondrej Zizka Assignee: Aslak Knutsen Having a possibility to restore server configuration after the test is run, or similar principle, would be very cool. For example, there are some tests which change datasource config quite dramatically. And getting it back to the original state afterwards requires a lot of coding. So instead, the test would have {{@RestoreASConfigAfterTest}} and Arq would re-load a snapshot it made before the test was run. -- 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

12 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ARQ-743) Prepare Seam2 Alpha1 release

by Aslak Knutsen (JIRA)

Aslak Knutsen created ARQ-743: --------------------------------- Summary: Prepare Seam2 Alpha1 release Key: ARQ-743 URL: https://issues.jboss.org/browse/ARQ-743 Project: Arquillian Issue Type: Release Security Level: Public (Everyone can see) Components: Extension - Seam2 Reporter: Aslak Knutsen Assignee: Aslak Knutsen Fix For: seam2_1.0.0.Alpha1 -- 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

12 years, 10 months

1
2
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

arquillian-issues February 2012