October 2011 - arquillian-issues - Jboss List Archives

[JBoss JIRA] Created: (ARQ-423) Create a DeployableContainer integration for remote WAS V8.0

by Gerhard Poul (JIRA)

Create a DeployableContainer integration for remote WAS V8.0 ------------------------------------------------------------ Key: ARQ-423 URL: https://issues.jboss.org/browse/ARQ-423 Project: Arquillian Issue Type: Feature Request Security Level: Public (Everyone can see) Components: WebSphere Containers Reporter: Gerhard Poul Priority: Optional Create a DeployableContainer integration for remote WebSphere Application Server V8.0 which will eGA June 17, 2011, and GA July 22, 2011. - Announcement letter: http://www-01.ibm.com/common/ssi/cgi-bin/ssialias?infotype=AN&subtype=CA&... -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 8 months

3
6
0 / 0

[JBoss JIRA] Created: (ARQ-424) Create a DeployableContainer integration for embeddable WAS V8.0

by Gerhard Poul (JIRA)

Create a DeployableContainer integration for embeddable WAS V8.0 ---------------------------------------------------------------- Key: ARQ-424 URL: https://issues.jboss.org/browse/ARQ-424 Project: Arquillian Issue Type: Feature Request Security Level: Public (Everyone can see) Components: WebSphere Containers Reporter: Gerhard Poul Priority: Optional Create a DeployableContainer integration for remote WebSphere Application Server V8.0 which will eGA June 17, 2011, and GA July 22, 2011. - Announcement letter: http://www-01.ibm.com/common/ssi/cgi-bin/ssialias?infotype=AN&subtype=CA&... -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 8 months

2
7
0 / 0

[JBoss JIRA] (ARQ-626) Arquillian test with asynchronous components (Asynchonous EJB or JMS) in glassfish -embedded (and surely -remote)

by Hugo de Paix de Coeur (Created) (JIRA)

Arquillian test with asynchronous components (Asynchonous EJB or JMS) in glassfish -embedded (and surely -remote) ----------------------------------------------------------------------------------------------------------------- Key: ARQ-626 URL: https://issues.jboss.org/browse/ARQ-626 Project: Arquillian Issue Type: Bug Security Level: Public (Everyone can see) Components: GlassFish Containers Affects Versions: 1.0.0.Alpha5 Environment: arquillian-glassfish-embedded-3.1, arquillian-junit-1.0.0.Alpha5 Reporter: Hugo de Paix de Coeur When we use Asynchronous EJB or MDB with JMS in our tests, the test leave and it seems the container is undeployed or something ... It results in async always running code complaining about undeployed or stopped container for subsequents EJB calls and so on ... Am I wrong ? -- 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

12 years, 8 months

5
5
0 / 0

[JBoss JIRA] Created: (ARQ-593) glassfish-resources.xml (application scoped resources) not loaded with glassfish-remote

by F L (JIRA)

glassfish-resources.xml (application scoped resources) not loaded with glassfish-remote --------------------------------------------------------------------------------------- Key: ARQ-593 URL: https://issues.jboss.org/browse/ARQ-593 Project: Arquillian Issue Type: Bug Security Level: Public (Everyone can see) Components: GlassFish Containers Affects Versions: 1.0.0.Alpha5 Environment: MacOSX Lion, Maven 3, arquillian 1.0.0.Alpha5, arquillian-glassfish-remote-3.1 1.0.0.Alpha5, Glassfish 3.1.1, Java 1.6.0_26 64bits Reporter: F L An EJB Jar with an glassfish-resources.xml references an jdbc/rt JNDI resource. It's correctly read as java:app/jdbc/rt by the EJB package generated by maven but failed with Arquillian/ShrinkWrap targeting glassfish-remote-3.1 ShrinkWrap : JavaArchive archive = ShrinkWrap.create(JavaArchive.class, "Project-ejb-1.0.0-SNAPSHOT.jar") .addPackages(true, "com.company.project.ejb.entities") .addPackages(true, "com.company.project.ejb.model") .addAsManifestResource("META-INF/ejb-jar.xml", ArchivePaths.create("ejb-jar.xml")) .addAsManifestResource("META-INF/sun-ejb-jar.xml", ArchivePaths.create("sun-ejb-jar.xml")) .addAsManifestResource("META-INF/glassfish-resources-test.xml", ArchivePaths.create("glassfish-resources.xml")) .addAsManifestResource("META-INF/persistence-test.xml", ArchivePaths.create("persistence.xml")); persistence.xml : <?xml version="1.0" encoding="UTF-8"?> <persistence version="1.0" xmlns="http://java.sun.com/xml/ns/persistence" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://java.sun.com/xml/ns/persistence http://java.sun.com/xml/ns/persistence/persistence_1_0.xsd"> <persistence-unit name="RTUnit" transaction-type="JTA"> <provider>org.eclipse.persistence.jpa.PersistenceProvider</provider> <jta-data-source>java:app/jdbc/rt</jta-data-source> <exclude-unlisted-classes>false</exclude-unlisted-classes> </persistence-unit> </persistence> -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 8 months

