From issues at jboss.org  Sun Apr 10 02:19:00 2016
From: issues at jboss.org (Claude Libois (JIRA))
Date: Sun, 10 Apr 2016 02:19:00 -0400 (EDT)
Subject: [arquillian-issues] [JBoss JIRA] (ARQ-2004)
 arquillian-wls-embedded-12.1 doesn't support Ear deployment
In-Reply-To: <JIRA.12596570.1450098858000@Atlassian.JIRA>
References: <JIRA.12596570.1450098858000@Atlassian.JIRA>
	<JIRA.12596570.1450098858000@jira.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12596570.1450098858000.118.1460269140121@Atlassian.JIRA>


    [ https://issues.jboss.org/browse/ARQ-2004?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13189427#comment-13189427 ] 

Claude Libois commented on ARQ-2004:
------------------------------------

This "bug" has been pushed 4 month ago but still no update. I just would like to know if it's a bug  something that won't be fix whatever the reason...


> arquillian-wls-embedded-12.1 doesn't support Ear deployment
> -----------------------------------------------------------
>
>                 Key: ARQ-2004
>                 URL: https://issues.jboss.org/browse/ARQ-2004
>             Project: Arquillian
>          Issue Type: Bug
>          Components: WebLogic Containers
>    Affects Versions: 1.0.1.Final
>         Environment: Test done on Linux with java 7u79 through intelliJ test.
>            Reporter: Claude Libois
>            Assignee: Vineet Reynolds
>
> For weblogic, I need to deploy a ear to embed datasource definition. However when creating a ear archive I get a "Could not determine the module name for <ear name>". By digging in the code I have noticed that the ear is deployed as an EJB. Maybe that it's a limitation of the embeddable API but it wasn't clear if embedded container support ear deployment or not:
> {code:java}
> @Deployment
> public static Archive<?> createDeploymentPackage() {
>         EnterpriseArchive ea=ShrinkWrap.create(org.jboss.shrinkwrap.api.spec.EnterpriseArchive.class, "m.ear").
>                 addAsManifestResource(new FileAsset(new File("META-INF/weblogic-application.xml")), "weblogic-application.xml").
>                 setApplicationXML("META-INF/application.xml").
>                 addAsResource(new FileAsset(new File("datasources/minfin.ccff.fwk.core.db.SharedDataSource-jdbc.xml")), "datasources/minfin.ccff.fwk.core.db.SharedDataSource-jdbc.xml").
>                 addAsResource(new FileAsset(new File("datasources/minfin.ccff.fwk.core.db.SharedDataSourceTx-jdbc.xml")), "datasources/minfin.ccff.fwk.core.db.SharedDataSourceTx-jdbc.xml");
>         JavaArchive jar= ShrinkWrap.create(JavaArchive.class,"idgeneratorTest.jar")
>                 .addClass(IDDAO.class)
>                 .addClass(IDDAOTestEJB.class).
>                         addAsManifestResource(new FileAsset(new File("META-INF/ejb-jar.xml")), "ejb-jar.xml");
>         ea.addAsModule(jar);
>         return ea;
>     }
> {code}



--
This message was sent by Atlassian JIRA
(v6.4.11#64026)

From issues at jboss.org  Sun Apr 10 02:20:00 2016
From: issues at jboss.org (Claude Libois (JIRA))
Date: Sun, 10 Apr 2016 02:20:00 -0400 (EDT)
Subject: [arquillian-issues] [JBoss JIRA] (ARQ-2004)
 arquillian-wls-embedded-12.1 doesn't support Ear deployment
In-Reply-To: <JIRA.12596570.1450098858000@Atlassian.JIRA>
References: <JIRA.12596570.1450098858000@Atlassian.JIRA>
	<JIRA.12596570.1450098858000@jira.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12596570.1450098858000.121.1460269200186@Atlassian.JIRA>


    [ https://issues.jboss.org/browse/ARQ-2004?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13189427#comment-13189427 ] 

Claude Libois edited comment on ARQ-2004 at 4/10/16 2:19 AM:
-------------------------------------------------------------

This "bug" has been pushed 4 month ago but still no update. I just would like to know if it's a bug  or something that won't be fix whatever the reason...



was (Author: clibois.work):
This "bug" has been pushed 4 month ago but still no update. I just would like to know if it's a bug  something that won't be fix whatever the reason...


> arquillian-wls-embedded-12.1 doesn't support Ear deployment
> -----------------------------------------------------------
>
>                 Key: ARQ-2004
>                 URL: https://issues.jboss.org/browse/ARQ-2004
>             Project: Arquillian
>          Issue Type: Bug
>          Components: WebLogic Containers
>    Affects Versions: 1.0.1.Final
>         Environment: Test done on Linux with java 7u79 through intelliJ test.
>            Reporter: Claude Libois
>            Assignee: Vineet Reynolds
>
> For weblogic, I need to deploy a ear to embed datasource definition. However when creating a ear archive I get a "Could not determine the module name for <ear name>". By digging in the code I have noticed that the ear is deployed as an EJB. Maybe that it's a limitation of the embeddable API but it wasn't clear if embedded container support ear deployment or not:
> {code:java}
> @Deployment
> public static Archive<?> createDeploymentPackage() {
>         EnterpriseArchive ea=ShrinkWrap.create(org.jboss.shrinkwrap.api.spec.EnterpriseArchive.class, "m.ear").
>                 addAsManifestResource(new FileAsset(new File("META-INF/weblogic-application.xml")), "weblogic-application.xml").
>                 setApplicationXML("META-INF/application.xml").
>                 addAsResource(new FileAsset(new File("datasources/minfin.ccff.fwk.core.db.SharedDataSource-jdbc.xml")), "datasources/minfin.ccff.fwk.core.db.SharedDataSource-jdbc.xml").
>                 addAsResource(new FileAsset(new File("datasources/minfin.ccff.fwk.core.db.SharedDataSourceTx-jdbc.xml")), "datasources/minfin.ccff.fwk.core.db.SharedDataSourceTx-jdbc.xml");
>         JavaArchive jar= ShrinkWrap.create(JavaArchive.class,"idgeneratorTest.jar")
>                 .addClass(IDDAO.class)
>                 .addClass(IDDAOTestEJB.class).
>                         addAsManifestResource(new FileAsset(new File("META-INF/ejb-jar.xml")), "ejb-jar.xml");
>         ea.addAsModule(jar);
>         return ea;
>     }
> {code}



--
This message was sent by Atlassian JIRA
(v6.4.11#64026)

From issues at jboss.org  Tue Apr 12 06:40:01 2016
From: issues at jboss.org (Matous Jobanek (JIRA))
Date: Tue, 12 Apr 2016 06:40:01 -0400 (EDT)
Subject: [arquillian-issues] [JBoss JIRA] (ARQGRA-487) Update Arquillian
	Drone to 2.0.0.Final
In-Reply-To: <JIRA.12614545.1460457594000@Atlassian.JIRA>
References: <JIRA.12614545.1460457594000@Atlassian.JIRA>
	<JIRA.12614545.1460457594718@jira.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12614545.1460457594000.9127.1460457601139@Atlassian.JIRA>

Matous Jobanek created ARQGRA-487:
-------------------------------------

             Summary: Update Arquillian Drone to 2.0.0.Final
                 Key: ARQGRA-487
                 URL: https://issues.jboss.org/browse/ARQGRA-487
             Project: Arquillian Graphene
          Issue Type: Component  Upgrade
    Affects Versions: 2.1.0.Beta1
            Reporter: Matous Jobanek
            Assignee: Matous Jobanek
             Fix For: 2.1.0.CR1






--
This message was sent by Atlassian JIRA
(v6.4.11#64026)

From issues at jboss.org  Tue Apr 12 06:52:00 2016
From: issues at jboss.org (Matous Jobanek (JIRA))
Date: Tue, 12 Apr 2016 06:52:00 -0400 (EDT)
Subject: [arquillian-issues] [JBoss JIRA] (ARQGRA-487) Update Arquillian
	Drone to 2.0.0.Final
In-Reply-To: <JIRA.12614545.1460457595000@Atlassian.JIRA>
References: <JIRA.12614545.1460457595000@Atlassian.JIRA>
	<JIRA.12614545.1460457595000@jira.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12614545.1460457595000.9260.1460458320268@Atlassian.JIRA>


     [ https://issues.jboss.org/browse/ARQGRA-487?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Matous Jobanek resolved ARQGRA-487.
-----------------------------------
    Resolution: Done


Pushed upstream in https://github.com/arquillian/arquillian-graphene/commit/041b17f2e46ca504fc88797aa95427743bf659c3

> Update Arquillian Drone to 2.0.0.Final
> --------------------------------------
>
>                 Key: ARQGRA-487
>                 URL: https://issues.jboss.org/browse/ARQGRA-487
>             Project: Arquillian Graphene
>          Issue Type: Component  Upgrade
>    Affects Versions: 2.1.0.Beta1
>            Reporter: Matous Jobanek
>            Assignee: Matous Jobanek
>             Fix For: 2.1.0.CR1
>
>




--
This message was sent by Atlassian JIRA
(v6.4.11#64026)

From issues at jboss.org  Tue Apr 12 06:52:00 2016
From: issues at jboss.org (Matous Jobanek (JIRA))
Date: Tue, 12 Apr 2016 06:52:00 -0400 (EDT)
Subject: [arquillian-issues] [JBoss JIRA] (ARQGRA-487) Update Arquillian
	Drone to 2.0.0.Final
In-Reply-To: <JIRA.12614545.1460457595000@Atlassian.JIRA>
References: <JIRA.12614545.1460457595000@Atlassian.JIRA>
	<JIRA.12614545.1460457595000@jira.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12614545.1460457595000.9263.1460458320354@Atlassian.JIRA>


     [ https://issues.jboss.org/browse/ARQGRA-487?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Matous Jobanek closed ARQGRA-487.
---------------------------------


> Update Arquillian Drone to 2.0.0.Final
> --------------------------------------
>
>                 Key: ARQGRA-487
>                 URL: https://issues.jboss.org/browse/ARQGRA-487
>             Project: Arquillian Graphene
>          Issue Type: Component  Upgrade
>    Affects Versions: 2.1.0.Beta1
>            Reporter: Matous Jobanek
>            Assignee: Matous Jobanek
>             Fix For: 2.1.0.CR1
>
>




--
This message was sent by Atlassian JIRA
(v6.4.11#64026)

From issues at jboss.org  Wed Apr 13 10:14:00 2016
From: issues at jboss.org (Matous Jobanek (JIRA))
Date: Wed, 13 Apr 2016 10:14:00 -0400 (EDT)
Subject: [arquillian-issues] [JBoss JIRA] (ARQ-2012) Warnings when test runs
 as client without @RunAsClient
In-Reply-To: <JIRA.12603912.1455545786000@Atlassian.JIRA>
References: <JIRA.12603912.1455545786000@Atlassian.JIRA>
	<JIRA.12603912.1455545786000@jira.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12603912.1455545786000.16828.1460556840611@Atlassian.JIRA>


     [ https://issues.jboss.org/browse/ARQ-2012?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Matous Jobanek updated ARQ-2012:
--------------------------------
    Git Pull Request: https://github.com/arquillian/arquillian-core/pull/106


> Warnings when test runs as client without @RunAsClient
> ------------------------------------------------------
>
>                 Key: ARQ-2012
>                 URL: https://issues.jboss.org/browse/ARQ-2012
>             Project: Arquillian
>          Issue Type: Bug
>          Components: Deployable Containers SPI
>    Affects Versions: 1.1.11.Final
>            Reporter: Ladislav Thon
>
> When I moved to Arquillian 1.1.11.Final, I started getting warnings when my tests run as client but don't use the {{@RunAsClient}} annotation. The cause is ARQ-1937.
> I'll just reiterate that I actually never ever use the {{@RunAsClient}} annotation because it's superfluous. I simply set my {{@Deployment}} to {{testable = false}} or I have no {{@Deployment}} at all. I do that intentionally and I _expect_ that the test will run as client, so the warning doesn't make much sense for me.



--
This message was sent by Atlassian JIRA
(v6.4.11#64026)

From issues at jboss.org  Wed Apr 13 10:14:00 2016
From: issues at jboss.org (Matous Jobanek (JIRA))
Date: Wed, 13 Apr 2016 10:14:00 -0400 (EDT)
Subject: [arquillian-issues] [JBoss JIRA] (ARQ-2012) Warnings when test runs
 as client without @RunAsClient
In-Reply-To: <JIRA.12603912.1455545786000@Atlassian.JIRA>
References: <JIRA.12603912.1455545786000@Atlassian.JIRA>
	<JIRA.12603912.1455545786000@jira.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12603912.1455545786000.16831.1460556840734@Atlassian.JIRA>


     [ https://issues.jboss.org/browse/ARQ-2012?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Matous Jobanek reassigned ARQ-2012:
-----------------------------------

    Assignee: Matous Jobanek


> Warnings when test runs as client without @RunAsClient
> ------------------------------------------------------
>
>                 Key: ARQ-2012
>                 URL: https://issues.jboss.org/browse/ARQ-2012
>             Project: Arquillian
>          Issue Type: Bug
>          Components: Deployable Containers SPI
>    Affects Versions: 1.1.11.Final
>            Reporter: Ladislav Thon
>            Assignee: Matous Jobanek
>
> When I moved to Arquillian 1.1.11.Final, I started getting warnings when my tests run as client but don't use the {{@RunAsClient}} annotation. The cause is ARQ-1937.
> I'll just reiterate that I actually never ever use the {{@RunAsClient}} annotation because it's superfluous. I simply set my {{@Deployment}} to {{testable = false}} or I have no {{@Deployment}} at all. I do that intentionally and I _expect_ that the test will run as client, so the warning doesn't make much sense for me.



--
This message was sent by Atlassian JIRA
(v6.4.11#64026)

From issues at jboss.org  Fri Apr 15 04:29:00 2016
From: issues at jboss.org (Christian Schulz (JIRA))
Date: Fri, 15 Apr 2016 04:29:00 -0400 (EDT)
Subject: [arquillian-issues] [JBoss JIRA] (ARQ-2026) Client activity
 failures should have more priority over server activities
In-Reply-To: <JIRA.12615254.1460708881000@Atlassian.JIRA>
References: <JIRA.12615254.1460708881000@Atlassian.JIRA>
	<JIRA.12615254.1460708881791@jira.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12615254.1460708881000.25285.1460708940388@Atlassian.JIRA>

Christian Schulz created ARQ-2026:
-------------------------------------

             Summary: Client activity failures should have more priority over server activities
                 Key: ARQ-2026
                 URL: https://issues.jboss.org/browse/ARQ-2026
             Project: Arquillian
          Issue Type: Enhancement
          Components: Extension - Warp
    Affects Versions: warp_1.0.0.Alpha7
            Reporter: Christian Schulz


I have noticed multiple times that my warp tests are failing caused by ServerWarpExecutionException.

In my research I found out that the DefaultWarpExecutor prefers to show server activity failures over client activity failures.

In my opinion client failures should be handled with higher priority, because in most cases the failing client activities is the reason for the server activity failure f.e. with asserts.

I would suggest to ignore AssertionErrors from server activities if there is a catched client exception.



--
This message was sent by Atlassian JIRA
(v6.4.11#64026)

From issues at jboss.org  Sun Apr 17 14:39:00 2016
From: issues at jboss.org (Bartosz Majsak (JIRA))
Date: Sun, 17 Apr 2016 14:39:00 -0400 (EDT)
Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1815) Unable to locate Oracle
	Sequence filter
In-Reply-To: <JIRA.12546090.1405006378000@Atlassian.JIRA>
References: <JIRA.12546090.1405006378000@Atlassian.JIRA>
	<JIRA.12546090.1405006378000@jira.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12546090.1405006378000.29712.1460918340392@Atlassian.JIRA>


     [ https://issues.jboss.org/browse/ARQ-1815?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Work on ARQ-1815 started by Bartosz Majsak.
-------------------------------------------
> Unable to locate Oracle Sequence filter
> ---------------------------------------
>
>                 Key: ARQ-1815
>                 URL: https://issues.jboss.org/browse/ARQ-1815
>             Project: Arquillian
>          Issue Type: Bug
>          Components: Extension - Persistence
>    Affects Versions: persistence_1.0.0.Alpha7
>            Reporter: Bartosz Majsak
>            Assignee: Bartosz Majsak
>            Priority: Blocker
>             Fix For: persistence_1.0.0.next
>
>
> When trying to define custom table filter using
> {{<property name=?customTableFilter?>org.jboss.arquillian.persistence.dbunit.filter.OracleDatabaseSequenceFilterProvider</property>}}
> It's resulting in
> {{Unable to find sequence filter for org.jboss.arquillian.persistence.dbunit.filter.OracleDatabaseSequenceFilterProvider. Using default database sequence filter.}}



--
This message was sent by Atlassian JIRA
(v6.4.11#64026)


From issues at jboss.org  Sun Apr 17 16:49:00 2016
From: issues at jboss.org (Bartosz Majsak (JIRA))
Date: Sun, 17 Apr 2016 16:49:00 -0400 (EDT)
Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1815) Unable to locate Oracle
	Sequence filter
In-Reply-To: <JIRA.12546090.1405006378000@Atlassian.JIRA>
References: <JIRA.12546090.1405006378000@Atlassian.JIRA>
	<JIRA.12546090.1405006378000@jira.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12546090.1405006378000.29730.1460926140291@Atlassian.JIRA>


    [ https://issues.jboss.org/browse/ARQ-1815?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13192808#comment-13192808 ] 

Bartosz Majsak commented on ARQ-1815:
-------------------------------------

Pushed upstream [@a91091|https://github.com/arquillian/arquillian-extension-persistence/commit/a91091d26fe9adba31b7edd300e8412b99e01476].

> Unable to locate Oracle Sequence filter
> ---------------------------------------
>
>                 Key: ARQ-1815
>                 URL: https://issues.jboss.org/browse/ARQ-1815
>             Project: Arquillian
>          Issue Type: Bug
>          Components: Extension - Persistence
>    Affects Versions: persistence_1.0.0.Alpha7
>            Reporter: Bartosz Majsak
>            Assignee: Bartosz Majsak
>            Priority: Blocker
>             Fix For: persistence_1.0.0.next
>
>
> When trying to define custom table filter using
> {{<property name=?customTableFilter?>org.jboss.arquillian.persistence.dbunit.filter.OracleDatabaseSequenceFilterProvider</property>}}
> It's resulting in
> {{Unable to find sequence filter for org.jboss.arquillian.persistence.dbunit.filter.OracleDatabaseSequenceFilterProvider. Using default database sequence filter.}}



--
This message was sent by Atlassian JIRA
(v6.4.11#64026)


From issues at jboss.org  Sun Apr 17 16:49:00 2016
From: issues at jboss.org (Bartosz Majsak (JIRA))
Date: Sun, 17 Apr 2016 16:49:00 -0400 (EDT)
Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1815) Unable to locate Oracle
	Sequence filter
In-Reply-To: <JIRA.12546090.1405006378000@Atlassian.JIRA>
References: <JIRA.12546090.1405006378000@Atlassian.JIRA>
	<JIRA.12546090.1405006378000@jira.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12546090.1405006378000.29734.1460926140503@Atlassian.JIRA>


     [ https://issues.jboss.org/browse/ARQ-1815?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Bartosz Majsak resolved ARQ-1815.
---------------------------------
    Resolution: Done


> Unable to locate Oracle Sequence filter
> ---------------------------------------
>
>                 Key: ARQ-1815
>                 URL: https://issues.jboss.org/browse/ARQ-1815
>             Project: Arquillian
>          Issue Type: Bug
>          Components: Extension - Persistence
>    Affects Versions: persistence_1.0.0.Alpha7
>            Reporter: Bartosz Majsak
>            Assignee: Bartosz Majsak
>            Priority: Blocker
>             Fix For: persistence_1.0.0.next
>
>
> When trying to define custom table filter using
> {{<property name=?customTableFilter?>org.jboss.arquillian.persistence.dbunit.filter.OracleDatabaseSequenceFilterProvider</property>}}
> It's resulting in
> {{Unable to find sequence filter for org.jboss.arquillian.persistence.dbunit.filter.OracleDatabaseSequenceFilterProvider. Using default database sequence filter.}}



--
This message was sent by Atlassian JIRA
(v6.4.11#64026)


From issues at jboss.org  Sun Apr 17 16:53:00 2016
From: issues at jboss.org (Bartosz Majsak (JIRA))
Date: Sun, 17 Apr 2016 16:53:00 -0400 (EDT)
Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1817) Ad-hoc H2 java
 functions are treated as comments
In-Reply-To: <JIRA.12546196.1405088441000@Atlassian.JIRA>
References: <JIRA.12546196.1405088441000@Atlassian.JIRA>
	<JIRA.12546196.1405088441000@jira.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12546196.1405088441000.29738.1460926380215@Atlassian.JIRA>


     [ https://issues.jboss.org/browse/ARQ-1817?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Work on ARQ-1817 started by Bartosz Majsak.
-------------------------------------------
> Ad-hoc H2 java functions are treated as comments
> ------------------------------------------------
>
>                 Key: ARQ-1817
>                 URL: https://issues.jboss.org/browse/ARQ-1817
>             Project: Arquillian
>          Issue Type: Bug
>          Components: Extension - Persistence
>    Affects Versions: persistence_1.0.0.Alpha7
>            Reporter: Bartosz Majsak
>            Assignee: Bartosz Majsak
>             Fix For: persistence_1.0.0.next
>
>




--
This message was sent by Atlassian JIRA
(v6.4.11#64026)

From issues at jboss.org  Sun Apr 17 17:59:00 2016
From: issues at jboss.org (Bartosz Majsak (JIRA))
Date: Sun, 17 Apr 2016 17:59:00 -0400 (EDT)
Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1779) Tests are not executed
 using combinations of @ApplyScriptBefore / @ApplyScriptAfter
In-Reply-To: <JIRA.12541085.1400491949000@Atlassian.JIRA>
References: <JIRA.12541085.1400491949000@Atlassian.JIRA>
	<JIRA.12541085.1400491949000@jira.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12541085.1400491949000.29748.1460930340292@Atlassian.JIRA>


     [ https://issues.jboss.org/browse/ARQ-1779?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Bartosz Majsak closed ARQ-1779.
-------------------------------
    Resolution: Duplicate Issue


> Tests are not executed using combinations of @ApplyScriptBefore / @ApplyScriptAfter
> -----------------------------------------------------------------------------------
>
>                 Key: ARQ-1779
>                 URL: https://issues.jboss.org/browse/ARQ-1779
>             Project: Arquillian
>          Issue Type: Bug
>          Components: Extension - Persistence
>    Affects Versions: persistence_1.0.0.Alpha7
>            Reporter: Thomas K?stermann
>            Assignee: Bartosz Majsak
>             Fix For: persistence_1.0.0.next
>
>
> Forum reference: https://community.jboss.org/message/874117
> The following test case succeeds (green bar) although it should fail:
> {code:java}
> @RunWith(Arquillian.class)  
> @DataSource("java:oracleDS")  
> @Cleanup(phase=TestExecutionPhase.NONE)  
> @ApplyScriptBefore("deploy-db-functionality.sql")  
> @ApplyScriptAfter("undeploy-db-functionality.sql")  
> public class PersistenceIT {  
>    // @Deployment ...  
>   
>    @Test  
>    @ApplyScriptBefore("trigger-db-functionality.sql")  
>    public void shouldFail() {  
>        Assert.fail("should fail, but doesn't");  
>    }  
> }
> {code}
> Removing class level annotations does not work either:
> {code:java}
> @Test  
> @ApplyScriptBefore({ "deploy-db-functionality.sql", "trigger-db-functionality.sql" })  
> @ApplyScriptAfter("undeploy-db-functionality.sql")  
> public void shouldFail() { ... }  
> {code}
> What actually works is to use only one ApplyScriptBefore / ApplyScriptAfter annotation per test, each with only one script to execute.



--
This message was sent by Atlassian JIRA
(v6.4.11#64026)


From issues at jboss.org  Tue Apr 19 05:05:00 2016
From: issues at jboss.org (Michael Kotten (JIRA))
Date: Tue, 19 Apr 2016 05:05:00 -0400 (EDT)
Subject: [arquillian-issues] [JBoss JIRA] (ARQGRA-467) Screenshooter: Tests
 fail when no Drone contexts exist
In-Reply-To: <JIRA.12561773.1422369207000@Atlassian.JIRA>
References: <JIRA.12561773.1422369207000@Atlassian.JIRA>
	<JIRA.12561773.1422369207000@jira.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12561773.1422369207000.36283.1461056700226@Atlassian.JIRA>


    [ https://issues.jboss.org/browse/ARQGRA-467?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13193546#comment-13193546 ] 

Michael Kotten commented on ARQGRA-467:
---------------------------------------

I'm using version 2.1.0.CR1 and for me the error isn't gone. I have a project that contains Done/Graphene/Warp tests and ordinary in-container tests with Arquillian. For the in-container tests, the error occurs.

The new code 
{code:java}
try {
  context = GrapheneContext.getContextFor(Default.class);
} catch (IllegalStateException ex) {
  return null;
}
{code}
never returns null for me.

This is what i use in my pom.xml.

{code:xml}
         <dependency>
            <groupId>org.jboss.arquillian.graphene</groupId>
            <artifactId>arquillian-browser-screenshooter</artifactId>
            <version>${graphene.version}</version>
            <scope>test</scope>
         </dependency>
         <dependency>
            <groupId>org.jboss.arquillian.extension</groupId>
            <artifactId>arquillian-phantom-driver</artifactId>
            <version>1.2.1.Final</version>
         </dependency>
         <dependency>
            <groupId>org.jboss.arquillian.graphene</groupId>
            <artifactId>graphene-webdriver</artifactId>
            <version>${graphene.version}</version>
            <type>pom</type>
            <scope>test</scope>
         </dependency>
{code}

> Screenshooter: Tests fail when no Drone contexts exist
> ------------------------------------------------------
>
>                 Key: ARQGRA-467
>                 URL: https://issues.jboss.org/browse/ARQGRA-467
>             Project: Arquillian Graphene
>          Issue Type: Bug
>          Components: screenshooter
>    Affects Versions: 2.1.0.Alpha1
>            Reporter: Luk?? Fry?
>            Assignee: Stefan Miklosovic
>             Fix For: 2.1.0.Alpha2
>
>
> https://github.com/arquillian/arquillian-recorder/issues/10



--
This message was sent by Atlassian JIRA
(v6.4.11#64026)


From issues at jboss.org  Tue Apr 19 05:06:00 2016
From: issues at jboss.org (=?UTF-8?Q?Luk=C3=A1=C5=A1_Fry=C4=8D_=28JIRA=29?=)
Date: Tue, 19 Apr 2016 05:06:00 -0400 (EDT)
Subject: [arquillian-issues] [JBoss JIRA] (ARQGRA-467) Screenshooter: Tests
 fail when no Drone contexts exist
In-Reply-To: <JIRA.12561773.1422369207000@Atlassian.JIRA>
References: <JIRA.12561773.1422369207000@Atlassian.JIRA>
	<JIRA.12561773.1422369207000@jira.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12561773.1422369207000.36292.1461056760497@Atlassian.JIRA>


    [ https://issues.jboss.org/browse/ARQGRA-467?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13193548#comment-13193548 ] 

Luk?? Fry? commented on ARQGRA-467:
-----------------------------------

Bonjour,

En l'absence de votre correspondant, merci d'adresser votre email ?? jbalunas at redhat.com

Bien cordialement.
-- 

Dear Sender,

In the absence of your contact, please send your email to jbalunas at redhat.com

Many thanks.
-- 

Lieber Absender,

In Abwesenheit Ihrers Kontaktes senden Sie Ihre E-Mail bitte an jbalunas at redhat.com

Vielen Dank. 


> Screenshooter: Tests fail when no Drone contexts exist
> ------------------------------------------------------
>
>                 Key: ARQGRA-467
>                 URL: https://issues.jboss.org/browse/ARQGRA-467
>             Project: Arquillian Graphene
>          Issue Type: Bug
>          Components: screenshooter
>    Affects Versions: 2.1.0.Alpha1
>            Reporter: Luk?? Fry?
>            Assignee: Stefan Miklosovic
>             Fix For: 2.1.0.Alpha2
>
>
> https://github.com/arquillian/arquillian-recorder/issues/10



--
This message was sent by Atlassian JIRA
(v6.4.11#64026)


From issues at jboss.org  Thu Apr 21 17:25:01 2016
From: issues at jboss.org (Chris Dollar (JIRA))
Date: Thu, 21 Apr 2016 17:25:01 -0400 (EDT)
Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1282) TestNG @DataProvider is
 fully invoked for each record
In-Reply-To: <JIRA.12483918.1359633652000@Atlassian.JIRA>
References: <JIRA.12483918.1359633652000@Atlassian.JIRA>
	<JIRA.12483918.1359633652000@jira.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12483918.1359633652000.54156.1461273901011@Atlassian.JIRA>


    [ https://issues.jboss.org/browse/ARQ-1282?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13195483#comment-13195483 ] 

Chris Dollar commented on ARQ-1282:
-----------------------------------

I'm using arquillian 1.1.11.Final and the attached workaround isn't working for me. I only get the first element from the data provider and the rest are skipped. Trying to use a @DataProvider normally (without the _provide_ hack) results in the same squared behavior of executions.

Does anyone have any other workarounds? Or maybe a clue as what to look at in the arquillian source that might be causing the issue?

> TestNG @DataProvider is fully invoked for each record
> -----------------------------------------------------
>
>                 Key: ARQ-1282
>                 URL: https://issues.jboss.org/browse/ARQ-1282
>             Project: Arquillian
>          Issue Type: Bug
>          Components: JBoss AS Containers
>    Affects Versions: 1.0.3.Final
>            Reporter: Karel Cemus
>         Attachments: ArquillianDataProvider.java, FlightServiceTest.java
>
>
> h2. Expected behavior
> TestNG defines @DataProvider annotation to allow single method to perform multiple test cases. Provider method annotated with @DataProvider returns an array of arrays, each containing one test case. These parameters are given to the target method as input parameters. By the definition, the total count of performed test by single method is equal to number of test cases in related data provider.
> h2. Actual behavior
> Using TestNG under Arquillian framework makes this functionality buggy. Although the client (maven, IDE, etc.) thinks, that the total number of invoked test is correct, it is not. When we take a look into server's log, we can see that for each single test case it invoked full set of all test cases. It means, that in the end the amount of performed tests is equal to expected count squared. Such behaviour is not only slow but also in some cases it doesn't work and it makes tests to fail.
> h2. Example
> {code:java}
> @DataProvider
> public Object[][] sumProvider() {
>     return new Object[][]{
>         new Object[]{ 0, 0, 0 },
>         new Object[]{ 1, 1, 2 },
>         new Object[]{ 1, 5, 6 },
>         new Object[]{ 5, 1, 6 }
>     };
> }
> {code}
> h3. Expected output in server log
> {quote}
> Execution of sum: 0 + 0 = 0
> Execution of sum: 1 + 1 = 2
> Execution of sum: 1 + 5 = 6
> Execution of sum: 5 + 1 = 6
> {quote}
> h3. Actual output
> {quote}
> Execution of sum: 0 + 0 = 0
> Execution of sum: 1 + 1 = 2
> Execution of sum: 1 + 5 = 6
> Execution of sum: 5 + 1 = 6
> Execution of sum: 0 + 0 = 0
> Execution of sum: 1 + 1 = 2
> Execution of sum: 1 + 5 = 6
> Execution of sum: 5 + 1 = 6
> Execution of sum: 0 + 0 = 0
> Execution of sum: 1 + 1 = 2
> Execution of sum: 1 + 5 = 6
> Execution of sum: 5 + 1 = 6
> Execution of sum: 0 + 0 = 0
> Execution of sum: 1 + 1 = 2
> Execution of sum: 1 + 5 = 6
> Execution of sum: 5 + 1 = 6
> {quote}



--
This message was sent by Atlassian JIRA
(v6.4.11#64026)

From issues at jboss.org  Sun Apr 24 06:10:00 2016
From: issues at jboss.org (Bartosz Majsak (JIRA))
Date: Sun, 24 Apr 2016 06:10:00 -0400 (EDT)
Subject: [arquillian-issues] [JBoss JIRA] (ARQ-808) Apply the formatter for
 the GlassFish container adapters
In-Reply-To: <JIRA.12461360.1331550525000@Atlassian.JIRA>
References: <JIRA.12461360.1331550525000@Atlassian.JIRA>
	<JIRA.12461360.1331550525000@jira.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12461360.1331550525000.59458.1461492600333@Atlassian.JIRA>


     [ https://issues.jboss.org/browse/ARQ-808?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Bartosz Majsak reassigned ARQ-808:
----------------------------------

    Assignee: Bartosz Majsak  (was: Vineet Reynolds)


> Apply the formatter for the GlassFish container adapters
> --------------------------------------------------------
>
>                 Key: ARQ-808
>                 URL: https://issues.jboss.org/browse/ARQ-808
>             Project: Arquillian
>          Issue Type: Task
>          Components: GlassFish Containers
>            Reporter: Vineet Reynolds
>            Assignee: Bartosz Majsak
>            Priority: Minor
>             Fix For: glassfish_1.0.0.Final
>
>
> The formatting in the classes of the GlassFish adapters vary from class to class, and sometimes even across lines. We'll need to use a consistent code formatting scheme for this Maven project.



--
This message was sent by Atlassian JIRA
(v6.4.11#64026)

From issues at jboss.org  Sun Apr 24 06:22:00 2016
From: issues at jboss.org (Bartosz Majsak (JIRA))
Date: Sun, 24 Apr 2016 06:22:00 -0400 (EDT)
Subject: [arquillian-issues] [JBoss JIRA] (ARQ-808) Apply the formatter for
 the GlassFish container adapters
In-Reply-To: <JIRA.12461360.1331550525000@Atlassian.JIRA>
References: <JIRA.12461360.1331550525000@Atlassian.JIRA>
	<JIRA.12461360.1331550525000@jira.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12461360.1331550525000.59464.1461493320470@Atlassian.JIRA>


     [ https://issues.jboss.org/browse/ARQ-808?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Bartosz Majsak resolved ARQ-808.
--------------------------------
    Resolution: Done


Pushed upstream [@bbeb0a89|https://github.com/arquillian/arquillian-container-glassfish/commit/bbeb0a89a4af3b7d8a1b15530090b3566dcaff44].

> Apply the formatter for the GlassFish container adapters
> --------------------------------------------------------
>
>                 Key: ARQ-808
>                 URL: https://issues.jboss.org/browse/ARQ-808
>             Project: Arquillian
>          Issue Type: Task
>          Components: GlassFish Containers
>            Reporter: Vineet Reynolds
>            Assignee: Bartosz Majsak
>            Priority: Minor
>             Fix For: glassfish_1.0.0.Final
>
>
> The formatting in the classes of the GlassFish adapters vary from class to class, and sometimes even across lines. We'll need to use a consistent code formatting scheme for this Maven project.



--
This message was sent by Atlassian JIRA
(v6.4.11#64026)

From issues at jboss.org  Sun Apr 24 06:23:00 2016
From: issues at jboss.org (Bartosz Majsak (JIRA))
Date: Sun, 24 Apr 2016 06:23:00 -0400 (EDT)
Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1282) TestNG @DataProvider is
 fully invoked for each record
In-Reply-To: <JIRA.12483918.1359633652000@Atlassian.JIRA>
References: <JIRA.12483918.1359633652000@Atlassian.JIRA>
	<JIRA.12483918.1359633652000@jira.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12483918.1359633652000.59477.1461493380654@Atlassian.JIRA>


    [ https://issues.jboss.org/browse/ARQ-1282?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13196120#comment-13196120 ] 

Bartosz Majsak commented on ARQ-1282:
-------------------------------------

This issue affects pretty much any other data-driven tests, for example Spock test runner. I'm looking at it.

> TestNG @DataProvider is fully invoked for each record
> -----------------------------------------------------
>
>                 Key: ARQ-1282
>                 URL: https://issues.jboss.org/browse/ARQ-1282
>             Project: Arquillian
>          Issue Type: Bug
>          Components: JBoss AS Containers
>    Affects Versions: 1.0.3.Final
>            Reporter: Karel Cemus
>         Attachments: ArquillianDataProvider.java, FlightServiceTest.java
>
>
> h2. Expected behavior
> TestNG defines @DataProvider annotation to allow single method to perform multiple test cases. Provider method annotated with @DataProvider returns an array of arrays, each containing one test case. These parameters are given to the target method as input parameters. By the definition, the total count of performed test by single method is equal to number of test cases in related data provider.
> h2. Actual behavior
> Using TestNG under Arquillian framework makes this functionality buggy. Although the client (maven, IDE, etc.) thinks, that the total number of invoked test is correct, it is not. When we take a look into server's log, we can see that for each single test case it invoked full set of all test cases. It means, that in the end the amount of performed tests is equal to expected count squared. Such behaviour is not only slow but also in some cases it doesn't work and it makes tests to fail.
> h2. Example
> {code:java}
> @DataProvider
> public Object[][] sumProvider() {
>     return new Object[][]{
>         new Object[]{ 0, 0, 0 },
>         new Object[]{ 1, 1, 2 },
>         new Object[]{ 1, 5, 6 },
>         new Object[]{ 5, 1, 6 }
>     };
> }
> {code}
> h3. Expected output in server log
> {quote}
> Execution of sum: 0 + 0 = 0
> Execution of sum: 1 + 1 = 2
> Execution of sum: 1 + 5 = 6
> Execution of sum: 5 + 1 = 6
> {quote}
> h3. Actual output
> {quote}
> Execution of sum: 0 + 0 = 0
> Execution of sum: 1 + 1 = 2
> Execution of sum: 1 + 5 = 6
> Execution of sum: 5 + 1 = 6
> Execution of sum: 0 + 0 = 0
> Execution of sum: 1 + 1 = 2
> Execution of sum: 1 + 5 = 6
> Execution of sum: 5 + 1 = 6
> Execution of sum: 0 + 0 = 0
> Execution of sum: 1 + 1 = 2
> Execution of sum: 1 + 5 = 6
> Execution of sum: 5 + 1 = 6
> Execution of sum: 0 + 0 = 0
> Execution of sum: 1 + 1 = 2
> Execution of sum: 1 + 5 = 6
> Execution of sum: 5 + 1 = 6
> {quote}



--
This message was sent by Atlassian JIRA
(v6.4.11#64026)

From issues at jboss.org  Sun Apr 24 06:23:01 2016
From: issues at jboss.org (Bartosz Majsak (JIRA))
Date: Sun, 24 Apr 2016 06:23:01 -0400 (EDT)
Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1282) TestNG @DataProvider is
 fully invoked for each record
In-Reply-To: <JIRA.12483918.1359633652000@Atlassian.JIRA>
References: <JIRA.12483918.1359633652000@Atlassian.JIRA>
	<JIRA.12483918.1359633652000@jira.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12483918.1359633652000.59491.1461493381116@Atlassian.JIRA>


     [ https://issues.jboss.org/browse/ARQ-1282?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Bartosz Majsak reassigned ARQ-1282:
-----------------------------------

    Assignee: Bartosz Majsak


> TestNG @DataProvider is fully invoked for each record
> -----------------------------------------------------
>
>                 Key: ARQ-1282
>                 URL: https://issues.jboss.org/browse/ARQ-1282
>             Project: Arquillian
>          Issue Type: Bug
>          Components: JBoss AS Containers
>    Affects Versions: 1.0.3.Final
>            Reporter: Karel Cemus
>            Assignee: Bartosz Majsak
>         Attachments: ArquillianDataProvider.java, FlightServiceTest.java
>
>
> h2. Expected behavior
> TestNG defines @DataProvider annotation to allow single method to perform multiple test cases. Provider method annotated with @DataProvider returns an array of arrays, each containing one test case. These parameters are given to the target method as input parameters. By the definition, the total count of performed test by single method is equal to number of test cases in related data provider.
> h2. Actual behavior
> Using TestNG under Arquillian framework makes this functionality buggy. Although the client (maven, IDE, etc.) thinks, that the total number of invoked test is correct, it is not. When we take a look into server's log, we can see that for each single test case it invoked full set of all test cases. It means, that in the end the amount of performed tests is equal to expected count squared. Such behaviour is not only slow but also in some cases it doesn't work and it makes tests to fail.
> h2. Example
> {code:java}
> @DataProvider
> public Object[][] sumProvider() {
>     return new Object[][]{
>         new Object[]{ 0, 0, 0 },
>         new Object[]{ 1, 1, 2 },
>         new Object[]{ 1, 5, 6 },
>         new Object[]{ 5, 1, 6 }
>     };
> }
> {code}
> h3. Expected output in server log
> {quote}
> Execution of sum: 0 + 0 = 0
> Execution of sum: 1 + 1 = 2
> Execution of sum: 1 + 5 = 6
> Execution of sum: 5 + 1 = 6
> {quote}
> h3. Actual output
> {quote}
> Execution of sum: 0 + 0 = 0
> Execution of sum: 1 + 1 = 2
> Execution of sum: 1 + 5 = 6
> Execution of sum: 5 + 1 = 6
> Execution of sum: 0 + 0 = 0
> Execution of sum: 1 + 1 = 2
> Execution of sum: 1 + 5 = 6
> Execution of sum: 5 + 1 = 6
> Execution of sum: 0 + 0 = 0
> Execution of sum: 1 + 1 = 2
> Execution of sum: 1 + 5 = 6
> Execution of sum: 5 + 1 = 6
> Execution of sum: 0 + 0 = 0
> Execution of sum: 1 + 1 = 2
> Execution of sum: 1 + 5 = 6
> Execution of sum: 5 + 1 = 6
> {quote}



--
This message was sent by Atlassian JIRA
(v6.4.11#64026)

From issues at jboss.org  Sun Apr 24 06:50:00 2016
From: issues at jboss.org (Bartosz Majsak (JIRA))
Date: Sun, 24 Apr 2016 06:50:00 -0400 (EDT)
Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1213) Add support for
	GlassFish 3.0 container
In-Reply-To: <JIRA.12479581.1353455577000@Atlassian.JIRA>
References: <JIRA.12479581.1353455577000@Atlassian.JIRA>
	<JIRA.12479581.1353455577000@jira.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12479581.1353455577000.59494.1461495000226@Atlassian.JIRA>


    [ https://issues.jboss.org/browse/ARQ-1213?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13196121#comment-13196121 ] 

Bartosz Majsak commented on ARQ-1213:
-------------------------------------

Do we still consider this issue relevant?

> Add support for GlassFish 3.0 container
> ---------------------------------------
>
>                 Key: ARQ-1213
>                 URL: https://issues.jboss.org/browse/ARQ-1213
>             Project: Arquillian
>          Issue Type: Feature Request
>          Components: GlassFish Containers
>            Reporter: Vineet Reynolds
>            Priority: Minor
>
> The RESTful admin API provided by GlassFish 3.0 does not provide all the REST resources that are currently used by the GlassFish 3.1 adapter. Hence, the 3.1 adapter is not backward compatible with a GlassFish 3.0 instance.
> Additionally, the message formats returned by the REST resources of GF 3.0 are different from the ones returned by GF 3.1, hence requiring different parsing semantics.
> We must therefore implement a separate adapter to support GlassFish 3.0, that either uses the RESTful Admin APIs available in 3.0, or a supported API like JSR-88.



--
This message was sent by Atlassian JIRA
(v6.4.11#64026)

From issues at jboss.org  Sun Apr 24 06:51:00 2016
From: issues at jboss.org (Bartosz Majsak (JIRA))
Date: Sun, 24 Apr 2016 06:51:00 -0400 (EDT)
Subject: [arquillian-issues] [JBoss JIRA] (ARQ-77) Support @EJB injection
	with proper semantics
In-Reply-To: <JIRA.12405529.1267305490000@Atlassian.JIRA>
References: <JIRA.12405529.1267305490000@Atlassian.JIRA>
	<JIRA.12405529.1267305490000@jira.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12405529.1267305490000.59506.1461495060460@Atlassian.JIRA>


    [ https://issues.jboss.org/browse/ARQ-77?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13196122#comment-13196122 ] 

Bartosz Majsak commented on ARQ-77:
-----------------------------------

Spring cleaning - is it still relevant? Seems to me like fixed ages ago. Can  we close this issue?

> Support @EJB injection with proper semantics
> --------------------------------------------
>
>                 Key: ARQ-77
>                 URL: https://issues.jboss.org/browse/ARQ-77
>             Project: Arquillian
>          Issue Type: Bug
>          Components: GlassFish Containers, JBoss AS Containers, OpenEJB Containers, Packaging Enricher SPI
>    Affects Versions: 1.0.0.Alpha1, 1.0.0.Alpha2
>            Reporter: Andrew Rubinger
>            Assignee: Andrew Rubinger
>            Priority: Critical
>
> Tests should be able to have class or instance members injected according to @EJB semantics, avoiding the need for lookup code.  The prototype is currently in the OpenEJB integration module, but really we should have some EJB 3.1 Global JNDI syntax compatible resolvers (which need an EJB name, module name, app name, and business interface name).  Note that portable JNDI is under java:global, so only accessible to local JVMs.



--
This message was sent by Atlassian JIRA
(v6.4.11#64026)

From issues at jboss.org  Sun Apr 24 07:14:00 2016
From: issues at jboss.org (Bartosz Majsak (JIRA))
Date: Sun, 24 Apr 2016 07:14:00 -0400 (EDT)
Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1212) Add support for
	GlassFish 2.x containers
In-Reply-To: <JIRA.12479580.1353455272000@Atlassian.JIRA>
References: <JIRA.12479580.1353455272000@Atlassian.JIRA>
	<JIRA.12479580.1353455272000@jira.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12479580.1353455272000.59509.1461496440118@Atlassian.JIRA>


    [ https://issues.jboss.org/browse/ARQ-1212?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13196123#comment-13196123 ] 

Bartosz Majsak commented on ARQ-1212:
-------------------------------------

Is this issue still relevant?

> Add support for GlassFish 2.x containers
> ----------------------------------------
>
>                 Key: ARQ-1212
>                 URL: https://issues.jboss.org/browse/ARQ-1212
>             Project: Arquillian
>          Issue Type: Feature Request
>          Components: GlassFish Containers
>            Reporter: Vineet Reynolds
>            Priority: Minor
>
> There has been atleast one request to support the GlassFish 2.x container. Since the RESTful admin API used by the current GlassFish adapter is available only since 3.0, we'll need to implement support for 2.x using a different mechanism (possibly using JSR-88 APIs).



--
This message was sent by Atlassian JIRA
(v6.4.11#64026)

From issues at jboss.org  Sun Apr 24 07:20:00 2016
From: issues at jboss.org (Bartosz Majsak (JIRA))
Date: Sun, 24 Apr 2016 07:20:00 -0400 (EDT)
Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1383) Support deployment of
 container wide resource.xml in GlassFish Managed and Remote
In-Reply-To: <JIRA.12490823.1367330511000@Atlassian.JIRA>
References: <JIRA.12490823.1367330511000@Atlassian.JIRA>
	<JIRA.12490823.1367330511000@jira.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12490823.1367330511000.59512.1461496800182@Atlassian.JIRA>


     [ https://issues.jboss.org/browse/ARQ-1383?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Bartosz Majsak reassigned ARQ-1383:
-----------------------------------

    Assignee: Bartosz Majsak


> Support deployment of container wide resource.xml in GlassFish Managed and Remote 
> ----------------------------------------------------------------------------------
>
>                 Key: ARQ-1383
>                 URL: https://issues.jboss.org/browse/ARQ-1383
>             Project: Arquillian
>          Issue Type: Feature Request
>          Components: GlassFish Containers
>    Affects Versions: glassfish_1.0.0.CR4
>            Reporter: Aslak Knutsen
>            Assignee: Bartosz Majsak
>             Fix For: glassfish_1.0.0.Final
>
>
> As a User I would like to deploy Container wide resources
> Given a Reference to a resource.xml file in ContainerConfiguration
> When the Container starts up
> Then the resource.xml should be deployed
> When the Container shuts down
> Then the resource.xml should be undeployed
> This is similar to how GlassFish Embedded works.
> Configuration: https://github.com/arquillian/arquillian-container-glassfish/blob/master/glassfish-embedded-3.1/src/main/java/org/jboss/arquillian/container/glassfish/embedded_3_1/GlassFishConfiguration.java#L156
> Container Impl: https://github.com/arquillian/arquillian-container-glassfish/blob/master/glassfish-embedded-3.1/src/main/java/org/jboss/arquillian/container/glassfish/embedded_3_1/GlassFishContainer.java#L186



--
This message was sent by Atlassian JIRA
(v6.4.11#64026)

From issues at jboss.org  Mon Apr 25 03:31:00 2016
From: issues at jboss.org (Bartosz Majsak (JIRA))
Date: Mon, 25 Apr 2016 03:31:00 -0400 (EDT)
Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1566) NPE in
 GlassFishClientService when connecting to a ssl only glassfish
In-Reply-To: <JIRA.12524874.1384261015000@Atlassian.JIRA>
References: <JIRA.12524874.1384261015000@Atlassian.JIRA>
	<JIRA.12524874.1384261015000@jira.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12524874.1384261015000.60082.1461569460302@Atlassian.JIRA>


     [ https://issues.jboss.org/browse/ARQ-1566?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Bartosz Majsak reassigned ARQ-1566:
-----------------------------------

    Assignee: Bartosz Majsak


> NPE in GlassFishClientService when connecting to a ssl only glassfish
> ---------------------------------------------------------------------
>
>                 Key: ARQ-1566
>                 URL: https://issues.jboss.org/browse/ARQ-1566
>             Project: Arquillian
>          Issue Type: Bug
>          Components: GlassFish Containers
>    Affects Versions: glassfish_1.0.0.CR4
>            Reporter: Daniel G
>            Assignee: Bartosz Majsak
>
> When connecting to a remote-glassfish that has no http port open
> {noformat:title=related domain.xml excerpt}
> <network-listeners>
>           <network-listener port="${HTTP_LISTENER_PORT}" enabled="false" protocol="http-listener-1" transport="tcp" name
> ="http-listener-1" thread-pool="http-thread-pool"></network-listener>
> ...
> {noformat}
> the test-startup crashes with a NullPointerException.
> {noformat}
> java.lang.NullPointerException: null
>  	at java.util.regex.Matcher.getTextLength(Matcher.java:1234)
>  	at java.util.regex.Matcher.reset(Matcher.java:308)
>  	at java.util.regex.Matcher.<init>(Matcher.java:228)
>  	at java.util.regex.Pattern.matcher(Pattern.java:1088)
>  	at org.jboss.arquillian.container.glassfish.clientutils.GlassFishClientService.getPortValue(GlassFishClientService.java:673)
>  	at org.jboss.arquillian.container.glassfish.clientutils.GlassFishClientService.access$500(GlassFishClientService.java:41)
>  	at org.jboss.arquillian.container.glassfish.clientutils.GlassFishClientService$ClusterServer.getNodeAddressList(GlassFishClientService.java:880)
>  	at org.jboss.arquillian.container.glassfish.clientutils.GlassFishClientService.startUp(GlassFishClientService.java:133)
>  	at org.jboss.arquillian.container.glassfish.CommonGlassFishManager.start(CommonGlassFishManager.java:72)
>  	at org.jboss.arquillian.container.glassfish.remote_3_1.GlassFishRestDeployableContainer.start(GlassFishRestDeployableContainer.java:59)
>  	at org.jboss.arquillian.container.impl.ContainerImpl.start(ContainerImpl.java:199)
>  	at org.jboss.arquillian.container.impl.client.container.ContainerLifecycleController$8.perform(ContainerLifecycleController.java:163)
>  	at org.jboss.arquillian.container.impl.client.container.ContainerLifecycleController$8.perform(ContainerLifecycleController.java:157)
>  	at org.jboss.arquillian.container.impl.client.container.ContainerLifecycleController.forContainer(ContainerLifecycleController.java:255)
>  	at org.jboss.arquillian.container.impl.client.container.ContainerLifecycleController.startContainer(ContainerLifecycleController.java:156)
>  	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> ...
> {noformat}
> so i forked the build (https://github.com/dgeissl/arquillian-container-glassfish.git) and fixed the corresponding codelines.
> to finaly see that the basic https support is missing in Arquillian, cause now i get this exception:
> {noformat}
> java.lang.IllegalStateException: Error launching test MyTest public void MyTest.testMe()
> 	at org.jboss.arquillian.protocol.servlet.ServletMethodExecutor.invoke(ServletMethodExecutor.java:103)
> 	at org.jboss.arquillian.container.test.impl.execution.RemoteTestExecuter.execute(RemoteTestExecuter.java:120)
> 	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> 	at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
> 	at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
> 	at java.lang.reflect.Method.invoke(Unknown Source)
> 	at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94)
> 	at org.jboss.arquillian.core.impl.EventContextImpl.invokeObservers(EventContextImpl.java:99)
> 	at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:81)
> 	at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:135)
> 	at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:115)
> ...
> Caused by: java.net.SocketException: Unexpected end of file from server
> 	at sun.net.www.http.HttpClient.parseHTTPHeader(Unknown Source)
> 	at sun.net.www.http.HttpClient.parseHTTP(Unknown Source)
> 	at sun.net.www.http.HttpClient.parseHTTPHeader(Unknown Source)
> 	at sun.net.www.http.HttpClient.parseHTTP(Unknown Source)
> 	at sun.net.www.protocol.http.HttpURLConnection.getInputStream(Unknown Source)
> 	at java.net.HttpURLConnection.getResponseCode(Unknown Source)
> 	at org.jboss.arquillian.protocol.servlet.ServletMethodExecutor.execute(ServletMethodExecutor.java:183)
> 	at org.jboss.arquillian.protocol.servlet.ServletMethodExecutor.executeWithRetry(ServletMethodExecutor.java:121)
> 	at org.jboss.arquillian.protocol.servlet.ServletMethodExecutor.invoke(ServletMethodExecutor.java:99)
> 	... 75 more
> {noformat}
> So the basic NPE cause can be fixed but for the https support we need core changes right?
> Like mentioned in ARQ-643



--
This message was sent by Atlassian JIRA
(v6.4.11#64026)

From issues at jboss.org  Wed Apr 27 03:10:00 2016
From: issues at jboss.org (Aslak Knutsen (JIRA))
Date: Wed, 27 Apr 2016 03:10:00 -0400 (EDT)
Subject: [arquillian-issues] [JBoss JIRA] (ARQ-77) Support @EJB injection
	with proper semantics
In-Reply-To: <JIRA.12405529.1267305490000@Atlassian.JIRA>
References: <JIRA.12405529.1267305490000@Atlassian.JIRA>
	<JIRA.12405529.1267305490000@jira.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12405529.1267305490000.71890.1461741000803@Atlassian.JIRA>


    [ https://issues.jboss.org/browse/ARQ-77?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13197512#comment-13197512 ] 

Aslak Knutsen commented on ARQ-77:
----------------------------------

No, EJB injection outside of a CDI enabled deployment is still based on guessing names. But only relevant to older containers as CDI is enabled by default in EE7

> Support @EJB injection with proper semantics
> --------------------------------------------
>
>                 Key: ARQ-77
>                 URL: https://issues.jboss.org/browse/ARQ-77
>             Project: Arquillian
>          Issue Type: Bug
>          Components: GlassFish Containers, JBoss AS Containers, OpenEJB Containers, Packaging Enricher SPI
>    Affects Versions: 1.0.0.Alpha1, 1.0.0.Alpha2
>            Reporter: Andrew Rubinger
>            Assignee: Andrew Rubinger
>            Priority: Critical
>
> Tests should be able to have class or instance members injected according to @EJB semantics, avoiding the need for lookup code.  The prototype is currently in the OpenEJB integration module, but really we should have some EJB 3.1 Global JNDI syntax compatible resolvers (which need an EJB name, module name, app name, and business interface name).  Note that portable JNDI is under java:global, so only accessible to local JVMs.



--
This message was sent by Atlassian JIRA
(v6.4.11#64026)

From issues at jboss.org  Wed Apr 27 03:11:00 2016
From: issues at jboss.org (Aslak Knutsen (JIRA))
Date: Wed, 27 Apr 2016 03:11:00 -0400 (EDT)
Subject: [arquillian-issues] [JBoss JIRA] (ARQ-1213) Add support for
	GlassFish 3.0 container
In-Reply-To: <JIRA.12479581.1353455577000@Atlassian.JIRA>
References: <JIRA.12479581.1353455577000@Atlassian.JIRA>
	<JIRA.12479581.1353455577000@jira.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12479581.1353455577000.71896.1461741060353@Atlassian.JIRA>


    [ https://issues.jboss.org/browse/ARQ-1213?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13197513#comment-13197513 ] 

Aslak Knutsen commented on ARQ-1213:
------------------------------------

I would say no

> Add support for GlassFish 3.0 container
> ---------------------------------------
>
>                 Key: ARQ-1213
>                 URL: https://issues.jboss.org/browse/ARQ-1213
>             Project: Arquillian
>          Issue Type: Feature Request
>          Components: GlassFish Containers
>            Reporter: Vineet Reynolds
>            Priority: Minor
>
> The RESTful admin API provided by GlassFish 3.0 does not provide all the REST resources that are currently used by the GlassFish 3.1 adapter. Hence, the 3.1 adapter is not backward compatible with a GlassFish 3.0 instance.
> Additionally, the message formats returned by the REST resources of GF 3.0 are different from the ones returned by GF 3.1, hence requiring different parsing semantics.
> We must therefore implement a separate adapter to support GlassFish 3.0, that either uses the RESTful Admin APIs available in 3.0, or a supported API like JSR-88.



--
This message was sent by Atlassian JIRA
(v6.4.11#64026)