[JBoss JIRA] (ARQ-1027) Support CommandService Protocol SPI via Warp Protocol
by Lukáš Fryč (JIRA)
[ https://issues.jboss.org/browse/ARQ-1027?page=com.atlassian.jira.plugin.s... ]
Lukáš Fryč updated ARQ-1027:
----------------------------
Status: Pull Request Sent (was: Open)
Git Pull Request: https://github.com/arquillian/arquillian-extension-warp/pull/9
> Support CommandService Protocol SPI via Warp Protocol
> -----------------------------------------------------
>
> Key: ARQ-1027
> URL: https://issues.jboss.org/browse/ARQ-1027
> Project: Arquillian
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: Extension - Warp
> Affects Versions: warp_1.0.0.Alpha1
> Reporter: Curtis McMillen
> Priority: Critical
> Fix For: warp_1.0.0.Beta1
>
> Attachments: stacktrace.txt
>
> Original Estimate: 1 day
> Remaining Estimate: 1 day
>
> It seems there is a problem with running Warp tests if arquillian-jacoco is on the classpath.
> When WarpFilter fires the AfterSuite event, the writeCoverageData observer in arquillian-jacoco is executing which ultimately leads to a NPE coming from servlet protocol. The full stacktrace is attached.
> You can reproduce by simply adding the following dependencies to the pom for warp in arquillian-showcase and then running the BasicJSFUnitTestCase.
> {code:xml}
> <dependency>
> <groupId>org.jboss.arquillian.extension</groupId>
> <artifactId>arquillian-jacoco</artifactId>
> <version>1.0.0.Alpha3</version>
> <scope>test</scope>
> </dependency>
> <dependency>
> <groupId>org.jacoco</groupId>
> <artifactId>org.jacoco.core</artifactId>
> <version>0.5.7.201204190339</version>
> <scope>test</scope>
> </dependency>
> {code}
> Removing these dependencies isn't really an option because I have other arquillian tests not using Warp that I want code coverage on. I tried using alternative annotated with @Specializes thinking I could basically disable the observer in arquillian-jacoco simply by including a different beans.xml in the deployment of my Warp tests. This however fails with "WELD-000047 Specializing bean must extend another bean" which I'm thinking is due to https://issues.jboss.org/browse/WELD-1113.
> Any ideas for getting this to work?
--
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
13 years, 1 month
[JBoss JIRA] (ARQ-1027) Support CommandService Protocol SPI via Warp Protocol
by Lukáš Fryč (JIRA)
[ https://issues.jboss.org/browse/ARQ-1027?page=com.atlassian.jira.plugin.s... ]
Lukáš Fryč updated ARQ-1027:
----------------------------
Assignee: (was: Lukáš Fryč)
> Support CommandService Protocol SPI via Warp Protocol
> -----------------------------------------------------
>
> Key: ARQ-1027
> URL: https://issues.jboss.org/browse/ARQ-1027
> Project: Arquillian
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: Extension - Warp
> Affects Versions: warp_1.0.0.Alpha1
> Reporter: Curtis McMillen
> Priority: Critical
> Fix For: warp_1.0.0.Beta1
>
> Attachments: stacktrace.txt
>
> Original Estimate: 1 day
> Remaining Estimate: 1 day
>
> It seems there is a problem with running Warp tests if arquillian-jacoco is on the classpath.
> When WarpFilter fires the AfterSuite event, the writeCoverageData observer in arquillian-jacoco is executing which ultimately leads to a NPE coming from servlet protocol. The full stacktrace is attached.
> You can reproduce by simply adding the following dependencies to the pom for warp in arquillian-showcase and then running the BasicJSFUnitTestCase.
> {code:xml}
> <dependency>
> <groupId>org.jboss.arquillian.extension</groupId>
> <artifactId>arquillian-jacoco</artifactId>
> <version>1.0.0.Alpha3</version>
> <scope>test</scope>
> </dependency>
> <dependency>
> <groupId>org.jacoco</groupId>
> <artifactId>org.jacoco.core</artifactId>
> <version>0.5.7.201204190339</version>
> <scope>test</scope>
> </dependency>
> {code}
> Removing these dependencies isn't really an option because I have other arquillian tests not using Warp that I want code coverage on. I tried using alternative annotated with @Specializes thinking I could basically disable the observer in arquillian-jacoco simply by including a different beans.xml in the deployment of my Warp tests. This however fails with "WELD-000047 Specializing bean must extend another bean" which I'm thinking is due to https://issues.jboss.org/browse/WELD-1113.
> Any ideas for getting this to work?
--
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
13 years, 1 month
[JBoss JIRA] (ARQ-1291) Warp: single request execution does enrich only first request
by Lukáš Fryč (JIRA)
[ https://issues.jboss.org/browse/ARQ-1291?page=com.atlassian.jira.plugin.s... ]
Lukáš Fryč updated ARQ-1291:
----------------------------
Affects Version/s: warp_1.0.0.Alpha2
> Warp: single request execution does enrich only first request
> -------------------------------------------------------------
>
> Key: ARQ-1291
> URL: https://issues.jboss.org/browse/ARQ-1291
> Project: Arquillian
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: Extension - Warp
> Affects Versions: warp_1.0.0.Alpha2
> Reporter: Lukáš Fryč
>
> When single-request execution API is used
> {code}
> Warp.initiate(Activity)
> .inspect(Inspection);
> {code}
> then the default filter is applied which says that only first request can be enriched,
> and thus when user-provided filter selects second or further request, nothing will be enriched.
> In fact it should work in the way that first user-selected request is enriched.
--
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
13 years, 1 month
[JBoss JIRA] (ARQ-1291) Warp: single request execution does enrich only first request
by Lukáš Fryč (JIRA)
[ https://issues.jboss.org/browse/ARQ-1291?page=com.atlassian.jira.plugin.s... ]
Lukáš Fryč updated ARQ-1291:
----------------------------
Description:
When single-request execution API is used
{code}
Warp.initiate(Activity)
.inspect(Inspection);
{code}
then the default filter is applied which says that only first request can be enriched,
and thus when user-provided filter selects second or further request, nothing will be enriched.
In fact it should work in the way that first user-selected request is enriched.
> Warp: single request execution does enrich only first request
> -------------------------------------------------------------
>
> Key: ARQ-1291
> URL: https://issues.jboss.org/browse/ARQ-1291
> Project: Arquillian
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Reporter: Lukáš Fryč
>
> When single-request execution API is used
> {code}
> Warp.initiate(Activity)
> .inspect(Inspection);
> {code}
> then the default filter is applied which says that only first request can be enriched,
> and thus when user-provided filter selects second or further request, nothing will be enriched.
> In fact it should work in the way that first user-selected request is enriched.
--
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
13 years, 1 month
[JBoss JIRA] (ARQ-1290) Warp: support Servlets 2.5
by Lukáš Fryč (JIRA)
[ https://issues.jboss.org/browse/ARQ-1290?page=com.atlassian.jira.plugin.s... ]
Lukáš Fryč updated ARQ-1290:
----------------------------
Description:
Warp currently uses {{@WebFilter}} and thus it is supported only when using Servlets 3.0 protocol.
Additionally with ARQ-1027, the usage of {{web-fragment.xml}} was introduced.
Warp should detect what protocol is used (2.5 or 3.0) and in case of 2.5, the {{web.xml}} enrichment will be used instead.
was:
Warp currently uses {{@WebFilter}} and thus it is supported only when using Servlets 3.0 protocol.
Additionally with ARQ-1027, the usage of {{web-fragment.xml}} was introduced.
Warp should detect what protocol is used (2.5 or 3.0) and in case of 2.5, the web.xml enrichment will be used instead.
> Warp: support Servlets 2.5
> --------------------------
>
> Key: ARQ-1290
> URL: https://issues.jboss.org/browse/ARQ-1290
> Project: Arquillian
> Issue Type: Enhancement
> Security Level: Public(Everyone can see)
> Components: Extension - Warp
> Affects Versions: warp_1.0.0.Alpha2
> Reporter: Lukáš Fryč
>
> Warp currently uses {{@WebFilter}} and thus it is supported only when using Servlets 3.0 protocol.
> Additionally with ARQ-1027, the usage of {{web-fragment.xml}} was introduced.
> Warp should detect what protocol is used (2.5 or 3.0) and in case of 2.5, the {{web.xml}} enrichment will be used instead.
--
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
13 years, 1 month
[JBoss JIRA] (ARQ-1290) Warp: support Servlets 2.5
by Lukáš Fryč (JIRA)
[ https://issues.jboss.org/browse/ARQ-1290?page=com.atlassian.jira.plugin.s... ]
Lukáš Fryč updated ARQ-1290:
----------------------------
Description:
Warp currently uses {{@WebFilter}} and thus it is supported only when using Servlets 3.0 protocol.
Additionally with ARQ-1027, the usage of {{web-fragment.xml}} was introduced.
Warp should detect what protocol is used (2.5 or 3.0) and in case of 2.5, the web.xml enrichment will be used instead.
was:
Warp currently uses @WebFilter and thus it is supported only when using Servlets 3.0 protocol.
Additionally with ARQ-1027, the usage of {{web-fragment.xml}} was introduced.
Warp should detect what protocol is used (2.5 or 3.0) and in case of 2.5, the web.xml enrichment will be used instead.
> Warp: support Servlets 2.5
> --------------------------
>
> Key: ARQ-1290
> URL: https://issues.jboss.org/browse/ARQ-1290
> Project: Arquillian
> Issue Type: Enhancement
> Security Level: Public(Everyone can see)
> Components: Extension - Warp
> Affects Versions: warp_1.0.0.Alpha2
> Reporter: Lukáš Fryč
>
> Warp currently uses {{@WebFilter}} and thus it is supported only when using Servlets 3.0 protocol.
> Additionally with ARQ-1027, the usage of {{web-fragment.xml}} was introduced.
> Warp should detect what protocol is used (2.5 or 3.0) and in case of 2.5, the web.xml enrichment will be used instead.
--
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
13 years, 1 month
[JBoss JIRA] (ARQ-1290) Warp: support Servlets 2.5
by Lukáš Fryč (JIRA)
[ https://issues.jboss.org/browse/ARQ-1290?page=com.atlassian.jira.plugin.s... ]
Lukáš Fryč updated ARQ-1290:
----------------------------
Summary: Warp: support Servlets 2.5 (was: Warp: Support Servlets 2.5)
> Warp: support Servlets 2.5
> --------------------------
>
> Key: ARQ-1290
> URL: https://issues.jboss.org/browse/ARQ-1290
> Project: Arquillian
> Issue Type: Enhancement
> Security Level: Public(Everyone can see)
> Components: Extension - Warp
> Affects Versions: warp_1.0.0.Alpha2
> Reporter: Lukáš Fryč
>
> Warp currently uses @WebFilter and thus it is supported only when using Servlets 3.0 protocol.
> Additionally with ARQ-1027, the usage of {{web-fragment.xml}} was introduced.
> Warp should detect what protocol is used (2.5 or 3.0) and in case of 2.5, the web.xml enrichment will be used instead.
--
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
13 years, 1 month