3
7
0 / 0

[JBoss JIRA] Created: (ARQAJO-81) support for configurating arquillian.xml during runtime for matrix browser compability jobs

by Juraj Huska (JIRA)

support for configurating arquillian.xml during runtime for matrix browser compability jobs ------------------------------------------------------------------------------------------- Key: ARQAJO-81 URL: https://issues.jboss.org/browse/ARQAJO-81 Project: Arquillian Ajocado Issue Type: Feature Request Components: configuration Affects Versions: 1.0.0.CR1 Reporter: Juraj Huska Assignee: Juraj Huska Fix For: 1.0.0.CR1 Create support for configurating arquillian.xml during runtime for matrix browser compability jobs. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 8 months

3
12
0 / 0

[JBoss JIRA] (ARQ-628) Tomcat managed throws NullPointerException when AUT brings weld-servlet dependency

by Juraj Huska (Created) (JIRA)

Tomcat managed throws NullPointerException when AUT brings weld-servlet dependency ---------------------------------------------------------------------------------- Key: ARQ-628 URL: https://issues.jboss.org/browse/ARQ-628 Project: Arquillian Issue Type: Bug Security Level: Public (Everyone can see) Components: Tomcat Containers Affects Versions: tomcat_1.0.0.CR2 Environment: tomcat-managed-7 application - richfaces-showcase-4.1.0-20111011-M3-tomcat6.war Reporter: Juraj Huska I have encountered this issue when I was testing richfaces-showcase application. It seems that tomcat-managed-7 has problem with applications which bring own weld-servlet dependency. -- 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

12 years, 8 months

4
7
0 / 0

[JBoss JIRA] (ARQ-623) openshift - provide better way of detecting deployment

by Jozef Hartinger (Created) (JIRA)

openshift - provide better way of detecting deployment ------------------------------------------------------ Key: ARQ-623 URL: https://issues.jboss.org/browse/ARQ-623 Project: Arquillian Issue Type: Feature Request Security Level: Public (Everyone can see) Components: OpenShift Containers Affects Versions: openshift_1.0.0.Alpha1 Reporter: Jozef Hartinger Fix For: openshift_1.0.0.next Currently, org.jboss.arquillian.container.openshift.express.ping.DeploymentServlet is used to detect whether an archive being tested has been deployed yet. The DeploymentServlet uses calls to the AS7 management API. However, the DeploymentServlet does not act gracefully in cases when the application has not been deployed yet. Instead the operation causes the following stacktrace in the server log. Given the fact that arq is polling the server (stacktrace appears on every attempt), this can be very confusing to the end user. A stacktrace in the server log can easily lead her to the conclusion that the deployment was not successful even if it was. {noformat} 04:18:48,740 ERROR [org.jboss.as.controller] (http--127.1.30.1-8080-1) Operation ("read-resource") failed - address: ([("deployment" => "rest-tasks.war")]): java.util.NoSuchElementException: "deployment" => "rest-tasks.war" at org.jboss.as.controller.registry.BasicResource.requireChild(BasicResource.java:95) [jboss-as-controller-7.0.1.Final.jar:7.0.1.Final] at org.jboss.as.controller.ModelControllerImpl$RootResource.requireChild(ModelControllerImpl.java:423) [jboss-as-controller-7.0.1.Final.jar:7.0.1.Final] at org.jboss.as.controller.OperationContextImpl.readResource(OperationContextImpl.java:759) [jboss-as-controller-7.0.1.Final.jar:7.0.1.Final] at org.jboss.as.controller.operations.global.GlobalOperationHandlers$ReadResourceHandler.doExecute(GlobalOperationHandlers.java:151) [jboss-as-controller-7.0.1.Final.jar:7.0.1.Final] at org.jboss.as.controller.operations.global.GlobalOperationHandlers$AbstractMultiTargetHandler.execute(GlobalOperationHandlers.java:828) [jboss-as-controller-7.0.1.Final.jar:7.0.1.Final] at org.jboss.as.controller.OperationContextImpl.executeStep(OperationContextImpl.java:351) [jboss-as-controller-7.0.1.Final.jar:7.0.1.Final] at org.jboss.as.controller.OperationContextImpl.doCompleteStep(OperationContextImpl.java:298) [jboss-as-controller-7.0.1.Final.jar:7.0.1.Final] at org.jboss.as.controller.OperationContextImpl.completeStep(OperationContextImpl.java:223) [jboss-as-controller-7.0.1.Final.jar:7.0.1.Final] at org.jboss.as.controller.ModelControllerImpl$DefaultPrepareStepHandler.execute(ModelControllerImpl.java:350) [jboss-as-controller-7.0.1.Final.jar:7.0.1.Final] at org.jboss.as.controller.OperationContextImpl.executeStep(OperationContextImpl.java:351) [jboss-as-controller-7.0.1.Final.jar:7.0.1.Final] at org.jboss.as.controller.OperationContextImpl.doCompleteStep(OperationContextImpl.java:298) [jboss-as-controller-7.0.1.Final.jar:7.0.1.Final] at org.jboss.as.controller.OperationContextImpl.completeStep(OperationContextImpl.java:223) [jboss-as-controller-7.0.1.Final.jar:7.0.1.Final] at org.jboss.as.controller.ModelControllerImpl.execute(ModelControllerImpl.java:119) [jboss-as-controller-7.0.1.Final.jar:7.0.1.Final] at org.jboss.arquillian.container.openshift.express.ping.DeploymentServlet.deploymentExists(DeploymentServlet.java:51) [classes:] at org.jboss.arquillian.container.openshift.express.ping.DeploymentServlet.doGet(DeploymentServlet.java:34) [classes:] at javax.servlet.http.HttpServlet.service(HttpServlet.java:734) [jboss-servlet-api_3.0_spec-1.0.0.Final.jar:1.0.0.Final] at javax.servlet.http.HttpServlet.service(HttpServlet.java:847) [jboss-servlet-api_3.0_spec-1.0.0.Final.jar:1.0.0.Final] at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:329) [jbossweb-7.0.1.Final.jar:7.0.1.Final] at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:248) [jbossweb-7.0.1.Final.jar:7.0.1.Final] at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:275) [jbossweb-7.0.1.Final.jar:7.0.1.Final] at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:161) [jbossweb-7.0.1.Final.jar:7.0.1.Final] at org.jboss.as.web.security.SecurityContextAssociationValve.invoke(SecurityContextAssociationValve.java:139) [jboss-as-web-7.0.1.Final.jar:7.0.1.Final] at org.jboss.as.web.NamingValve.invoke(NamingValve.java:57) [jboss-as-web-7.0.1.Final.jar:7.0.1.Final] at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:154) [jbossweb-7.0.1.Final.jar:7.0.1.Final] at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102) [jbossweb-7.0.1.Final.jar:7.0.1.Final] at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109) [jbossweb-7.0.1.Final.jar:7.0.1.Final] at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:362) [jbossweb-7.0.1.Final.jar:7.0.1.Final] at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:877) [jbossweb-7.0.1.Final.jar:7.0.1.Final] at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:667) [jbossweb-7.0.1.Final.jar:7.0.1.Final] at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:952) [jbossweb-7.0.1.Final.jar:7.0.1.Final] at java.lang.Thread.run(Thread.java:636) [:1.6.0_20] {noformat} -- 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

