February 2018 - arquillian-issues

[JBoss JIRA] (ARQ-2175) DeploymentExceptionHandler can sometimes pass null to transformers

by Matous Jobanek (JIRA)

[ https://issues.jboss.org/browse/ARQ-2175?page=com.atlassian.jira.plugin.s... ] Matous Jobanek updated ARQ-2175: -------------------------------- Fix Version/s: 1.4.0.Final > DeploymentExceptionHandler can sometimes pass null to transformers > ------------------------------------------------------------------ > > Key: ARQ-2175 > URL: https://issues.jboss.org/browse/ARQ-2175 > Project: Arquillian > Issue Type: Bug > Components: core > Affects Versions: 1.3.0.Final > Reporter: Matej Novotny > Assignee: Matej Novotny > Fix For: 1.4.0.Final > > > In some rare cases {{DeploymentExceptionHandler}} can pass null value to transformers, which isn't really useful. > This can happen when the exception is {{DeploymentException}} which has no cause (or has itself set as cause). E.g. [this code|https://github.com/arquillian/arquillian-core/blob/1.3.0.Final/conta...] can yield {{null}}. > I came across this in combination with [wildfly-arquillian|https://github.com/wildfly/wildfly-arquillian] and certain Arq. interceptor ordering (so that this exception handler was called first and the exception wasn't wrapped yet). -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ARQ-2175) DeploymentExceptionHandler can sometimes pass null to transformers

by Matous Jobanek (JIRA)

[ https://issues.jboss.org/browse/ARQ-2175?page=com.atlassian.jira.plugin.s... ] Matous Jobanek closed ARQ-2175. ------------------------------- Resolution: Done Pushed upstream in https://github.com/arquillian/arquillian-core/commit/d5f4f93661e57d3695fa... > DeploymentExceptionHandler can sometimes pass null to transformers > ------------------------------------------------------------------ > > Key: ARQ-2175 > URL: https://issues.jboss.org/browse/ARQ-2175 > Project: Arquillian > Issue Type: Bug > Components: core > Affects Versions: 1.3.0.Final > Reporter: Matej Novotny > Assignee: Matej Novotny > Fix For: 1.4.0.Final > > > In some rare cases {{DeploymentExceptionHandler}} can pass null value to transformers, which isn't really useful. > This can happen when the exception is {{DeploymentException}} which has no cause (or has itself set as cause). E.g. [this code|https://github.com/arquillian/arquillian-core/blob/1.3.0.Final/conta...] can yield {{null}}. > I came across this in combination with [wildfly-arquillian|https://github.com/wildfly/wildfly-arquillian] and certain Arq. interceptor ordering (so that this exception handler was called first and the exception wasn't wrapped yet). -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ARQ-2177) Extend expression language in arquillian configuration

by Matous Jobanek (JIRA)

[ https://issues.jboss.org/browse/ARQ-2177?page=com.atlassian.jira.plugin.s... ] Matous Jobanek updated ARQ-2177: -------------------------------- Fix Version/s: 1.4.0.Final > Extend expression language in arquillian configuration > ------------------------------------------------------ > > Key: ARQ-2177 > URL: https://issues.jboss.org/browse/ARQ-2177 > Project: Arquillian > Issue Type: Enhancement > Reporter: Alex Soto > Fix For: 1.4.0.Final > > > Add ability to refer to a file being available in the project, but expended to the full path during test execution, so we can refer to it in a flexible way. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ARQ-2177) Extend expression language in arquillian configuration

by Matous Jobanek (JIRA)

[ https://issues.jboss.org/browse/ARQ-2177?page=com.atlassian.jira.plugin.s... ] Matous Jobanek reassigned ARQ-2177: ----------------------------------- Assignee: Alex Soto > Extend expression language in arquillian configuration > ------------------------------------------------------ > > Key: ARQ-2177 > URL: https://issues.jboss.org/browse/ARQ-2177 > Project: Arquillian > Issue Type: Enhancement > Reporter: Alex Soto > Assignee: Alex Soto > Fix For: 1.4.0.Final > > > Add ability to refer to a file being available in the project, but expended to the full path during test execution, so we can refer to it in a flexible way. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ARQ-2177) Extend expression language in arquillian configuration

by Matous Jobanek (JIRA)

[ https://issues.jboss.org/browse/ARQ-2177?page=com.atlassian.jira.plugin.s... ] Matous Jobanek closed ARQ-2177. ------------------------------- > Extend expression language in arquillian configuration > ------------------------------------------------------ > > Key: ARQ-2177 > URL: https://issues.jboss.org/browse/ARQ-2177 > Project: Arquillian > Issue Type: Enhancement > Reporter: Alex Soto > Assignee: Alex Soto > Fix For: 1.4.0.Final > > > Add ability to refer to a file being available in the project, but expended to the full path during test execution, so we can refer to it in a flexible way. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ARQ-2115) Create Arquillian adapter for WebSphere 9

by Gerhard Poul (JIRA)

[ https://issues.jboss.org/browse/ARQ-2115?page=com.atlassian.jira.plugin.s... ] Gerhard Poul commented on ARQ-2115: ----------------------------------- Yes, [~bmajsak] is correct. That is the current situation. I've had a discussion with someone from IBM last week and we'll see whether this can be changed or not; if you're a licensed customer you're certainly more than welcome to point IBM development or your IBM account reps in my direction as well to get this pushed in the right direction, if this is important for you. > Create Arquillian adapter for WebSphere 9 > ----------------------------------------- > > Key: ARQ-2115 > URL: https://issues.jboss.org/browse/ARQ-2115 > Project: Arquillian > Issue Type: Feature Request > Components: WebSphere Containers > Reporter: Marián Macik > Assignee: Gerhard Poul > Fix For: was_1.0.0.CR1 > > > Hi, guys, > I have created the Arquillian adapter for WebSphere 9. Here is the summary of the PR [1]: > \#### Short description of what this resolves: > Hi, guys, > my name is Marian Macik and I work at Red Hat as QE Engineer on [jBPM|https://github.com/kiegroup/jbpm] project. This PR introduces Arquillian container adapter for WebSphere 9. We have been using it at Red Hat in our QE automation for about two months without any issues. It is copied from adapter for WebSphere 8.5 (as WebSphere 8.5 was copied from WebSphere 8). There were only some minor changes when it comes to system paths pointing at WebSphere dependencies (jgss-provider and ws-admin-client). > However, since WebSphere 9, wsadmin is using jython27 by default. Jython21 is still supported and to use jython21, 'com.ibm.ws.admin.client.forJython21_9.0.jar' should be used. Moreover, the new wsadmin jar has additional libraries which are not used by Arquillian (such as Python JSR 223 implementation) and might cause issues when deploying and running tests. If this happens, simply override this property with jython21 jar: > {code} > -Dws_admin_client_jar_name=com.ibm.ws.admin.client.forJython21_9.0.jar > {code} > I added this property because the new jython27 wsadmin implementation was causing issues since it loaded unwanted classes on the classpath. Of course, by default the new jython27 wsadmin is used, override is optional. > I have also run the enclosed tests with my own arquillian.xml and they have passed. > Thanks, > Marian > [1] https://github.com/arquillian/arquillian-container-was/pull/29 -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ARQ-2115) Create Arquillian adapter for WebSphere 9

by Bartosz Majsak (JIRA)

[ https://issues.jboss.org/browse/ARQ-2115?page=com.atlassian.jira.plugin.s... ] Bartosz Majsak commented on ARQ-2115: ------------------------------------- AFAIK the only one we can officially release to Maven Central is based on open source Liberty Profile. The others you have to build yourself if you have WAS licensed. Maybe [~gpoul] can correct me if I'm wrong. > Create Arquillian adapter for WebSphere 9 > ----------------------------------------- > > Key: ARQ-2115 > URL: https://issues.jboss.org/browse/ARQ-2115 > Project: Arquillian > Issue Type: Feature Request > Components: WebSphere Containers > Reporter: Marián Macik > Assignee: Gerhard Poul > Fix For: was_1.0.0.CR1 > > > Hi, guys, > I have created the Arquillian adapter for WebSphere 9. Here is the summary of the PR [1]: > \#### Short description of what this resolves: > Hi, guys, > my name is Marian Macik and I work at Red Hat as QE Engineer on [jBPM|https://github.com/kiegroup/jbpm] project. This PR introduces Arquillian container adapter for WebSphere 9. We have been using it at Red Hat in our QE automation for about two months without any issues. It is copied from adapter for WebSphere 8.5 (as WebSphere 8.5 was copied from WebSphere 8). There were only some minor changes when it comes to system paths pointing at WebSphere dependencies (jgss-provider and ws-admin-client). > However, since WebSphere 9, wsadmin is using jython27 by default. Jython21 is still supported and to use jython21, 'com.ibm.ws.admin.client.forJython21_9.0.jar' should be used. Moreover, the new wsadmin jar has additional libraries which are not used by Arquillian (such as Python JSR 223 implementation) and might cause issues when deploying and running tests. If this happens, simply override this property with jython21 jar: > {code} > -Dws_admin_client_jar_name=com.ibm.ws.admin.client.forJython21_9.0.jar > {code} > I added this property because the new jython27 wsadmin implementation was causing issues since it loaded unwanted classes on the classpath. Of course, by default the new jython27 wsadmin is used, override is optional. > I have also run the enclosed tests with my own arquillian.xml and they have passed. > Thanks, > Marian > [1] https://github.com/arquillian/arquillian-container-was/pull/29 -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ARQ-2115) Create Arquillian adapter for WebSphere 9

by Marián Macik (JIRA)

[ https://issues.jboss.org/browse/ARQ-2115?page=com.atlassian.jira.plugin.s... ] Marián Macik edited comment on ARQ-2115 at 2/26/18 2:45 AM: ------------------------------------------------------------ Hi, [~bmajsak], does it mean that WebSphere adapter has finally been released and deployed to the Maven repo? was (Author: mmacik): Hi, [~bmajsak], does it mean that WebSphere adapter has finally been released to the Maven repo? > Create Arquillian adapter for WebSphere 9 > ----------------------------------------- > > Key: ARQ-2115 > URL: https://issues.jboss.org/browse/ARQ-2115 > Project: Arquillian > Issue Type: Feature Request > Components: WebSphere Containers > Reporter: Marián Macik > Assignee: Gerhard Poul > Fix For: was_1.0.0.CR1 > > > Hi, guys, > I have created the Arquillian adapter for WebSphere 9. Here is the summary of the PR [1]: > \#### Short description of what this resolves: > Hi, guys, > my name is Marian Macik and I work at Red Hat as QE Engineer on [jBPM|https://github.com/kiegroup/jbpm] project. This PR introduces Arquillian container adapter for WebSphere 9. We have been using it at Red Hat in our QE automation for about two months without any issues. It is copied from adapter for WebSphere 8.5 (as WebSphere 8.5 was copied from WebSphere 8). There were only some minor changes when it comes to system paths pointing at WebSphere dependencies (jgss-provider and ws-admin-client). > However, since WebSphere 9, wsadmin is using jython27 by default. Jython21 is still supported and to use jython21, 'com.ibm.ws.admin.client.forJython21_9.0.jar' should be used. Moreover, the new wsadmin jar has additional libraries which are not used by Arquillian (such as Python JSR 223 implementation) and might cause issues when deploying and running tests. If this happens, simply override this property with jython21 jar: > {code} > -Dws_admin_client_jar_name=com.ibm.ws.admin.client.forJython21_9.0.jar > {code} > I added this property because the new jython27 wsadmin implementation was causing issues since it loaded unwanted classes on the classpath. Of course, by default the new jython27 wsadmin is used, override is optional. > I have also run the enclosed tests with my own arquillian.xml and they have passed. > Thanks, > Marian > [1] https://github.com/arquillian/arquillian-container-was/pull/29 -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ARQ-2115) Create Arquillian adapter for WebSphere 9

by Marián Macik (JIRA)

[ https://issues.jboss.org/browse/ARQ-2115?page=com.atlassian.jira.plugin.s... ] Marián Macik edited comment on ARQ-2115 at 2/26/18 2:45 AM: ------------------------------------------------------------ Hi, [~bmajsak], does it mean that WebSphere adapter has finally been released to the Maven repo? was (Author: mmacik): Hi, [~bmajsak], does it mean that WebSphere adapter has finally been released? > Create Arquillian adapter for WebSphere 9 > ----------------------------------------- > > Key: ARQ-2115 > URL: https://issues.jboss.org/browse/ARQ-2115 > Project: Arquillian > Issue Type: Feature Request > Components: WebSphere Containers > Reporter: Marián Macik > Assignee: Gerhard Poul > Fix For: was_1.0.0.CR1 > > > Hi, guys, > I have created the Arquillian adapter for WebSphere 9. Here is the summary of the PR [1]: > \#### Short description of what this resolves: > Hi, guys, > my name is Marian Macik and I work at Red Hat as QE Engineer on [jBPM|https://github.com/kiegroup/jbpm] project. This PR introduces Arquillian container adapter for WebSphere 9. We have been using it at Red Hat in our QE automation for about two months without any issues. It is copied from adapter for WebSphere 8.5 (as WebSphere 8.5 was copied from WebSphere 8). There were only some minor changes when it comes to system paths pointing at WebSphere dependencies (jgss-provider and ws-admin-client). > However, since WebSphere 9, wsadmin is using jython27 by default. Jython21 is still supported and to use jython21, 'com.ibm.ws.admin.client.forJython21_9.0.jar' should be used. Moreover, the new wsadmin jar has additional libraries which are not used by Arquillian (such as Python JSR 223 implementation) and might cause issues when deploying and running tests. If this happens, simply override this property with jython21 jar: > {code} > -Dws_admin_client_jar_name=com.ibm.ws.admin.client.forJython21_9.0.jar > {code} > I added this property because the new jython27 wsadmin implementation was causing issues since it loaded unwanted classes on the classpath. Of course, by default the new jython27 wsadmin is used, override is optional. > I have also run the enclosed tests with my own arquillian.xml and they have passed. > Thanks, > Marian > [1] https://github.com/arquillian/arquillian-container-was/pull/29 -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ARQ-2115) Create Arquillian adapter for WebSphere 9

by Marián Macik (JIRA)

[ https://issues.jboss.org/browse/ARQ-2115?page=com.atlassian.jira.plugin.s... ] Marián Macik commented on ARQ-2115: ----------------------------------- Hi, [~bmajsak], does it mean that WebSphere adapter has finally been released? > Create Arquillian adapter for WebSphere 9 > ----------------------------------------- > > Key: ARQ-2115 > URL: https://issues.jboss.org/browse/ARQ-2115 > Project: Arquillian > Issue Type: Feature Request > Components: WebSphere Containers > Reporter: Marián Macik > Assignee: Gerhard Poul > Fix For: was_1.0.0.CR1 > > > Hi, guys, > I have created the Arquillian adapter for WebSphere 9. Here is the summary of the PR [1]: > \#### Short description of what this resolves: > Hi, guys, > my name is Marian Macik and I work at Red Hat as QE Engineer on [jBPM|https://github.com/kiegroup/jbpm] project. This PR introduces Arquillian container adapter for WebSphere 9. We have been using it at Red Hat in our QE automation for about two months without any issues. It is copied from adapter for WebSphere 8.5 (as WebSphere 8.5 was copied from WebSphere 8). There were only some minor changes when it comes to system paths pointing at WebSphere dependencies (jgss-provider and ws-admin-client). > However, since WebSphere 9, wsadmin is using jython27 by default. Jython21 is still supported and to use jython21, 'com.ibm.ws.admin.client.forJython21_9.0.jar' should be used. Moreover, the new wsadmin jar has additional libraries which are not used by Arquillian (such as Python JSR 223 implementation) and might cause issues when deploying and running tests. If this happens, simply override this property with jython21 jar: > {code} > -Dws_admin_client_jar_name=com.ibm.ws.admin.client.forJython21_9.0.jar > {code} > I added this property because the new jython27 wsadmin implementation was causing issues since it loaded unwanted classes on the classpath. Of course, by default the new jython27 wsadmin is used, override is optional. > I have also run the enclosed tests with my own arquillian.xml and they have passed. > Thanks, > Marian > [1] https://github.com/arquillian/arquillian-container-was/pull/29 -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 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 2018