November 2010 - arquillian-issues

[JBoss JIRA] Created: (ARQ-323) Implement a GlassFish 3.1 remote container based on REST API

by Dan Allen (JIRA)

Implement a GlassFish 3.1 remote container based on REST API ------------------------------------------------------------ Key: ARQ-323 URL: https://jira.jboss.org/browse/ARQ-323 Project: Arquillian Issue Type: Feature Request Components: GlassFish Containers Affects Versions: 1.0.0.Alpha4 Reporter: Dan Allen Priority: Minor The GlassFish 3 remote container is based on JMX. GlassFish 3.1 has a much more powerful REST administration API. This API should be leveraged to create the GlassFish 3.1 remote and managed container. @see http://wikis.sun.com/display/GlassFish/V3.1RESTfulApiOnePager @see http://blogs.steeplesoft.com/2010/08/glassfish-administration-the-rest-of... -- 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

13 years, 2 months

3
8
0 / 0

[JBoss JIRA] Created: (ARQ-290) performence/pom.xml references WELD-1.0.1

by steven verborgh (JIRA)

performence/pom.xml references WELD-1.0.1 ----------------------------------------- Key: ARQ-290 URL: https://jira.jboss.org/browse/ARQ-290 Project: Arquillian Issue Type: Bug Components: Build Infrastructure Environment: Mac OS, Maven 3, using jboss-repository-public as in JBoss maven Getting started wiki Reporter: steven verborgh build fails with: [ERROR] The build could not read 1 project -> [Help 1] [ERROR] The project org.jboss.arquillian.extension:arquillian-performance:1.0.0-SNAPSHOT (/Users/verborghs/Documents/Repositories/arquilian/arquillian/arquillian/extensions/performance/pom.xml) has 4 errors [ERROR] Non-resolvable import POM org.jboss.weld:weld-core-bom:1.0.2-SNAPSHOT: Failed to resolve POM for org.jboss.weld:weld-core-bom:1.0.2-SNAPSHOT due to The following artifacts could not be resolved: org.jboss.weld:weld-core-bom:pom:1.0.2-SNAPSHOT: Could not find artifact org.jboss.weld:weld-core-bom:pom:1.0.2-SNAPSHOT in jboss-public-repository-group (https://repository.jboss.org/nexus/content/groups/public-jboss/, releases=true, snapshots=true, managed=false) @ line 105, column 26 -> [Help 2] [ERROR] 'dependencies.dependency.version' for org.jboss.weld:weld-core:jar is missing. @ line 84, column 25 [ERROR] 'dependencies.dependency.version' for org.jboss.weld:weld-api:jar is missing. @ line 88, column 25 [ERROR] 'dependencies.dependency.version' for org.slf4j:slf4j-simple:jar is missing. @ line 92, column 25 [ERROR] [ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch. [ERROR] Re-run Maven using the -X switch to enable full debug logging. [ERROR] [ERROR] For more information about the errors and possible solutions, please read the following articles: [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/ProjectBuildingException [ERROR] [Help 2] http://cwiki.apache.org/confluence/display/MAVEN/UnresolvableModelException Solved by replacing 1.0.2-SNAPSHOT which is no longer in https://repository.jboss.org/nexus/content/groups/public-jboss/ to 1.1.0-SNAPSHOT -- 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

13 years, 2 months

3
10
0 / 0

[JBoss JIRA] Created: (ARQ-211) Protocol Servlet should be automatically registered for Tomcat Embedded 6

by Dan Allen (JIRA)

Protocol Servlet should be automatically registered for Tomcat Embedded 6 ------------------------------------------------------------------------- Key: ARQ-211 URL: https://jira.jboss.org/browse/ARQ-211 Project: Arquillian Issue Type: Bug Components: Tomcat Containers Affects Versions: 1.0.0.Alpha3 Reporter: Dan Allen Priority: Minor Fix For: 1.0.0.Beta1 Currently, the developer must add the protocol Servlet to the web.xml in the test archive manually. In containers that support Servlet 3.0, the protocol Servlet is defined in a web-fragment.xml. We need to find another way to register the protocol Servlet in pre-Servlet 3.0 containers. -- 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

13 years, 2 months

2
4
0 / 0

[JBoss JIRA] Created: (ARQ-217) Servlet 2.5 Protocol should support Application WebArchives

by Aslak Knutsen (JIRA)

Servlet 2.5 Protocol should support Application WebArchives ----------------------------------------------------------- Key: ARQ-217 URL: https://jira.jboss.org/browse/ARQ-217 Project: Arquillian Issue Type: Bug Reporter: Aslak Knutsen Currently when using the Servlet 2.5 for EE 5 containers, the Protocol packager will throw an Exception if you try to deploy a WebArchive. It does not support web.xml merging. Use the Descriptors library to append the required Servlet/Mappings. -- 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

13 years, 2 months

1
7
0 / 0

[JBoss JIRA] Created: (ARQ-326) Track JBoss AS CR1

by Aslak Knutsen (JIRA)

