May 2013 - arquillian-issues - Jboss List Archives

[JBoss JIRA] (ARQ-1390) @ArquillianResource URL contextPath is malformed if the web archive name contains dots

by Bartosz Majsak (JIRA)

[ https://issues.jboss.org/browse/ARQ-1390?page=com.atlassian.jira.plugin.s... ] Bartosz Majsak commented on ARQ-1390: ------------------------------------- Then this might be a [problem|https://github.com/wildfly/wildfly/blob/master/arquillian/common/...]. > @ArquillianResource URL contextPath is malformed if the web archive name contains dots > -------------------------------------------------------------------------------------- > > Key: ARQ-1390 > URL: https://issues.jboss.org/browse/ARQ-1390 > Project: Arquillian > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Base Implementation > Affects Versions: 1.0.3.Final > Reporter: Ron Šmeral > Attachments: arq-1390-reproducer.zip > > > If a WAR with dots in the name is deployed, the context path returned using {{@ArquillianResource URL contextPath}} is incorrect, as it has the segment after the last dot stripped off. > For example, deploying an archive called {{this.archive.has.dots.war}}, the real context path reported by the server is {{/this.archive.has.dots}} but {{@ArquillianResource URL}} points to {{/this.archive.has}}. -- 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

12 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ARQ-1390) @ArquillianResource URL contextPath is malformed if the web archive name contains dots

by Ron Šmeral (JIRA)

[ https://issues.jboss.org/browse/ARQ-1390?page=com.atlassian.jira.plugin.s... ] Ron Šmeral commented on ARQ-1390: --------------------------------- Tried just now - still broken with Wildfly 8.0.0.Alpha1. > @ArquillianResource URL contextPath is malformed if the web archive name contains dots > -------------------------------------------------------------------------------------- > > Key: ARQ-1390 > URL: https://issues.jboss.org/browse/ARQ-1390 > Project: Arquillian > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Base Implementation > Affects Versions: 1.0.3.Final > Reporter: Ron Šmeral > Attachments: arq-1390-reproducer.zip > > > If a WAR with dots in the name is deployed, the context path returned using {{@ArquillianResource URL contextPath}} is incorrect, as it has the segment after the last dot stripped off. > For example, deploying an archive called {{this.archive.has.dots.war}}, the real context path reported by the server is {{/this.archive.has.dots}} but {{@ArquillianResource URL}} points to {{/this.archive.has}}. -- 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

12 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ARQ-1390) @ArquillianResource URL contextPath is malformed if the web archive name contains dots

by Bartosz Majsak (JIRA)

[ https://issues.jboss.org/browse/ARQ-1390?page=com.atlassian.jira.plugin.s... ] Bartosz Majsak commented on ARQ-1390: ------------------------------------- Hi Ron! Many thanks for detailed report. I think it is more AS7 container adapter issue rather than Arquillian Core itself. Have you tried newer version? > @ArquillianResource URL contextPath is malformed if the web archive name contains dots > -------------------------------------------------------------------------------------- > > Key: ARQ-1390 > URL: https://issues.jboss.org/browse/ARQ-1390 > Project: Arquillian > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Base Implementation > Affects Versions: 1.0.3.Final > Reporter: Ron Šmeral > Attachments: arq-1390-reproducer.zip > > > If a WAR with dots in the name is deployed, the context path returned using {{@ArquillianResource URL contextPath}} is incorrect, as it has the segment after the last dot stripped off. > For example, deploying an archive called {{this.archive.has.dots.war}}, the real context path reported by the server is {{/this.archive.has.dots}} but {{@ArquillianResource URL}} points to {{/this.archive.has}}. -- 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

12 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ARQ-1390) @ArquillianResource URL contextPath is malformed if the web archive name contains dots

by Ron Šmeral (JIRA)

