[JBoss JIRA] Created: (ARQ-309) Allow configuration to specify an OpenEJB configuration resources (openejb.xml)
by Dan Allen (JIRA)
Allow configuration to specify an OpenEJB configuration resources (openejb.xml)
-------------------------------------------------------------------------------
Key: ARQ-309
URL: https://jira.jboss.org/browse/ARQ-309
Project: Arquillian
Issue Type: Feature Request
Components: OpenEJB Containers
Affects Versions: 1.0.0.Alpha4
Reporter: Dan Allen
Priority: Minor
Implement the feature described in the OpenEJB FAQ for supplying a custom configuration file.
http://openejb.apache.org/faq.html
Create an openejb.xml file in any directory* that gets added to your test classpath. Then in your test case do this:
protected void setUp() throws Exception {
Properties properties = new Properties();
properties.setProperty(Context.INITIAL_CONTEXT_FACTORY, "org.apache.openejb.client.LocalInitialContextFactory");
URL config = this.getClass().getClassLoader().getResource("openejb.xml");
properties.setProperty("openejb.configuration", config.toExternalForm());
initialContext = new InitialContext(properties);
}
* The name of this file could be an Arquillian container configuration property.
--
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
14 years, 6 months
[JBoss JIRA] Created: (ARQ-340) mappedName and lookup attributes are ignored for @EJB in jections into test cases, forcing a naming convention on implementations
by Radai Rosenblatt (JIRA)
mappedName and lookup attributes are ignored for @EJB in jections into test cases, forcing a naming convention on implementations
---------------------------------------------------------------------------------------------------------------------------------
Key: ARQ-340
URL: https://jira.jboss.org/browse/ARQ-340
Project: Arquillian
Issue Type: Bug
Components: Runtime Enricher SPI
Affects Versions: 1.0.0.Alpha4
Environment: JRE 1.6.0.21 windows xp jboss embedded 6
Reporter: Radai Rosenblatt
suppose i have an interface called BeanInterface, which is a local interface implemented a class called BeanImplementation.
then, in my test case, i have the following in ijected field:
@EJB(mappedName = "java:global/test/BeanImplementation/local")
private BeanInterface bean;
this will fail because the enricher does not bother looking at the annotation attributes. specifically, as can be seen in EJBInjectionEnricher.java line 102, the code does not pass the Field itself to the lookup method, only its name. the lookup method then proceeds to try several JNDI naming alternatives (line 137).
this means that production classes are forced to adhere to the naming conventions used by arquillian code or tests fail.
the code in question could take into account the mappedName and/or lookup attributes of @EJB to allow developers to specify the JNDI name for the lookup.
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 6 months
[JBoss JIRA] Created: (ARQ-375) Support for the containers in JBoss products
by Juraci Costa (JIRA)
Support for the containers in JBoss products
--------------------------------------------
Key: ARQ-375
URL: https://issues.jboss.org/browse/ARQ-375
Project: Arquillian
Issue Type: Feature Request
Reporter: Juraci Costa
We have some work planned for improving our integration tests coverage in EAP, EWP and EWS. Arquillian is our best option at the moment. For that, we'll need support for the containers we ship as part of our offerings. These ones are not currently supported by Arquillian, and we would like Arquillian team to evaluate if those can be (and will be) implemented as "remote" containers.
EAP 6 - JBoss AS 7
EWS 1.x - Tomcat 5.5 and Tomcat 6
Also, I understand that JBoss AS 5.1 is supported, covering the following products:
EAP 5.1 - JBoss AS 5.1
EWP 5.1 - JBoss AS 5.1
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 7 months