[JBoss JIRA] (ARQ-824) Verify Arquillian can run on JDK 1.5
by Aslak Knutsen (JIRA)
Aslak Knutsen created ARQ-824:
---------------------------------
Summary: Verify Arquillian can run on JDK 1.5
Key: ARQ-824
URL: https://issues.jboss.org/browse/ARQ-824
Project: Arquillian
Issue Type: Bug
Security Level: Public (Everyone can see)
Affects Versions: 1.0.0.CR7
Reporter: Aslak Knutsen
Assignee: Aslak Knutsen
Fix For: 1.0.0.Final
Setting compiler options target/source to 1.5 is not enough to verify that the code can actually run on JDK 1.5 since it ignores API changes. To avoid forcing developers to have JDK 1.5 installed to compile, we can add e.g. the Animal Sniffer Maven Plugin to verify using usage of JDK based on known api signatures.
--
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
[JBoss JIRA] Created: (ARQ-77) Support @EJB injection
by Andrew Lee Rubinger (JIRA)
Support @EJB injection
-----------------------
Key: ARQ-77
URL: https://jira.jboss.org/jira/browse/ARQ-77
Project: Arquillian
Issue Type: Feature Request
Components: OpenEJB Containers
Reporter: Andrew Lee Rubinger
Assignee: Andrew Lee Rubinger
Tests should be able to have class or instance members injected according to @EJB semantics, avoiding the need for lookup code. The prototype is currently in the OpenEJB integration module, but really we should have some EJB 3.1 Global JNDI syntax compatible resolvers (which need an EJB name, module name, app name, and business interface name). Note that portable JNDI is under java:global, so only accessible to local JVMs.
--
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
[JBoss JIRA] (ARQ-837) Managed GlassFish container does not shutdown when a test errors out
by Vineet Reynolds (JIRA)
Vineet Reynolds created ARQ-837:
-----------------------------------
Summary: Managed GlassFish container does not shutdown when a test errors out
Key: ARQ-837
URL: https://issues.jboss.org/browse/ARQ-837
Project: Arquillian
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: GlassFish Containers
Affects Versions: glassfish_1.0.0.CR3
Reporter: Vineet Reynolds
When a test errors out, Arquillian does not invoke the {{DeployableContainer.stop()}} implementation of the managed GlassFish container. The GlassFish container started by Arquillian continues to run, and the subsequent test execution produces the expected error message:
{{quote}}
The server is already running! Managed containers does not support connecting to running server instances due to the possible harmful effect of connecting to the wrong server. Please stop server before running or change to another type of container.
To disable this check and allow Arquillian to connect to a running server, set allowConnectingToRunningServer to true in the container configuration
{{quote}}
The GlassFish container implementation should incorporate a mechanism similar to the JBoss AS 7 managed container implementation, to execute the {{asadmin stop-domain}} command in a shutdown hook.
--
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, 1 month