January 2012 - arquillian-issues - Jboss List Archives

[JBoss JIRA] (ARQ-630) The default charset is used to encode the HTTP BASIC AUTH credentials string into a sequence of bytes. ISO-8859-1 should be used for Tomcat

by Vineet Reynolds (Created) (JIRA)

The default charset is used to encode the HTTP BASIC AUTH credentials string into a sequence of bytes. ISO-8859-1 should be used for Tomcat ------------------------------------------------------------------------------------------------------------------------------------------- Key: ARQ-630 URL: https://issues.jboss.org/browse/ARQ-630 Project: Arquillian Issue Type: Bug Security Level: Public (Everyone can see) Components: Tomcat Containers Reporter: Vineet Reynolds Assignee: Vineet Reynolds Tomcat decodes the Authorization HTTP header containing the HTTP BASIC authentication credentials, using the ISO-8859-1 charset. On the contrary, Arquillian uses {{Charset.defaultCharset}} to encode the supplied credentials, before Base64 encoding the resulting byte array. This can result in a 401 error, when accessing the manager application on Tomcat; the failure will occur when the credentials contain characters that are encoded differently in ISO-8859-1 and the default charset of the environment. For example, if the default charset is UTF-8, then credentials containing _ö_ will not be accepted by Tomcat as _ö_ is encoded as 0xC3 0xB6 in UTF-8 and 0xF6 in ISO-8859-1. The suggested fix is to use ISO-8859-1 in {{CommonTomcatManager.constructHttpBasicAuthHeader()}} as listed: {code:java} // Set up an authorization header with our credentials String credentials = configuration.getUser() + ":" + configuration.getPass(); return "Basic " + new String(Base64.encodeBase64(credentials.getBytes(Charset.forName("ISO-8859-1"))), Charset.defaultCharset()); {code} instead of the existing {code:java} // Set up an authorization header with our credentials String credentials = configuration.getUser() + ":" + configuration.getPass(); return "Basic " + new String(Base64.encodeBase64(credentials.getBytes(Charset.defaultCharset())), Charset.defaultCharset()); {code} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 1 month

4
5
0 / 0

[JBoss JIRA] Created: (ARQ-476) Support portOffset in JBoss ContainerConfiguration

by Aslak Knutsen (JIRA)

Support portOffset in JBoss ContainerConfiguration -------------------------------------------------- Key: ARQ-476 URL: https://issues.jboss.org/browse/ARQ-476 Project: Arquillian Issue Type: Feature Request Security Level: Public (Everyone can see) Components: JBoss Containers Reporter: Aslak Knutsen Fix For: jbossas_1.0.0.CR1 The JBoss Configuration should understand the jboss port set rules. <property name="portSet">ports-01</property> Should set -Djboss.service.binding.set for the managed container + rmi/httpPort and could set the jndi port for Remote -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 1 month

1
4
0 / 0

[JBoss JIRA] (ARQ-717) JBoss AS managed 6 container should support setting partition

by Marek Schmidt (Created) (JIRA)

JBoss AS managed 6 container should support setting partition ------------------------------------------------------------- Key: ARQ-717 URL: https://issues.jboss.org/browse/ARQ-717 Project: Arquillian Issue Type: Feature Request Security Level: Public (Everyone can see) Components: JBoss Containers Affects Versions: jbossas_1.0.0.CR2 Reporter: Marek Schmidt Assignee: Marek Schmidt Currently the jbossas-managed-6 container sets the partition with server.setPartition(Long.toHexString(System.currentTimeMillis())); which makes clustering in a group very unlikely to work. The container should allow setting the partition in configuration. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 1 month

4
7
0 / 0

[JBoss JIRA] Created: (ARQ-146) Create a DeployableContainer integration for Resin

by Aslak Knutsen (JIRA)

Create a DeployableContainer integration for Resin --------------------------------------------------- Key: ARQ-146 URL: https://jira.jboss.org/browse/ARQ-146 Project: Arquillian Issue Type: Feature Request Components: Resin Container Reporter: Aslak Knutsen Create support for Resin -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 1 month

1
7
0 / 0

[JBoss JIRA] (ARQ-652) Extract Persistence Events to SPI

by Aslak Knutsen (Created) (JIRA)

Extract Persistence Events to SPI --------------------------------- Key: ARQ-652 URL: https://issues.jboss.org/browse/ARQ-652 Project: Arquillian Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Extension - Persistence Affects Versions: persistence_1.0.0.Alpha1 Reporter: Aslak Knutsen Fix For: persistence_1.0.0.next Move BeforeStartTransaction, AfterStartTransaction , etc into a SPI module that other Extensions can depend on. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 2 months

3
2
0 / 0

[JBoss JIRA] (ARQ-648) Implement @ArquillianResource Map<URL> for multi-container configuration.