[ https://issues.jboss.org/browse/ARQ-1390?page=com.atlassian.jira.plugin.s... ] Ron Šmeral updated ARQ-1390: ---------------------------- Attachment: arq-1390-reproducer.zip Reproducer attached. > @ArquillianResource URL contextPath is malformed if the web archive name contains dots > -------------------------------------------------------------------------------------- > > Key: ARQ-1390 > URL: https://issues.jboss.org/browse/ARQ-1390 > Project: Arquillian > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Base Implementation > Affects Versions: 1.0.3.Final > Reporter: Ron Šmeral > Attachments: arq-1390-reproducer.zip > > > If a WAR with dots in the name is deployed, the context path returned using {{@ArquillianResource URL contextPath}} is incorrect, as it has the segment after the last dot stripped off. > For example, deploying an archive called {{this.archive.has.dots.war}}, the real context path reported by the server is {{/this.archive.has.dots}} but {{@ArquillianResource URL}} points to {{/this.archive.has}}. -- 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

12 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ARQ-1390) @ArquillianResource URL contextPath is malformed if the web archive name contains dots

by Ron Šmeral (JIRA)

Ron Šmeral created ARQ-1390: ------------------------------- Summary: @ArquillianResource URL contextPath is malformed if the web archive name contains dots Key: ARQ-1390 URL: https://issues.jboss.org/browse/ARQ-1390 Project: Arquillian Issue Type: Bug Security Level: Public (Everyone can see) Components: Base Implementation Affects Versions: 1.0.3.Final Reporter: Ron Šmeral If a WAR with dots in the name is deployed, the context path returned using {{@ArquillianResource URL contextPath}} is incorrect, as it has the segment after the last dot stripped off. For example, deploying an archive called {{this.archive.has.dots.war}}, the real context path reported by the server is {{/this.archive.has.dots}} but {{@ArquillianResource URL}} points to {{/this.archive.has}}. -- 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

12 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ARQ-1389) Create an extension that allows users to specify CDI context active for a test.

by John Ament (JIRA)

John Ament created ARQ-1389: ------------------------------- Summary: Create an extension that allows users to specify CDI context active for a test. Key: ARQ-1389 URL: https://issues.jboss.org/browse/ARQ-1389 Project: Arquillian Issue Type: Feature Request Security Level: Public (Everyone can see) Reporter: John Ament I've seen the need for this to pop up in several places - at work, in SO questions, in email threads, and I think it would be ideal to handle as a new Arquillian Extension. Right now, Arquillian is dependent on the app server to manage context and typically the context activated is whatever the app server finds as appropriate. This works OK for servlet based containers since a RequestScope will be active, but for local, embedded (non servlet) or even JMX protocol based containers this doesn't work. Ideally, a developer would be able to annotate a test method: @ActiveContext(ValidScope.class) Where ValidScope.class is a CDI scope (RequestScoped, SessionScoped.. etc) that can be activated. The extension would then activate this scope for the duration of the test, allowing injection of appropriately scoped objects to be injected correctly. Perhaps this annotation can also be class level, applying to everything in that class. -- 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

12 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ARQ-512) Provide a ServerKillProcessor implementation for Infinispan server

by Martin Gencur (JIRA)

[ https://issues.jboss.org/browse/ARQ-512?page=com.atlassian.jira.plugin.sy... ] Martin Gencur resolved ARQ-512. ------------------------------- Resolution: Out of Date > Provide a ServerKillProcessor implementation for Infinispan server > ------------------------------------------------------------------ > > Key: ARQ-512 > URL: https://issues.jboss.org/browse/ARQ-512 > Project: Arquillian > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Infinispan Containers > Reporter: Martin Gencur > Assignee: Martin Gencur > > This implementation should be able to hard kill the Infinispan server. We can then test real failover. Work on this can be started once ARQ-336 is resolved. -- 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

12 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ARQ-1388) @EJB not working in embedded glassfish for @Remote Stateless beans if called more than twice

by Dominik Kuhn (JIRA)