12 years, 8 months

2
1
0 / 0

[JBoss JIRA] Created: (ARQAJO-93) Update jboss-parent to version 6

by Lukáš Fryč (JIRA)

Update jboss-parent to version 6 -------------------------------- Key: ARQAJO-93 URL: https://issues.jboss.org/browse/ARQAJO-93 Project: Arquillian Ajocado Issue Type: Component Upgrade Components: build Affects Versions: 1.0.0.CR1 Reporter: Lukáš Fryč Assignee: Lukáš Fryč Fix For: 1.0.0.CR2 -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 8 months

2
1
0 / 0

[JBoss JIRA] Created: (ARQ-312) Add TabLibConfiguration to Jetty plus container

by Dan Allen (JIRA)

Add TabLibConfiguration to Jetty plus container ----------------------------------------------- Key: ARQ-312 URL: https://jira.jboss.org/browse/ARQ-312 Project: Arquillian Issue Type: Bug Components: Jetty Containers Affects Versions: 1.0.0.Alpha4 Reporter: Dan Allen Assignee: Dan Allen The TagLibConfiguration was left out of the context configurations in the Jetty containers. This was done to speed up loading. However, some frameworks, such as JSF, use TLD files to register listeners. So those are broken as a result. The TagLibConfiguration needs to be added, or the user needs to be allow to configure this support via the container configuration. -- 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

12 years, 8 months

3
7
0 / 0

[JBoss JIRA] Created: (ARQ-157) OpenEJB container needs CDI-API to run

by Aslak Knutsen (JIRA)

OpenEJB container needs CDI-API to run -------------------------------------- Key: ARQ-157 URL: https://jira.jboss.org/browse/ARQ-157 Project: Arquillian Issue Type: Bug Components: OpenEJB Containers Affects Versions: 1.0.0.Alpha2 Reporter: Aslak Knutsen Assignee: Andrew Lee Rubinger The OpenEJBTestEnricher needs CDI to run due to import of javax.inject.Inject -- 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

12 years, 8 months

4
9
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

arquillian-issues October 2011