[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] Created: (ARQ-299) Create a IN_CONTAINER Exception Proxy
by Aslak Knutsen (JIRA)
Create a IN_CONTAINER Exception Proxy
-------------------------------------
Key: ARQ-299
URL: https://jira.jboss.org/browse/ARQ-299
Project: Arquillian
Issue Type: Feature Request
Reporter: Aslak Knutsen
On Exception, the IN_CONTAINER TestRunner tries to serialize the caught Exception back to the Client so it can be displayed as if it was local. The problem is if you don't have the Client lib on Client Classpath or you have the wrong version of it. This results in a Deserialization exception on the Client.
We probably have to not Serialize the actual Exception, but serialize a Textual representation of it, which we can create a 'proxy' Exception of on the client side and make it 'look' like the original.
--
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, 1 month
[JBoss JIRA] (ARQ-784) The wlsHome property of the WebLogic containers should default to a pre-defined environment variable
by Vineet Reynolds (JIRA)
Vineet Reynolds created ARQ-784:
-----------------------------------
Summary: The wlsHome property of the WebLogic containers should default to a pre-defined environment variable
Key: ARQ-784
URL: https://issues.jboss.org/browse/ARQ-784
Project: Arquillian
Issue Type: Enhancement
Security Level: Public (Everyone can see)
Components: WebLogic Containers
Affects Versions: wls_1.0.0.Alpha2, wls_1.0.0.Alpha1
Reporter: Vineet Reynolds
Assignee: Vineet Reynolds
Fix For: wls_1.0.0.next
The `wlsHome` property does not have a default value at present, and users are expected to specify this in arquillian.xml; a system property could be used in arquillian.xml, but this would require Surefire or the test-execution environment to pass an existing environment variable as a system property.
It would useful to default this to the `WL_HOME` environment variable to preserve the intent of the property. However, we could consider using the `WLS_HOME` environment variable (this points to the `WL_HOME/server` directory) since all usages refer to resources in the server sub-directory.
--
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