February 2014 - arquillian-issues

[JBoss JIRA] (ARQ-1654) Expose an ExecutorService to help Extension with multithreading

by Lukáš Fryč (JIRA)

[ https://issues.jboss.org/browse/ARQ-1654?page=com.atlassian.jira.plugin.s... ] Lukáš Fryč edited comment on ARQ-1654 at 2/26/14 4:11 PM: ---------------------------------------------------------- In Warp, I have implemented the idea of [OperationalContexts|https://github.com/arquillian/arquillian-extension-wa...]: * you can choose what contexts you want to propagate (e.g. what is a lifespan of the callable) * it reflects the hierarchy (nesting) of contexts * allows extensions for custom contexts Additional there is [Contextualizer|https://github.com/arquillian/arquillian-extension-warp/bl...] that you provide with either OperationalContext or its Retriever and it will make the given instance invocations to activate appropriate contexts. was (Author: lfryc): In Warp, I have implemented the idea of [OperationalContexts|https://github.com/arquillian/arquillian-extension-wa...]: * you can choose what contexts you want to propagate (e.g. what is a lifespan of the callable) * it reflects the hierarchy (nesting) of contexts * allows extensions for custom contexts > Expose an ExecutorService to help Extension with multithreading > --------------------------------------------------------------- > > Key: ARQ-1654 > URL: https://issues.jboss.org/browse/ARQ-1654 > Project: Arquillian > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Base Implementation > Affects Versions: 1.1.3.Final > Reporter: Aslak Knutsen > Assignee: Aslak Knutsen > Fix For: 2.0.0.Beta1 > > > Expose a Service to execute Callable's and Runnable's within a Inherited context. > The general idea is to hide the complexity of reactivating the current Contextual information on the new Thread. > ExecutorService needs to be a limited view of the java.utl.concurrent.ExecutorService to avoid 'abuse' like shutdown being called prematurely. > The submit$\*$ methods should probably be enough. -- 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

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ARQ-1654) Expose an ExecutorService to help Extension with multithreading

by Lukáš Fryč (JIRA)

[ https://issues.jboss.org/browse/ARQ-1654?page=com.atlassian.jira.plugin.s... ] Lukáš Fryč edited comment on ARQ-1654 at 2/26/14 4:09 PM: ---------------------------------------------------------- In Warp, I have implemented the idea of [OperationalContexts|https://github.com/arquillian/arquillian-extension-wa...]: * you can choose what contexts you want to propagate (e.g. what is a lifespan of the callable) * it reflects the hierarchy (nesting) of contexts * allows extensions for custom contexts was (Author: lfryc): In Warp, I have implemented the idea of OperationalContexts: * you can choose what contexts you want to propagate (e.g. what is a lifespan of the callable) * it reflects the hierarchy (nesting) of contexts * allows extensions for custom contexts > Expose an ExecutorService to help Extension with multithreading > --------------------------------------------------------------- > > Key: ARQ-1654 > URL: https://issues.jboss.org/browse/ARQ-1654 > Project: Arquillian > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Base Implementation > Affects Versions: 1.1.3.Final > Reporter: Aslak Knutsen > Assignee: Aslak Knutsen > Fix For: 2.0.0.Beta1 > > > Expose a Service to execute Callable's and Runnable's within a Inherited context. > The general idea is to hide the complexity of reactivating the current Contextual information on the new Thread. > ExecutorService needs to be a limited view of the java.utl.concurrent.ExecutorService to avoid 'abuse' like shutdown being called prematurely. > The submit$\*$ methods should probably be enough. -- 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

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ARQ-1654) Expose an ExecutorService to help Extension with multithreading

by Lukáš Fryč (JIRA)