[ https://issues.jboss.org/browse/ARQ-1388?page=com.atlassian.jira.plugin.s... ] Dominik Kuhn commented on ARQ-1388: ----------------------------------- Yes, i get the same result without caching. Sorry i didn't remove it for the simple test project. therefore i uploaded the zipped project without caching. > @EJB not working in embedded glassfish for @Remote Stateless beans if called more than twice > -------------------------------------------------------------------------------------------- > > Key: ARQ-1388 > URL: https://issues.jboss.org/browse/ARQ-1388 > Project: Arquillian > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Base Implementation > Affects Versions: 1.0.3.Final, glassfish_1.0.0.CR4 > Reporter: Dominik Kuhn > Attachments: arqtest.zip, arqtest2.zip > > > We have 20 testclasses. the ejb's are injected by the @EJB annotation. > If each testclass is run standalone (using eclipse), everything works and the tests are successful. > If all testclasses are run together (using eclipse or maven surefire plugin) the test fails after the first two testclasses with one of the two following error messages: > java.lang.NullPointerException > at arqtest.test.GreeterTest5.test(GreeterTest5.java:23) > ... > or > java.lang.IllegalArgumentException: ArquillianServletRunner not found. Could not determine ContextRoot from ProtocolMetadata, please contact DeployableContainer developer. > ... > If I change the @Remote annotation of the stateless beans to @Local the tests are successful, even if run together. > To test this i created a very simple test project, which i attached to this issue. -- 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

12 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ARQ-1388) @EJB not working in embedded glassfish for @Remote Stateless beans if called more than twice

by Dominik Kuhn (JIRA)

[ https://issues.jboss.org/browse/ARQ-1388?page=com.atlassian.jira.plugin.s... ] Dominik Kuhn updated ARQ-1388: ------------------------------ Attachment: arqtest2.zip Without caching ear / jar > @EJB not working in embedded glassfish for @Remote Stateless beans if called more than twice > -------------------------------------------------------------------------------------------- > > Key: ARQ-1388 > URL: https://issues.jboss.org/browse/ARQ-1388 > Project: Arquillian > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Base Implementation > Affects Versions: 1.0.3.Final, glassfish_1.0.0.CR4 > Reporter: Dominik Kuhn > Attachments: arqtest.zip, arqtest2.zip > > > We have 20 testclasses. the ejb's are injected by the @EJB annotation. > If each testclass is run standalone (using eclipse), everything works and the tests are successful. > If all testclasses are run together (using eclipse or maven surefire plugin) the test fails after the first two testclasses with one of the two following error messages: > java.lang.NullPointerException > at arqtest.test.GreeterTest5.test(GreeterTest5.java:23) > ... > or > java.lang.IllegalArgumentException: ArquillianServletRunner not found. Could not determine ContextRoot from ProtocolMetadata, please contact DeployableContainer developer. > ... > If I change the @Remote annotation of the stateless beans to @Local the tests are successful, even if run together. > To test this i created a very simple test project, which i attached to this issue. -- 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

12 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ARQ-1388) @EJB not working in embedded glassfish for @Remote Stateless beans if called more than twice

by Aslak Knutsen (JIRA)

[ https://issues.jboss.org/browse/ARQ-1388?page=com.atlassian.jira.plugin.s... ] Aslak Knutsen commented on ARQ-1388: ------------------------------------ Do you get the same even if you don't cache the ear and the jar between tests? > @EJB not working in embedded glassfish for @Remote Stateless beans if called more than twice > -------------------------------------------------------------------------------------------- > > Key: ARQ-1388 > URL: https://issues.jboss.org/browse/ARQ-1388 > Project: Arquillian > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Base Implementation > Affects Versions: 1.0.3.Final, glassfish_1.0.0.CR4 > Reporter: Dominik Kuhn > Attachments: arqtest.zip > > > We have 20 testclasses. the ejb's are injected by the @EJB annotation. > If each testclass is run standalone (using eclipse), everything works and the tests are successful. > If all testclasses are run together (using eclipse or maven surefire plugin) the test fails after the first two testclasses with one of the two following error messages: > java.lang.NullPointerException > at arqtest.test.GreeterTest5.test(GreeterTest5.java:23) > ... > or > java.lang.IllegalArgumentException: ArquillianServletRunner not found. Could not determine ContextRoot from ProtocolMetadata, please contact DeployableContainer developer. > ... > If I change the @Remote annotation of the stateless beans to @Local the tests are successful, even if run together. > To test this i created a very simple test project, which i attached to this issue. -- 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

12 years, 10 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

arquillian-issues May 2013