by Ondrej Zizka (Created) (JIRA)

Implement @ArquillianResource Map<URL> for multi-container configuration. ------------------------------------------------------------------------- Key: ARQ-648 URL: https://issues.jboss.org/browse/ARQ-648 Project: Arquillian Issue Type: Feature Request Security Level: Public (Everyone can see) Reporter: Ondrej Zizka Would work like @ArquillianResource URL url; Only would fill all container infos. Key would be container's qualifier. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 2 months

6
5
0 / 0

[JBoss JIRA] (ARQ-696) Last test's standard output is not recorded - probably missing flush() ?

by Ondrej Zizka (Created) (JIRA)

Last test's standard output is not recorded - probably missing flush() ? ------------------------------------------------------------------------ Key: ARQ-696 URL: https://issues.jboss.org/browse/ARQ-696 Project: Arquillian Issue Type: Bug Security Level: Public (Everyone can see) Components: Base Implementation Affects Versions: 1.0.0.CR5 Reporter: Ondrej Zizka When a suite of tests is run, the last test's stdout is not stored in ...-output.txt. It's always the last test, whichever it happens to be. It seems like Arquillian forgets to call a flush or something, and Surefire, not having anything in buffer, creates an empty file. Steps to reproduce with JBoss AS 7: -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 2 months

5
4
0 / 0

[JBoss JIRA] (ARQ-690) Verify ability to run under a security manager (evt. create a policy file)

by Ondrej Zizka (Created) (JIRA)

Verify ability to run under a security manager (evt. create a policy file) -------------------------------------------------------------------------- Key: ARQ-690 URL: https://issues.jboss.org/browse/ARQ-690 Project: Arquillian Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Base Implementation, JBoss Containers Affects Versions: 1.0.0.CR6 Reporter: Ondrej Zizka Assignee: Aslak Knutsen Verify whether Arquillian is able to run under security manager. Presumably, we need to create a security policy file for arquillian. Test with JBoss AS7 testsuite, using -Dsecurity.manager [ -Dsecurity.policy=<path>] - see https://docs.jboss.org/author/display/AS71/AS+7+Integration+Testsuite+Use... . -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 2 months

3
5
0 / 0

[JBoss JIRA] Created: (ARQ-347) Seam 2 integration

by Michael Schuetz (JIRA)

Seam 2 integration ------------------ Key: ARQ-347 URL: https://issues.jboss.org/browse/ARQ-347 Project: Arquillian Issue Type: Feature Request Reporter: Michael Schuetz This needs to be done: * create framework-integration * implement AuxiliaryArchiveAppender * implement TestEnricher -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 2 months

7
15
0 / 0

[JBoss JIRA] Created: (ARQ-602) Maven plugin - exception on shutdown

by Jozef Hartinger (JIRA)

Maven plugin - exception on shutdown ------------------------------------ Key: ARQ-602 URL: https://issues.jboss.org/browse/ARQ-602 Project: Arquillian Issue Type: Bug Security Level: Public (Everyone can see) Components: Maven Plugin Affects Versions: maven_1.0.0.Alpha1 Environment: JBoss AS 7.0.1.Final Reporter: Jozef Hartinger Fix For: maven_1.0.0.next I am getting the following exception after running arquillian:run with the jbossas-managed-7 container and using Ctrl+c to stop the server once it's started. Note that the application remains deployed and a subsequent attemp to run mvn arquillian:run causes duplicate deployment failure. ^Cjava.lang.IllegalStateException: Shutdown in progress at java.lang.ApplicationShutdownHooks.remove(ApplicationShutdownHooks.java:55) at java.lang.Runtime.removeShutdownHook(Runtime.java:220) at org.jboss.as.arquillian.container.managed.ManagedDeployableContainer.stopInternal(ManagedDeployableContainer.java:155) at org.jboss.as.arquillian.container.CommonDeployableContainer.stop(CommonDeployableContainer.java:76) at org.jboss.arquillian.container.impl.client.container.ContainerLifecycleController$6.perform(ContainerLifecycleController.java:163) at org.jboss.arquillian.container.impl.client.container.ContainerLifecycleController$6.perform(ContainerLifecycleController.java:153) at org.jboss.arquillian.container.impl.client.container.ContainerLifecycleController.forContainer(ContainerLifecycleController.java:186) at org.jboss.arquillian.container.impl.client.container.ContainerLifecycleController.stopContainer(ContainerLifecycleController.java:152) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:90) 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.container.impl.client.ContainerDeploymentContextHandler.createContainerContext(ContainerDeploymentContextHandler.java:57) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:90) at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88) at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:134) at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:114) at org.jboss.arquillian.maven.Utils.stop(Utils.java:64) at org.jboss.arquillian.maven.Run$1.run(Run.java:66) -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 2 months

2
2
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

arquillian-issues January 2012