December 2011 - arquillian-issues

[JBoss JIRA] (ARQ-684) Show better exception if deployment type is not supported

by Karel Piwko (Created) (JIRA)

Show better exception if deployment type is not supported --------------------------------------------------------- Key: ARQ-684 URL: https://issues.jboss.org/browse/ARQ-684 Project: Arquillian Issue Type: Enhancement Security Level: Public (Everyone can see) Components: Deployable Containers SPI Affects Versions: 1.0.0.CR6 Reporter: Karel Piwko There are archives which are not supported by a container, e.g. an EAR on Tomcat. There should be a better message is that happens than following: {code} [java] INFO: Starting Tomcat with: [java, -Dcom.sun.management.jmxremote.port=8089, -Dcom.sun.management.jmxremote.ssl=false, -Dcom.sun.management.jmxremote.authenticate=false, -Dbasedir=/home/tschloss/git/brms, -Dlog.dir=log, -classpath, /home/tschloss/QA/hudson/WORKSPACE/jboss-ews-1.0/tomcat6/bin/bootstrap.jar:/home/tschloss/QA/hudson/WORKSPACE/jboss-ews-1.0/tomcat6/bin/tomcat-juli.jar, -Djava.endorsed.dirs=/home/tschloss/QA/hudson/WORKSPACE/jboss-ews-1.0/tomcat6/endorsed, -Dcatalina.base=/home/tschloss/QA/hudson/WORKSPACE/jboss-ews-1.0/tomcat6, -Dcatalina.home=/home/tschloss/QA/hudson/WORKSPACE/jboss-ews-1.0/tomcat6, -Djava.io.tmpdir=/home/tschloss/QA/hudson/WORKSPACE/jboss-ews-1.0/tomcat6/temp, org.apache.catalina.startup.Bootstrap, -config, /home/tschloss/QA/hudson/WORKSPACE/jboss-ews-1.0/tomcat6/conf/server.xml, start] [java] Dec 5, 2011 9:54:53 AM org.apache.catalina.core.AprLifecycleListener init [java] INFO: The APR based Apache Tomcat Native library which allows optimal performance in production environments was not found on the java.library.path: /usr/lib/jvm/java-1.6.0-openjdk-1.6.0.0.x86_64/jre/lib/amd64/server:/usr/lib/jvm/java-1.6.0-openjdk-1.6.0.0.x86_64/jre/lib/amd64:/usr/lib/jvm/java-1.6.0-openjdk-1.6.0.0.x86_64/jre/../lib/amd64:/usr/java/packages/lib/amd64:/usr/lib64:/lib64:/lib:/usr/lib [java] Dec 5, 2011 9:54:53 AM org.apache.coyote.http11.Http11Protocol init [java] INFO: Initializing Coyote HTTP/1.1 on http-8080 [java] Dec 5, 2011 9:54:53 AM org.apache.catalina.startup.Catalina load [java] INFO: Initialization processed in 734 ms [java] Dec 5, 2011 9:54:53 AM org.apache.catalina.core.StandardService start [java] INFO: Starting service Catalina [java] Dec 5, 2011 9:54:53 AM org.apache.catalina.core.StandardEngine start [java] INFO: Starting Servlet Engine: Apache Tomcat/6.0.32 [java] Dec 5, 2011 9:54:53 AM org.apache.catalina.startup.HostConfig deployDirectory [java] INFO: Deploying web application directory host-manager [java] Dec 5, 2011 9:54:54 AM org.apache.catalina.startup.HostConfig deployDirectory [java] INFO: Deploying web application directory manager [java] Dec 5, 2011 9:54:54 AM org.apache.catalina.startup.HostConfig deployDirectory [java] INFO: Deploying web application directory ROOT [java] Dec 5, 2011 9:54:54 AM org.apache.catalina.startup.HostConfig deployDirectory [java] INFO: Deploying web application directory docs [java] Dec 5, 2011 9:54:54 AM org.apache.catalina.startup.HostConfig deployDirectory [java] INFO: Deploying web application directory examples [java] Dec 5, 2011 9:54:54 AM org.apache.coyote.http11.Http11Protocol start [java] INFO: Starting Coyote HTTP/1.1 on http-8080 [java] Dec 5, 2011 9:54:54 AM org.apache.catalina.core.ApplicationContext log [java] INFO: Manager: init: Associated with Deployer 'Catalina:type=Deployer,host=localhost' [java] Dec 5, 2011 9:54:54 AM org.apache.catalina.core.ApplicationContext log [java] INFO: Manager: init: Global resources are available [java] Dec 5, 2011 9:54:54 AM org.apache.jk.common.ChannelSocket init [java] INFO: JK: ajp13 listening on /0.0.0.0:8009 [java] Dec 5, 2011 9:54:54 AM org.apache.catalina.core.ApplicationContext log [java] INFO: Manager: list: Listing contexts for virtual host 'localhost' [java] Dec 5, 2011 9:54:54 AM org.apache.jk.server.JkMain start [java] INFO: Jk running ID=0 time=0/20 config=null [java] Dec 5, 2011 9:54:54 AM org.apache.catalina.startup.Catalina start [java] INFO: Server startup in 510 ms [java] Dec 5, 2011 9:55:11 AM org.apache.catalina.core.ApplicationContext log [java] INFO: Manager: deploy: Deploying web application at '/my-tests' [java] Dec 5, 2011 9:55:11 AM org.apache.catalina.core.ApplicationContext log [java] INFO: Manager: Uploading WAR file to /home/tschloss/QA/hudson/WORKSPACE/jboss-ews-1.0/tomcat6/webapps/my-tests.war [java] Dec 5, 2011 9:55:12 AM org.apache.catalina.startup.HostConfig deployWAR [java] INFO: Deploying web application archive my-tests.war [java] Dec 5, 2011 9:55:12 AM org.jboss.arquillian.container.tomcat.ProtocolMetadataParser connect [java] INFO: Connecting to JMX at service:jmx:rmi:///jndi/rmi://localhost:8089/jmxrmi [java] [2011-12-05 09:55:12,854] INFO - [java] Starting [DummyTest] [java] [2011-12-05 09:55:12,861] INFO - ==== dummyTest ==== [java] [2011-12-05 09:55:12,871] WARN - failed org.jboss.qa.brms.bre.container.DummyTest - dummyTest [java] Dec 5, 2011 9:55:12 AM org.apache.catalina.core.ApplicationContext log [java] INFO: Manager: undeploy: Undeploying web application at '/my-tests' [java] Dec 5, 2011 9:55:13 AM org.apache.catalina.startup.HostConfig checkResources [java] INFO: Undeploying context [/my-tests] [java] Dec 5, 2011 9:55:18 AM org.apache.catalina.core.ApplicationContext log [java] INFO: Manager: deploy: Deploying web application at '/my-tests' [java] Dec 5, 2011 9:55:18 AM org.apache.catalina.core.ApplicationContext log [java] INFO: Manager: Uploading WAR file to /home/tschloss/QA/hudson/WORKSPACE/jboss-ews-1.0/tomcat6/webapps/my-tests.war [java] Dec 5, 2011 9:55:18 AM org.apache.catalina.startup.HostConfig deployWAR [java] INFO: Deploying web application archive my-tests.war [java] Dec 5, 2011 9:55:18 AM org.jboss.arquillian.container.tomcat.ProtocolMetadataParser connect [java] INFO: Connecting to JMX at service:jmx:rmi:///jndi/rmi://localhost:8089/jmxrmi [java] [2011-12-05 09:55:18,699] INFO - [java] Starting [PersistenceTest] [java] [2011-12-05 09:55:18,703] INFO - ==== testCEP ==== [java] [2011-12-05 09:55:18,707] WARN - failed Persistence - testCEP [java] [2011-12-05 09:55:18,715] INFO - ==== testEMandEMF ==== [java] [2011-12-05 09:55:18,717] WARN - failed Persistence - testEMandEMF [java] [2011-12-05 09:55:18,723] INFO - ==== testFireRules ==== [java] [2011-12-05 09:55:18,727] WARN - failed Persistence - testFireRules [java] [2011-12-05 09:55:18,735] INFO - ==== testFireRulesSepparatedly ==== [java] [2011-12-05 09:55:18,738] WARN - failed Persistence - testFireRulesSepparatedly [java] [2011-12-05 09:55:18,744] INFO - ==== testInsert ==== [java] [2011-12-05 09:55:18,747] WARN - failed Persistence - testInsert [java] [2011-12-05 09:55:18,753] INFO - ==== testInsertEvent ==== [java] [2011-12-05 09:55:18,755] WARN - failed Persistence - testInsertEvent [java] Dec 5, 2011 9:55:18 AM org.apache.catalina.core.ApplicationContext log [java] INFO: Manager: undeploy: Undeploying web application at '/my-tests' [java] Dec 5, 2011 9:55:19 AM org.apache.catalina.startup.HostConfig checkResources [java] INFO: Undeploying context [/my-tests] [java] Tests run: 7, Failures: 7, Errors: 0, Skipped: 0, Time elapsed: 29.029 sec <<< FAILURE! {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

