[JBoss JIRA] Created: (ARQ-473) DeployableContainer should not be restricted to only deploy Descriptors or Archives
by Aslak Knutsen (JIRA)
DeployableContainer should not be restricted to only deploy Descriptors or Archives
-----------------------------------------------------------------------------------
Key: ARQ-473
URL: https://issues.jboss.org/browse/ARQ-473
Project: Arquillian
Issue Type: Feature Request
Security Level: Public (Everyone can see)
Components: Base Implementation, Deployable Containers SPI
Affects Versions: 1.0.0.CR1
Reporter: Aslak Knutsen
Fix For: 1.1.0.CR1
To open up for more specialized Containers we should support some type of 'WildCard' Deploy.
Possible by having a Annotation driven DeployableContainer, e.g.
@Deploy
public SomethingExposedInContext(SomeRandomOtherType type)
This will let us e.g. deploy Files/ Images etc directly for non Java/EE type Containers.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 9 months
[JBoss JIRA] Created: (ARQ-417) Support maven deployments
by Adrian Cole (JIRA)
Support maven deployments
-------------------------
Key: ARQ-417
URL: https://issues.jboss.org/browse/ARQ-417
Project: Arquillian
Issue Type: Feature Request
Security Level: Public (Everyone can see)
Components: Configuration
Reporter: Adrian Cole
Microdeployments via ShrinkWrap are a nimble deployment mechanism that allows developers to test bytecode skipping the build. Another usecase is to have ARQ in a CI loop, testing artifacts post-deploy. For this sort of scenario, it would be useful to reuse test cases from the microdeployments, but have them leveraged against code pulled from maven artifacts published in a prior step.
For example, we could have an @Maven annotation which could define the coordinates of an ear file, and place that on a test scenario that performs the war, ejb, cdi, etc tests of from the dependent modules.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 9 months
[JBoss JIRA] Created: (ARQ-480) Create a Notification SPI
by Aslak Knutsen (JIRA)
Create a Notification SPI
-------------------------
Key: ARQ-480
URL: https://issues.jboss.org/browse/ARQ-480
Project: Arquillian
Issue Type: Feature Request
Security Level: Public (Everyone can see)
Components: Base Implementation, Runtime Enricher SPI
Affects Versions: 1.0.0.Final
Reporter: Aslak Knutsen
Fix For: 1.1.0.Beta1
There should be a way for SPI impls to communicate with executor about what they have done outside of throwing exception.
e.g. TestEnrcihers
* EJBEnricher ran first and couldn't find a specific @EJB, but CDI runs after and can.
** EJBEnricher should not fail on his attempt, but should report what he tried and where he failed
** CDI Enricher should be executed regardless of EJBEnrichers outcome
** Summarize in the end to compare if we have a full Enriched Object
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 9 months
[JBoss JIRA] Created: (ARQ-453) Implement Apache Httpd managed container
by Ondrej Zizka (JIRA)
Implement Apache Httpd managed container
----------------------------------------
Key: ARQ-453
URL: https://issues.jboss.org/browse/ARQ-453
Project: Arquillian
Issue Type: Feature Request
Security Level: Public (Everyone can see)
Reporter: Ondrej Zizka
(15:22:04) OndrejZizka: Would it make sense to create httpd container, to make it manageable?
(15:22:25) OndrejZizka: Ommiting the deploy stuff
(15:37:40) aslak: OndraZizka, what's the purpose ?
(15:38:47) OndrejZizka: I'd make use of it for EWS testing.
(15:38:59) OndrejZizka: So I would have everything under one roof
(15:39:41) OndrejZizka: But right, I could use other Java httpd management lib if there's any
(15:41:39) aslak: OndraZizka, what do you do with it without deploy?
(15:55:37) aslak: OndraZizka, it could be useful
(16:02:21) OndrejZizka: aslak: I would configure httpd, restart it, and test something from a client side from junit
(16:03:21) OndrejZizka: Right, I would assume that something is already "deployed"
(16:03:47) OndrejZizka: I don't know how we could embrace the "deploy" concept for httpd
(16:04:22) OndrejZizka: Perhaps just by copying it to some dir detected in httpd.conf, e.g. DocumentRoot and extracting
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 9 months
[JBoss JIRA] Created: (ARQ-184) NPE in o.j.aop.Dispatcher.invoke:117 - ARQ Alpha2 + remote-50 + as-client 5.0.1
by Ondrej Žižka (JIRA)
NPE in o.j.aop.Dispatcher.invoke:117 - ARQ Alpha2 + remote-50 + as-client 5.0.1
-------------------------------------------------------------------------------
Key: ARQ-184
URL: https://jira.jboss.org/browse/ARQ-184
Project: Arquillian
Issue Type: Bug
Environment: ARQ Alpha2 + remote-50 + as-client 5.0.1 + EAP 5.0.1
Reporter: Ondrej Žižka
STR:
1) Download the project attached,
2) Run EAP 5.0.1 default, but I think the request doesn't even get sent.
3) mvn clean install (profile is self-enabled),
4) You'll get a NPE:
org.jboss.arquillian.impl.event.FiredEventException: org.jboss.arquillian.spi.LifecycleException: Could not connect to container
at org.jboss.arquillian.impl.event.MapEventManager.fire(MapEventManager.java:68)
at org.jboss.arquillian.impl.context.AbstractEventContext.fire(AbstractEventContext.java:115)
at org.jboss.arquillian.impl.EventTestRunnerAdaptor.beforeSuite(EventTestRunnerAdaptor.java:62)
at org.jboss.arquillian.junit.Arquillian.<init>(Arquillian.java:71)
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39)
at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)
at java.lang.reflect.Constructor.newInstance(Constructor.java:513)
at org.junit.internal.builders.AnnotatedBuilder.buildRunner(AnnotatedBuilder.java:31)
at org.junit.internal.builders.AnnotatedBuilder.runnerForClass(AnnotatedBuilder.java:24)
at org.junit.runners.model.RunnerBuilder.safeRunnerForClass(RunnerBuilder.java:57)
at org.junit.internal.builders.AllDefaultPossibilitiesBuilder.runnerForClass(AllDefaultPossibilitiesBuilder.java:29)
at org.junit.runners.model.RunnerBuilder.safeRunnerForClass(RunnerBuilder.java:57)
at org.junit.internal.requests.ClassRequest.getRunner(ClassRequest.java:24)
at org.apache.maven.surefire.junit4.JUnit4TestSet.<init>(JUnit4TestSet.java:45)
at org.apache.maven.surefire.junit4.JUnit4DirectoryTestSuite.createTestSet(JUnit4DirectoryTestSuite.java:56)
at org.apache.maven.surefire.suite.AbstractDirectoryTestSuite.locateTestSets(AbstractDirectoryTestSuite.java:96)
at org.apache.maven.surefire.Surefire.createSuiteFromDefinition(Surefire.java:209)
at org.apache.maven.surefire.Surefire.run(Surefire.java:156)
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.apache.maven.surefire.booter.SurefireBooter.runSuitesInProcess(SurefireBooter.java:345)
at org.apache.maven.surefire.booter.SurefireBooter.main(SurefireBooter.java:1009)
Caused by: org.jboss.arquillian.spi.LifecycleException: Could not connect to container
at org.jboss.arquillian.jbossas.remote50.JBossASRemoteContainer.start(JBossASRemoteContainer.java:89)
at org.jboss.arquillian.impl.handler.ContainerStarter.callback(ContainerStarter.java:52)
at org.jboss.arquillian.impl.handler.ContainerStarter.callback(ContainerStarter.java:41)
at org.jboss.arquillian.impl.event.MapEventManager.fire(MapEventManager.java:63)
... 24 more
Caused by: java.lang.NullPointerException
at org.jboss.aop.Dispatcher.invoke(Dispatcher.java:117)
at org.jboss.aspects.remoting.AOPRemotingInvocationHandler.invoke(AOPRemotingInvocationHandler.java:82)
at org.jboss.profileservice.management.upload.remoting.AbstractDeployHandler.invoke(AbstractDeployHandler.java:210)
at org.jboss.remoting.ServerInvoker.invoke(ServerInvoker.java:897)
at org.jboss.remoting.transport.socket.ServerThread.completeInvocation(ServerThread.java:768)
at org.jboss.remoting.transport.socket.ServerThread.processInvocation(ServerThread.java:721)
at org.jboss.remoting.transport.socket.ServerThread.dorun(ServerThread.java:548)
at org.jboss.remoting.transport.socket.ServerThread.run(ServerThread.java:234)
at org.jboss.remoting.MicroRemoteClientInvoker.invoke(MicroRemoteClientInvoker.java:206)
at org.jboss.remoting.Client.invoke(Client.java:1708)
at org.jboss.remoting.Client.invoke(Client.java:612)
at org.jboss.aspects.remoting.InvokeRemoteInterceptor.invoke(InvokeRemoteInterceptor.java:60)
at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102)
at org.jboss.aspects.remoting.MergeMetaDataInterceptor.invoke(MergeMetaDataInterceptor.java:74)
at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102)
at org.jboss.aspects.security.SecurityClientInterceptor.invoke(SecurityClientInterceptor.java:65)
at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102)
at AOPProxy$1.loadProfile(AOPProxy$1.java)
at org.jboss.arquillian.jbossas.remote50.JBossASRemoteContainer.initDeploymentManager(JBossASRemoteContainer.java:222)
at org.jboss.arquillian.jbossas.remote50.JBossASRemoteContainer.start(JBossASRemoteContainer.java:85)
at org.jboss.arquillian.impl.handler.ContainerStarter.callback(ContainerStarter.java:52)
at org.jboss.arquillian.impl.handler.ContainerStarter.callback(ContainerStarter.java:41)
at org.jboss.arquillian.impl.event.MapEventManager.fire(MapEventManager.java:63)
at org.jboss.arquillian.impl.context.AbstractEventContext.fire(AbstractEventContext.java:115)
at org.jboss.arquillian.impl.EventTestRunnerAdaptor.beforeSuite(EventTestRunnerAdaptor.java:62)
at org.jboss.arquillian.junit.Arquillian.<init>(Arquillian.java:71)
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39)
at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)
at java.lang.reflect.Constructor.newInstance(Constructor.java:513)
at org.junit.internal.builders.AnnotatedBuilder.buildRunner(AnnotatedBuilder.java:31)
at org.junit.internal.builders.AnnotatedBuilder.runnerForClass(AnnotatedBuilder.java:24)
at org.junit.runners.model.RunnerBuilder.safeRunnerForClass(RunnerBuilder.java:57)
at org.junit.internal.builders.AllDefaultPossibilitiesBuilder.runnerForClass(AllDefaultPossibilitiesBuilder.java:29)
at org.junit.runners.model.RunnerBuilder.safeRunnerForClass(RunnerBuilder.java:57)
at org.junit.internal.requests.ClassRequest.getRunner(ClassRequest.java:24)
at org.apache.maven.surefire.junit4.JUnit4TestSet.<init>(JUnit4TestSet.java:45)
at org.apache.maven.surefire.junit4.JUnit4DirectoryTestSuite.createTestSet(JUnit4DirectoryTestSuite.java:56)
at org.apache.maven.surefire.suite.AbstractDirectoryTestSuite.locateTestSets(AbstractDirectoryTestSuite.java:96)
at org.apache.maven.surefire.Surefire.createSuiteFromDefinition(Surefire.java:209)
at org.apache.maven.surefire.Surefire.run(Surefire.java:156)
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.apache.maven.surefire.booter.SurefireBooter.runSuitesInProcess(SurefireBooter.java:345)
at org.apache.maven.surefire.booter.SurefireBooter.main(SurefireBooter.java:1009)
at org.jboss.aspects.remoting.InvokeRemoteInterceptor.invoke(InvokeRemoteInterceptor.java:72)
at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102)
at org.jboss.aspects.remoting.MergeMetaDataInterceptor.invoke(MergeMetaDataInterceptor.java:74)
at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102)
at org.jboss.aspects.security.SecurityClientInterceptor.invoke(SecurityClientInterceptor.java:65)
at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102)
at AOPProxy$1.loadProfile(AOPProxy$1.java)
at org.jboss.arquillian.jbossas.remote50.JBossASRemoteContainer.initDeploymentManager(JBossASRemoteContainer.java:222)
at org.jboss.arquillian.jbossas.remote50.JBossASRemoteContainer.start(JBossASRemoteContainer.java:85)
... 27 more
--
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, 10 months
[JBoss JIRA] Created: (ARQ-131) Include utility base class to simplify JPA testing
by Paul Bakker (JIRA)
Include utility base class to simplify JPA testing
--------------------------------------------------
Key: ARQ-131
URL: https://jira.jboss.org/jira/browse/ARQ-131
Project: Arquillian
Issue Type: Feature Request
Components: Test Harness Integration
Reporter: Paul Bakker
Priority: Minor
Two things are often needed when testing JPA code:
-1 Counting rows in a table
-2 Rolling back the transaction after each test (to speed up test execution, while potentially dangerous)
To simplify testing it would be good to have a set of base classes that implement this common functionality. Test class can extend a base class when this kind of functionality is required. The Spring framework has excellent support for this and can be used for inspiration:
http://static.springsource.org/spring/docs/3.0.x/spring-framework-referen...
I included some example code that I wrote myself to get a feel how difficult it would be to implement. The code uses an embedded container using the EJB 3.1 API, but should off course integrate with Arquillian.
By default each testcase runs in a transaction (using the usertransaction) and is rolled back at the end of the test, unless the testcase is annotated @TransactionAttribute(TransactionAttributeType.NOT_SUPPORTED). The rollback behavior can be changed with the custom @RollbackAfterTest anotation.
I would be happy to help implementing this feature.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 10 months