June 2014 - arquillian-issues - Jboss List Archives

[JBoss JIRA] (ARQ-1777) Test hangs on remote Tomcat 6

by Aslak Knutsen (JIRA)

[ https://issues.jboss.org/browse/ARQ-1777?page=com.atlassian.jira.plugin.s... ] Aslak Knutsen updated ARQ-1777: ------------------------------- Component/s: Tomcat Containers > Test hangs on remote Tomcat 6 > ----------------------------- > > Key: ARQ-1777 > URL: https://issues.jboss.org/browse/ARQ-1777 > Project: Arquillian > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Tomcat Containers > Reporter: Pramod Kankure > > I have observed that test hangs when executing on tomcat 6 remote container. > My arquillian.xml looks like below. ( I don't use authentication for jmx) > <?xml version="1.0" encoding="UTF-8"?> > <arquillian xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" > xmlns="http://jboss.org/schema/arquillian" > xsi:schemaLocation="http://jboss.org/schema/arquillian > http://jboss.org/schema/arquillian/arquillian_1_0.xsd"> > <group qualifier="Grid" default="true"> > <defaultProtocol type="Servlet 3.0" /> > <container qualifier="remote-tomcat1" default="true"> > <configuration> > <property name="httpPort">1776</property> > <property name="host">localhost</property> > <property name="jmxPort">8090</property> > </configuration> > </container> > </group> > </arquillian> > The test do stops with an error when the server is down or wrong HTTP port is specified. It does execute @deployment method of the test but never comes to execute the test method annoted with [~test.todd] -- This message was sent by Atlassian JIRA (v6.2.6#6264)

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ARQ-1789) add tomcat 8 managed and/or remote container adapters

by Aslak Knutsen (JIRA)