12 years, 5 months

2
1
0 / 0

[JBoss JIRA] (ARQ-682) Introduce convention for fetching datasets from /datasources folder first.

by Bartosz Majsak (Created) (JIRA)

Introduce convention for fetching datasets from /datasources folder first. -------------------------------------------------------------------------- Key: ARQ-682 URL: https://issues.jboss.org/browse/ARQ-682 Project: Arquillian Issue Type: Enhancement Security Level: Public (Everyone can see) Components: Extension - Persistence Affects Versions: persistence_1.0.0.Alpha1 Reporter: Bartosz Majsak Assignee: Bartosz Majsak Fix For: persistence_1.0.0.next It would be handy to assume that all datasets are stored in "datasets" folder and in the same time not forcing user to write full location all the time. So the convention should work as follows: * Check if given dataset file is in /datasets folder * If it's not there assume that it's stored in the root folder. -- 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, 5 months

5
4
0 / 0

[JBoss JIRA] (ARQ-663) @Expected annotation giving false positives due to improper usage of DBUnit assertions

by Bartosz Majsak (Created) (JIRA)

@Expected annotation giving false positives due to improper usage of DBUnit assertions -------------------------------------------------------------------------------------- Key: ARQ-663 URL: https://issues.jboss.org/browse/ARQ-663 Project: Arquillian Issue Type: Bug Security Level: Public (Everyone can see) Components: Extension - Persistence Reporter: Bartosz Majsak -- 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, 5 months