Track JBoss AS CR1 ------------------ Key: ARQ-326 URL: https://jira.jboss.org/browse/ARQ-326 Project: Arquillian Issue Type: Feature Request Reporter: Aslak Knutsen Priority: Minor Fix For: 1.0.0.Beta1 http://community.jboss.org/wiki/AS600CR1StatusExecutiveSummary -- 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

13 years, 2 months

1
4
0 / 0

[JBoss JIRA] Created: (ARQ-289) All poms refere to old svn repo, update to git

by Aslak Knutsen (JIRA)

All poms refere to old svn repo, update to git ---------------------------------------------- Key: ARQ-289 URL: https://jira.jboss.org/browse/ARQ-289 Project: Arquillian Issue Type: Bug Reporter: Aslak Knutsen Fix For: 1.0.0.Beta1 -- 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

13 years, 2 months

1
3
0 / 0

[JBoss JIRA] Created: (ARQ-168) Use Bean Validation on container configuration properties

by Dan Allen (JIRA)

Use Bean Validation on container configuration properties --------------------------------------------------------- Key: ARQ-168 URL: https://jira.jboss.org/browse/ARQ-168 Project: Arquillian Issue Type: Feature Request Components: Configuration Affects Versions: 1.0.0.Alpha2 Reporter: Dan Allen The container needs to ensure that the user has supplied sane configuration values, or else risk blowing up in weird and unpredictable ways. Rather than doing these laborious checks manually (and possibly only partially), Bean Validation should be used to enforce the values fall with a value range or adhere to a required syntax. -- 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

13 years, 2 months

3
12
0 / 0

[JBoss JIRA] Created: (ARQ-259) Provide xsd for all containers and for core

by Pete Muir (JIRA)

Provide xsd for all containers and for core ------------------------------------------- Key: ARQ-259 URL: https://jira.jboss.org/browse/ARQ-259 Project: Arquillian Issue Type: Task Components: Configuration Affects Versions: 1.0.0.Alpha3 Reporter: Pete Muir Priority: Critical This will be a major usability improvement -- 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

13 years, 2 months

2
5
0 / 0

[JBoss JIRA] Created: (ARQ-153) Protocol configuration element should be separate from Container

by Aslak Knutsen (JIRA)

Protocol configuration element should be separate from Container ---------------------------------------------------------------- Key: ARQ-153 URL: https://jira.jboss.org/browse/ARQ-153 Project: Arquillian Issue Type: Feature Request Components: Configuration Affects Versions: 1.0.0.Alpha2 Reporter: Aslak Knutsen A Contianer should be able to run with any of the support Protocols for communication with TestCase running inside the container. This needs to be configurable in a common way. Currently Servlet Protocol configuration is stuck in the specific Containers who use it, this needs to be extracted. e.g. {code:XML} <arquillian xmlns="http://jboss.com/arquillian" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:jboss="urn:arq:org.jboss.arquillian.jbossas.remote60" xmlns:servlet="urn:arq:org.jboss.arquillian.protocol.servlet" xmlns:jmx="urn:arq:org.jboss.arquillian.protocol.jmx" xmlns:jndi="urn:arq:org.jboss.arquillian.jndi"> <jboss:container id="jbossTest"> <localDeploymentBindAddress>my.domain</localDeploymentBindAddress> <servlet:protocol> <remoteServerAddress>remote.server</remoteServerAddress> <remoteServerHttpPort>8181</remoteServerHttpPort> </servlet:protocol> <jndi:protocol>  <javaNamingProviderUrl>jnp://remote.server:1099</javaNamingProviderUrl> <javaNamingFactoryInitial>org.jnp.interfaces.NamingContextFactory</javaNamingFactoryInitial> <javaNamingFactoryUrlPkgs>org.jboss.naming\:org.jnp.interfaces</javaNamingFactoryUrlPkgs> </jndi:protocol> </jboss:container> <jboss:container id="jbossStage"> <localDeploymentBindAddress>my.domain</localDeploymentBindAddress> <jmx:protocol> <serviceUrl>service:jmx:rmi:///jndi/rmi://localhost:1099/</serviceUrl> </jmx:protocol> <jndi:protocol> <javaNamingProviderUrl>jnp://remote.server:1099</javaNamingProviderUrl> <javaNamingFactoryInitial>org.jnp.interfaces.NamingContextFactory</javaNamingFactoryInitial> <javaNamingFactoryUrlPkgs>org.jboss.naming\:org.jnp.interfaces</javaNamingFactoryUrlPkgs> </jndi:protocol> </jboss:container> </arquillian> {code} -- 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

13 years, 2 months

3
10
0 / 0

[JBoss JIRA] Created: (ARQ-292) Enforcing Maven 3 in build/pom.xml does not seem to work...

by Aslak Knutsen (JIRA)

Enforcing Maven 3 in build/pom.xml does not seem to work... ----------------------------------------------------------- Key: ARQ-292 URL: https://jira.jboss.org/browse/ARQ-292 Project: Arquillian Issue Type: Bug Reporter: Aslak Knutsen Assignee: Aslak Knutsen Fix For: 1.0.0.Beta1 -- 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

13 years, 2 months

1
3
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

arquillian-issues November 2010