June 2014 - arquillian-issues - Jboss List Archives

[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 commented on ARQ-1800: ------------------------------------- Thanks for the feature request. Of course this will be handy feature. Shall we consider UTF-8 as a default? Moreover would you be interested in contributing this improvement? That would be simply awesome. > 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 > Fix For: persistence_1.0.0.next > > > 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

[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: -------------------------------- Fix Version/s: persistence_1.0.0.next > 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 > Fix For: persistence_1.0.0.next > > > 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

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

by jean-françois Lefebvre (JIRA)

jean-françois Lefebvre created ARQ-1800: ------------------------------------------- Summary: 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 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

[JBoss JIRA] (ARQ-600) Improve Tomcat codebase - Managed

by Aslak Knutsen (JIRA)

[ https://issues.jboss.org/browse/ARQ-600?page=com.atlassian.jira.plugin.sy... ] Aslak Knutsen updated ARQ-600: ------------------------------ Assignee: Stephen Coy > Improve Tomcat codebase - Managed > --------------------------------- > > Key: ARQ-600 > URL: https://issues.jboss.org/browse/ARQ-600 > Project: Arquillian > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Tomcat Containers > Reporter: Aslak Knutsen > Assignee: Stephen Coy > Fix For: tomcat_1.0.0.Final > > > After the Tomcat Container code clean up, tomcat-common, it seems all the Managed Tomcat containers are identical both in impl and configuration. > We can create a similar tomcat-common-managed that will have the common parts between the different versions. > {note} > If Tomcat Managed 5.5, 6 and 7 are identical, why do we have 3 versions? > {note} -- This message was sent by Atlassian JIRA (v6.2.6#6264)

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ARQ-600) Improve Tomcat codebase - Managed

by Stephen Coy (JIRA)

[ https://issues.jboss.org/browse/ARQ-600?page=com.atlassian.jira.plugin.sy... ] Stephen Coy commented on ARQ-600: --------------------------------- I noticed this while working on ARQ-866. Please assign this JIRA to me and I'll do the refactor > Improve Tomcat codebase - Managed > --------------------------------- > > Key: ARQ-600 > URL: https://issues.jboss.org/browse/ARQ-600 > Project: Arquillian > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Tomcat Containers > Reporter: Aslak Knutsen > Fix For: tomcat_1.0.0.Final > > > After the Tomcat Container code clean up, tomcat-common, it seems all the Managed Tomcat containers are identical both in impl and configuration. > We can create a similar tomcat-common-managed that will have the common parts between the different versions. > {note} > If Tomcat Managed 5.5, 6 and 7 are identical, why do we have 3 versions? > {note} -- 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 Stephen Coy (JIRA)

[ https://issues.jboss.org/browse/ARQ-866?page=com.atlassian.jira.plugin.sy... ] Stephen Coy commented on ARQ-866: --------------------------------- Support for TC 5.5 and TC 7 now included > 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 > > 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-1191) Tomcat Embedded 6 undeploy(archive) issue

by Aslak Knutsen (JIRA)

[ https://issues.jboss.org/browse/ARQ-1191?page=com.atlassian.jira.plugin.s... ] Aslak Knutsen resolved ARQ-1191. -------------------------------- Assignee: Aslak Knutsen Resolution: Done > Tomcat Embedded 6 undeploy(archive) issue > ----------------------------------------- > > Key: ARQ-1191 > URL: https://issues.jboss.org/browse/ARQ-1191 > Project: Arquillian > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Tomcat Containers > Affects Versions: tomcat_1.0.0.CR4 > Environment: Tomcat-embedded-6 > Reporter: George Vagenas > Assignee: Aslak Knutsen > Priority: Critical > Fix For: tomcat_1.0.0.Final > > Attachments: arquillian-container-tomcat.patch, SimpleArqTest.zip > > > Having two test classes that extend an abstract class that provides the deployment archive (actually the fact that they extend an abstract class is insignificant, the important point here is that the deployment archive name is the same). > When the test classes run individually pass the test. When these two test classes combined in a test suite, the first only pass and the second always fails. > @RunWith(Suite.class) > @SuiteClasses({ > RegisteredEchoServletTestCase.class, > RegisteredEchoServletTestCase2.class > }) > public class MyTestSuite { > } > Find attached @RunWith(Suite.class) > @SuiteClasses({ > RegisteredEchoServletTestCase.class, > RegisteredEchoServletTestCase2.class > }) > public class MyTestSuite { > } > Issue exists only on tomcat 6 container. I run the same test suite against tomcat-embedded-7 with success. > George -- This message was sent by Atlassian JIRA (v6.2.6#6264)

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ARQ-1799) Remove dependency on common-codecs

by Aslak Knutsen (JIRA)

[ https://issues.jboss.org/browse/ARQ-1799?page=com.atlassian.jira.plugin.s... ] Aslak Knutsen resolved ARQ-1799. -------------------------------- Assignee: Aslak Knutsen Resolution: Done > Remove dependency on common-codecs > ---------------------------------- > > Key: ARQ-1799 > URL: https://issues.jboss.org/browse/ARQ-1799 > Project: Arquillian > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Tomcat Containers > Affects Versions: tomcat_1.0.0.CR6 > Reporter: Aslak Knutsen > Assignee: Aslak Knutsen > Fix For: tomcat_1.0.0.Final > > > Since client side can depend on Common-Codec and cause version conflicts with the Container, remove the external dependency and move Base64 encoding class internally. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ARQ-701) Tomcat containers are not able to start after begin stop (AddressAlready in use)

by Aslak Knutsen (JIRA)

[ https://issues.jboss.org/browse/ARQ-701?page=com.atlassian.jira.plugin.sy... ] Aslak Knutsen resolved ARQ-701. ------------------------------- Assignee: Aslak Knutsen Resolution: Done > Tomcat containers are not able to start after begin stop (AddressAlready in use) > -------------------------------------------------------------------------------- > > Key: ARQ-701 > URL: https://issues.jboss.org/browse/ARQ-701 > Project: Arquillian > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Tomcat Containers > Affects Versions: tomcat_1.0.0.CR2 > Reporter: Aslak Knutsen > Assignee: Aslak Knutsen > Fix For: tomcat_1.0.0.Final > > > Setting a embedded Tomcat 7 container to manual control mode and calling, start/stop/start cause Address Already in use Exception. > stop should call tomcat.destroy > (possible other tomcat versions as well, investigate) -- This message was sent by Atlassian JIRA (v6.2.6#6264)

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ARQ-1799) Remove dependency on common-codecs

by Aslak Knutsen (JIRA)

[ https://issues.jboss.org/browse/ARQ-1799?page=com.atlassian.jira.plugin.s... ] Aslak Knutsen updated ARQ-1799: ------------------------------- Fix Version/s: tomcat_1.0.0.Final > Remove dependency on common-codecs > ---------------------------------- > > Key: ARQ-1799 > URL: https://issues.jboss.org/browse/ARQ-1799 > Project: Arquillian > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Tomcat Containers > Affects Versions: tomcat_1.0.0.CR6 > Reporter: Aslak Knutsen > Fix For: tomcat_1.0.0.Final > > > Since client side can depend on Common-Codec and cause version conflicts with the Container, remove the external dependency and move Base64 encoding class internally. -- 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