6
8
0 / 0

[JBoss JIRA] (ARQ-680) Separate DBUnit DatabaseConnection creation in dedicated event.

by Bartosz Majsak (Created) (JIRA)

Separate DBUnit DatabaseConnection creation in dedicated event. --------------------------------------------------------------- Key: ARQ-680 URL: https://issues.jboss.org/browse/ARQ-680 Project: Arquillian Issue Type: Enhancement Security Level: Public (Everyone can see) Reporter: Bartosz Majsak Assignee: Bartosz Majsak -- 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, 5 months

5
5
0 / 0

[JBoss JIRA] (ARQ-653) Add Persistence configuration to Archive instead of client callback

by Aslak Knutsen (Created) (JIRA)

Add Persistence configuration to Archive instead of client callback ------------------------------------------------------------------- Key: ARQ-653 URL: https://issues.jboss.org/browse/ARQ-653 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 A Callback to the client side has a added overhead, adding the 'configuration' file to the deployment itself should speed it up -- 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, 5 months

7
8
0 / 0

[JBoss JIRA] (ARQ-681) Rename dataset annotations

by Bartosz Majsak (Created) (JIRA)

Rename dataset annotations -------------------------- Key: ARQ-681 URL: https://issues.jboss.org/browse/ARQ-681 Project: Arquillian Issue Type: Enhancement Security Level: Public (Everyone can see) Components: Extension - Persistence Affects Versions: persistence_1.0.0.Alpha1 Reporter: Bartosz Majsak Assignee: Bartosz Majsak Fix For: persistence_1.0.0.next Rename dataset related annotations based on the outcome from this thread (http://community.jboss.org/message/639107). -- 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, 5 months

4
3
0 / 0

[JBoss JIRA] (ARQ-654) Change Persistence TransactionStarted event to StartTransaction

by Aslak Knutsen (Created) (JIRA)