[ https://issues.jboss.org/browse/ARQ-1789?page=com.atlassian.jira.plugin.s... ] Aslak Knutsen commented on ARQ-1789: ------------------------------------ Have you tried running the Managed/Remote 7 against a 8 Container? > add tomcat 8 managed and/or remote container adapters > ----------------------------------------------------- > > Key: ARQ-1789 > URL: https://issues.jboss.org/browse/ARQ-1789 > Project: Arquillian > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Reporter: Peter Butkovic > > I'd like to see managed and/or remote support for tomcat 8 available in arquillian. > As I need to do some container pre-configuration/patching before the run as well as to have clear classpath separation. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ARQ-1791) add geronimo managed and/or remote adapters

by Aslak Knutsen (JIRA)

[ https://issues.jboss.org/browse/ARQ-1791?page=com.atlassian.jira.plugin.s... ] Aslak Knutsen commented on ARQ-1791: ------------------------------------ If you have some experience with this Container, I'm happy to guide you in implement this. ? > add geronimo managed and/or remote adapters > ------------------------------------------- > > Key: ARQ-1791 > URL: https://issues.jboss.org/browse/ARQ-1791 > Project: Arquillian > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Reporter: Peter Butkovic > -- This message was sent by Atlassian JIRA (v6.2.6#6264)

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ARQ-1792) allow deployment with default interfaces instead of static methods

by Aslak Knutsen (JIRA)

[ https://issues.jboss.org/browse/ARQ-1792?page=com.atlassian.jira.plugin.s... ] Aslak Knutsen commented on ARQ-1792: ------------------------------------ Nice idea, but to my knowledge, default interface methods still need an instance of the Object to call it. The reason it's currently static is because we're creating the Deployment before we have a Instance of the TestClass available. > allow deployment with default interfaces instead of static methods > ------------------------------------------------------------------ > > Key: ARQ-1792 > URL: https://issues.jboss.org/browse/ARQ-1792 > Project: Arquillian > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Reporter: Caleb Cushing > > I'd like to be able to do an > {code:java} > @Deployment > default Archive createDeployment() { ... } > {code} > and then just apply the interface to my test class -- This message was sent by Atlassian JIRA (v6.2.6#6264)

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ARQ-1801) @Before not called with arquillian-junit-standalone

by Aslak Knutsen (JIRA)

[ https://issues.jboss.org/browse/ARQ-1801?page=com.atlassian.jira.plugin.s... ] Aslak Knutsen updated ARQ-1801: ------------------------------- Fix Version/s: 1.1.5.Final > @Before not called with arquillian-junit-standalone > --------------------------------------------------- > > Key: ARQ-1801 > URL: https://issues.jboss.org/browse/ARQ-1801 > Project: Arquillian > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 1.1.4.Final > Reporter: Thomas Diesler > Fix For: 1.1.5.Final > > > When using > {code} > <dependency> > <groupId>org.jboss.arquillian.junit</groupId> > <artifactId>arquillian-junit-standalone</artifactId> > <version>1.1.4.Final</version> > </dependency> > {code} > @BeforeClass and @Before are not called. > Using arquillian-junit-container they are. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ARQ-1801) @Before not called with arquillian-junit-standalone

by Thomas Diesler (JIRA)

[ https://issues.jboss.org/browse/ARQ-1801?page=com.atlassian.jira.plugin.s... ] Thomas Diesler updated ARQ-1801: -------------------------------- Affects Version/s: 1.1.4.Final > @Before not called with arquillian-junit-standalone > --------------------------------------------------- > > Key: ARQ-1801 > URL: https://issues.jboss.org/browse/ARQ-1801 > Project: Arquillian > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 1.1.4.Final > Reporter: Thomas Diesler > > When using > {code} > <dependency> > <groupId>org.jboss.arquillian.junit</groupId> > <artifactId>arquillian-junit-standalone</artifactId> > <version>1.1.4.Final</version> > </dependency> > {code} > @BeforeClass and @Before are not called. > Using arquillian-junit-container they are. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ARQ-1801) @Before not called with arquillian-junit-standalone

by Thomas Diesler (JIRA)

Thomas Diesler created ARQ-1801: ----------------------------------- Summary: @Before not called with arquillian-junit-standalone Key: ARQ-1801 URL: https://issues.jboss.org/browse/ARQ-1801 Project: Arquillian Issue Type: Bug Security Level: Public (Everyone can see) Reporter: Thomas Diesler When using {code} <dependency> <groupId>org.jboss.arquillian.junit</groupId> <artifactId>arquillian-junit-standalone</artifactId> <version>1.1.4.Final</version> </dependency> {code} @BeforeClass and @Before are not called. Using arquillian-junit-container they are. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ARQ-866) Allow catalina.base to be configured separately from catalina.home in the Tomcat managed adapters

by Aslak Knutsen (JIRA)

[ https://issues.jboss.org/browse/ARQ-866?page=com.atlassian.jira.plugin.sy... ] Aslak Knutsen updated ARQ-866: ------------------------------ Status: Resolved (was: Pull Request Sent) Assignee: Stephen Coy Resolution: Done pushed upstream; https://github.com/arquillian/arquillian-container-tomcat/commit/e6031154... > Allow catalina.base to be configured separately from catalina.home in the Tomcat managed adapters > ------------------------------------------------------------------------------------------------- > > Key: ARQ-866 > URL: https://issues.jboss.org/browse/ARQ-866 > Project: Arquillian > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: Tomcat Containers > Affects Versions: tomcat_1.0.0.CR3 > Reporter: Dan Allen > Assignee: Stephen Coy > Fix For: tomcat_1.0.0.Final > > > The Tomcat managed container adapter assumes that catalina.base is the same as catalina.home. > {code} > String absolutePath = new File(CATALINA_HOME).getAbsolutePath(); > ... > cmd.add("-Dcatalina.base=" + absolutePath); > cmd.add("-Dcatalina.home=" + absolutePath); > {code} > However, this is not necessary true. For instance, when using Tomcat from Eclipse, the catalina.base (which includes the configuration files) is managed inside the Eclipse workspace. This allows the developer to modify Tomcat settings without affecting the system installation. > The fix for this problem is to add a configuration property named "catalinaBase" and honor if it's set when building the startup script. > This affects all the Tomcat managed containers (5, 6 and 7). -- This message was sent by Atlassian JIRA (v6.2.6#6264)

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ARQ-866) Allow catalina.base to be configured separately from catalina.home in the Tomcat managed adapters

by Aslak Knutsen (JIRA)

[ https://issues.jboss.org/browse/ARQ-866?page=com.atlassian.jira.plugin.sy... ] Aslak Knutsen updated ARQ-866: ------------------------------ Fix Version/s: tomcat_1.0.0.Final > Allow catalina.base to be configured separately from catalina.home in the Tomcat managed adapters > ------------------------------------------------------------------------------------------------- > > Key: ARQ-866 > URL: https://issues.jboss.org/browse/ARQ-866 > Project: Arquillian > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: Tomcat Containers > Affects Versions: tomcat_1.0.0.CR3 > Reporter: Dan Allen > Fix For: tomcat_1.0.0.Final > > > The Tomcat managed container adapter assumes that catalina.base is the same as catalina.home. > {code} > String absolutePath = new File(CATALINA_HOME).getAbsolutePath(); > ... > cmd.add("-Dcatalina.base=" + absolutePath); > cmd.add("-Dcatalina.home=" + absolutePath); > {code} > However, this is not necessary true. For instance, when using Tomcat from Eclipse, the catalina.base (which includes the configuration files) is managed inside the Eclipse workspace. This allows the developer to modify Tomcat settings without affecting the system installation. > The fix for this problem is to add a configuration property named "catalinaBase" and honor if it's set when building the startup script. > This affects all the Tomcat managed containers (5, 6 and 7). -- This message was sent by Atlassian JIRA (v6.2.6#6264)

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ARQ-1800) SQL scripts are loaded with the default charset

by Bartosz Majsak (JIRA)

[ https://issues.jboss.org/browse/ARQ-1800?page=com.atlassian.jira.plugin.s... ] Bartosz Majsak updated ARQ-1800: -------------------------------- Affects Version/s: persistence_1.0.0.Alpha7 > SQL scripts are loaded with the default charset > ----------------------------------------------- > > Key: ARQ-1800 > URL: https://issues.jboss.org/browse/ARQ-1800 > Project: Arquillian > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Extension - Persistence > Affects Versions: persistence_1.0.0.Alpha7 > Reporter: jean-françois Lefebvre > Assignee: Bartosz Majsak > > SQLSripts are loaded with the default plateform charset. > Could you please add a property like this : > <extension qualifier="persistence"> > <property name="defaultEncoding">XXX</property> > </extension> > to set the default scripts encoding. > see org.jboss.arquillian.persistence.script.ScriptLoader > reader = new BufferedReader(new InputStreamReader(inputStream)); -- This message was sent by Atlassian JIRA (v6.2.6#6264)

10 years, 6 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

arquillian-issues June 2014