[ https://issues.jboss.org/browse/ARQ-1654?page=com.atlassian.jira.plugin.s... ] Lukáš Fryč commented on ARQ-1654: --------------------------------- In Warp, I have implemented the idea of OperationalContexts: * you can choose what contexts you want to propagate (e.g. what is a lifespan of the callable) * it reflects the hierarchy (nesting) of contexts * allows extensions for custom contexts > Expose an ExecutorService to help Extension with multithreading > --------------------------------------------------------------- > > Key: ARQ-1654 > URL: https://issues.jboss.org/browse/ARQ-1654 > Project: Arquillian > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Base Implementation > Affects Versions: 1.1.3.Final > Reporter: Aslak Knutsen > Assignee: Aslak Knutsen > Fix For: 2.0.0.Beta1 > > > Expose a Service to execute Callable's and Runnable's within a Inherited context. > The general idea is to hide the complexity of reactivating the current Contextual information on the new Thread. > ExecutorService needs to be a limited view of the java.utl.concurrent.ExecutorService to avoid 'abuse' like shutdown being called prematurely. > The submit$\*$ methods should probably be enough. -- 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

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ARQ-1664) Provide custom table filter for seeding and cleaning databases

by Bartosz Majsak (JIRA)

[ https://issues.jboss.org/browse/ARQ-1664?page=com.atlassian.jira.plugin.s... ] Work on ARQ-1664 started by Bartosz Majsak. > Provide custom table filter for seeding and cleaning databases > -------------------------------------------------------------- > > Key: ARQ-1664 > URL: https://issues.jboss.org/browse/ARQ-1664 > Project: Arquillian > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Extension - Persistence > Affects Versions: persistence_1.0.0.Alpha6 > Reporter: Bartosz Majsak > Assignee: Bartosz Majsak > Fix For: persistence_1.0.0.next > > > In order to resolve Foreign Key dependency and remove tables in the correct order DatabaseSequenceFilter has been introduced. As itis causing significant performance drop, especially in Oracle DB, it should be possible to define custom table filtering through SPI mechanism. This is also useful when seeding database. -- 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

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ARQ-1664) Provide custom table filter for seeding and cleaning databases

by Bartosz Majsak (JIRA)

Bartosz Majsak created ARQ-1664: ----------------------------------- Summary: Provide custom table filter for seeding and cleaning databases Key: ARQ-1664 URL: https://issues.jboss.org/browse/ARQ-1664 Project: Arquillian Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Extension - Persistence Affects Versions: persistence_1.0.0.Alpha6 Reporter: Bartosz Majsak Assignee: Bartosz Majsak Fix For: persistence_1.0.0.next In order to resolve Foreign Key dependency and remove tables in the correct order DatabaseSequenceFilter has been introduced. As itis causing significant performance drop, especially in Oracle DB, it should be possible to define custom table filtering through SPI mechanism. This is also useful when seeding database. -- 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

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ARQ-1147) Improve the column filtering feature to use custom IColumnFilter implementations

by Bartosz Majsak (JIRA)

[ https://issues.jboss.org/browse/ARQ-1147?page=com.atlassian.jira.plugin.s... ] Bartosz Majsak updated ARQ-1147: -------------------------------- Fix Version/s: persistence_1.0.0.next > Improve the column filtering feature to use custom IColumnFilter implementations > -------------------------------------------------------------------------------- > > Key: ARQ-1147 > URL: https://issues.jboss.org/browse/ARQ-1147 > Project: Arquillian > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Extension - Persistence > Reporter: Vineet Reynolds > Assignee: Vineet Reynolds > Fix For: persistence_1.0.0.next > > > For now, APE implements column filtering based on column names specified in the {{excludeColumns}} attribute of the {{@ShouldMatchDataSet}} annotation (introduced in ARQ-772). This could be extended to allow custom {{IColumnFilter}} implementations to be plugged in during the verification phase. > The use of {{IColumnFilter}} implementations is described here: http://www.dbunit.org/faq.html#columnfilter -- 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

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ARQ-1131) Improve DBUnit database connection handling

by Bartosz Majsak (JIRA)

[ https://issues.jboss.org/browse/ARQ-1131?page=com.atlassian.jira.plugin.s... ] Bartosz Majsak commented on ARQ-1131: ------------------------------------- Rolled back to the original approach [@ea0984f|https://github.com/arquillian/arquillian-extension-persistence/commit/ea0984f7cb727865c40675df1989b9bbc940e16a] > Improve DBUnit database connection handling > ------------------------------------------- > > Key: ARQ-1131 > URL: https://issues.jboss.org/browse/ARQ-1131 > Project: Arquillian > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: Extension - Persistence > Reporter: Bartosz Majsak > Assignee: Bartosz Majsak > Fix For: persistence_1.0.0.next > > > -As Vineet Reynolds pointed out, current implementation initializes the connection and holds on to it, until the verification is performed. It would be better to relinquish the connection after the seeding phase (so utilize it only around "before persistence test" event), and obtain another connection for the dataset verification phase (around "after persistence test" event).- -- 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

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ARQ-1131) Improve DBUnit database connection handling