Change Persistence TransactionStarted event to StartTransaction --------------------------------------------------------------- Key: ARQ-654 URL: https://issues.jboss.org/browse/ARQ-654 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 Change the naming of the event to define what should happen, not what has happened. Since it's the Event that triggeres it, it hasn't actually happened yet. StartTransaction vs TransactionStarted TransactionStarted should in this case be switched with SPI level BeforeTransactionStarted and AfterTransactionStarted, see ARQ-652 -- 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, 5 months

6
5
0 / 0

[JBoss JIRA] (ARQ-662) Error when running a test that is not related with persistence

by Bartosz Majsak (Created) (JIRA)

Error when running a test that is not related with persistence -------------------------------------------------------------- Key: ARQ-662 URL: https://issues.jboss.org/browse/ARQ-662 Project: Arquillian Issue Type: Bug Security Level: Public (Everyone can see) Components: Extension - Persistence Affects Versions: persistence_1.0.0.Alpha1 Reporter: Bartosz Majsak Tries to load datasource even for tests which are not requiring persistence extensions. More details here: https://gist.github.com/1393355 -- 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, 5 months

5
5
0 / 0

[JBoss JIRA] (ARQ-683) Prepare Persistence Alpha2 release

by Aslak Knutsen (Created) (JIRA)

Prepare Persistence Alpha2 release ---------------------------------- Key: ARQ-683 URL: https://issues.jboss.org/browse/ARQ-683 Project: Arquillian Issue Type: Release Security Level: Public (Everyone can see) Components: Extension - Persistence Reporter: Aslak Knutsen Assignee: Aslak Knutsen Fix For: persistence_1.0.0.Alpha2 -- 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, 5 months

2
1
0 / 0

[JBoss JIRA] (ARQ-679) dependencies in manifest.mf ignored when running maven install

by Michael Voegele (Created) (JIRA)

dependencies in manifest.mf ignored when running maven install -------------------------------------------------------------- Key: ARQ-679 URL: https://issues.jboss.org/browse/ARQ-679 Project: Arquillian Issue Type: Bug Security Level: Public (Everyone can see) Components: JBoss Containers Affects Versions: 1.0.0.CR6 Environment: Windows Reporter: Michael Voegele I use following components / versions: arquillian-junit-container - 1.0.0.CR6 jboss - 7.1.0.Beta1 jboss-as-arquillian-container-remote - 7.1.0.Beta1 junit - 4.10 I have folloging testcase: @RunWith(Arquillian.class) public class DatasourceSessionBeanTest { @Deployment public static JavaArchive createTestArchive() { JavaArchive javaArchive = ShrinkWrap.create(JavaArchive.class, "datasource-test.jar"); javaArchive.addClasses(BeanInterceptor.class); javaArchive.addClasses(DatasourceServiceRemote.class, DatasourceSessionBean.class); javaArchive.addClasses(AlcatrazUser.class, DataTransferObject.class); javaArchive.addClasses(AlcatrazDAO.class, MatchMode.class); javaArchive.addAsManifestResource("META-INF/persistence.xml", "persistence.xml"); javaArchive.addAsManifestResource("META-INF/MANIFEST.MF", "MANIFEST.MF"); // javaArchive.addPackages(true, "org.slf4j"); // javaArchive.addPackages(true, "org.jboss.logmanager"); System.out.println(javaArchive.toString(true)); return javaArchive; } @EJB(mappedName = "java:app/datasource-test/DatasourceSessionBean") private DatasourceServiceRemote datasourceService; @Test public void testGetByRoid() { AlcatrazUser alcatrazUser = datasourceService.getByRoid("2531781"); assertNotNull("Result should not be null.", alcatrazUser); } } -> A manifest.mf is added containing 'Dependencies: org.slf4j' When running the test "as a junit test", slf4j is found and logging works. When the tests are executed from maven lifecycle, I get a ClassNotFoundException org.slf4j.Logger and the test fails. By adding dependencies to org.slf4j and org.jboss.logmanager to the pom and by adding them to the ShrinkWrap archive (see the two commented lines), the test works, although no logging is done. Dependencies to modules in manifest.mf should also be recognized when the tests are run from maven. -- 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, 5 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

arquillian-issues December 2011