by Bartosz Majsak (JIRA)

[ https://issues.jboss.org/browse/ARQ-1131?page=com.atlassian.jira.plugin.s... ] Bartosz Majsak updated ARQ-1131: -------------------------------- Fix Version/s: (was: persistence_1.0.0.next) > Improve DBUnit database connection handling > ------------------------------------------- > > Key: ARQ-1131 > URL: https://issues.jboss.org/browse/ARQ-1131 > Project: Arquillian > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: Extension - Persistence > Reporter: Bartosz Majsak > Assignee: Bartosz Majsak > > -As Vineet Reynolds pointed out, current implementation initializes the connection and holds on to it, until the verification is performed. It would be better to relinquish the connection after the seeding phase (so utilize it only around "before persistence test" event), and obtain another connection for the dataset verification phase (around "after persistence test" event).- -- 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

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ARQ-1663) Glassfish fails to shutdown fast enough and breaks subsequent test

by Aslak Knutsen (JIRA)

[ https://issues.jboss.org/browse/ARQ-1663?page=com.atlassian.jira.plugin.s... ] Aslak Knutsen commented on ARQ-1663: ------------------------------------ something similar to this; https://github.com/wildfly/wildfly/blob/master/arquillian/container-manag... > Glassfish fails to shutdown fast enough and breaks subsequent test > ------------------------------------------------------------------ > > Key: ARQ-1663 > URL: https://issues.jboss.org/browse/ARQ-1663 > Project: Arquillian > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: GlassFish Containers > Affects Versions: glassfish_1.0.0.CR4 > Reporter: Lukáš Fryč > > When a maven build is executed with Glassfish 4.0 and Glassfish container adapter 1.0.0.CR4 > and the maven contains several modules that run subsequently and make use of Arquillian, > the first module doesn't shutdown the test fast enough and this makes the subsequent maven module test execution fail. > ---- > Reproducer: > https://github.com/arquillian/arquillian-extension-warp/commit/3580210318... > mvn clean install -Dmaven.test.failure.ignore=true -Dintegration=glassfish40 > All the tests in {{jsf-ftest}} module due to the exception that the container wasn't started. -- 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

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ARQ-1071) NullPointerException when timeout is set in @Test when using JUnit

by Aslak Knutsen (JIRA)

[ https://issues.jboss.org/browse/ARQ-1071?page=com.atlassian.jira.plugin.s... ] Aslak Knutsen resolved ARQ-1071. -------------------------------- Assignee: Aslak Knutsen Fix Version/s: 1.1.4.Final Resolution: Done upstream https://github.com/arquillian/arquillian-core/commit/c5c73f0fb89114fb9144... > NullPointerException when timeout is set in @Test when using JUnit > ------------------------------------------------------------------ > > Key: ARQ-1071 > URL: https://issues.jboss.org/browse/ARQ-1071 > Project: Arquillian > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 1.0.0.Final, 1.0.1.Final, 1.1.3.Final > Reporter: Rick-Rainer Ludwig > Assignee: Aslak Knutsen > Fix For: 1.1.4.Final > > > When defining a timeout in @Test of JUnit Arquillian throws a NullPointerException: > {code} > java.lang.NullPointerException > at org.jboss.arquillian.junit.Arquillian$6.evaluate(Arquillian.java:263) > at org.junit.internal.runners.statements.FailOnTimeout$StatementThread.run(FailOfTimeout.java:62) > {code} > The code to reproduce this: > {code} > import org.jboss.arquillian.junit.Arquillian; > import org.junit.Test; > import org.junit.runner.RunWith; > @RunWith(Arquillian.class) > public class TestTimeout { > @Test(timeout = 3000) > public void test() throws Exception { > Thread.sleep(1000); > } > } > {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

10 years, 10 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

arquillian-issues February 2014