Hi I've created a JIRA ticket for this: https://issues.apache.org/jira/browse/OPENEJB-1649 It contains the following 4 sub-tasks: * Servlets: https://issues.apache.org/jira/browse/OPENEJB-1650
* Filters: https://issues.apache.org/jira/browse/OPENEJB-1651 * Listeners: https://issues.apache.org/jira/browse/OPENEJB-1652 * JSF Bean: https://issues.apache.org/jira/browse/OPENEJB-1653 I've uploaded a patch for the "Servlets" sub-task: https://issues.apache.org/jira/browse/OPENEJB-1650 Could someone review it? Three tests fail and once the functionality is implemented, these tests should pass (after uncommenting the injections). - Ranga ________________________________ From: David Blevins <[email protected]> To: [email protected] Sent: Friday, August 26, 2011 1:27 PM Subject: Arquillian tests Ok, real quick thoughts on what we could use -- at least initially -- for TomEE unit tests. For each of: - Servlet (lazy startup) - Servlet (load on startup) - Filter - Listener - JSF ManagedBean We should test basic injection of: - @Resource - TransactionManager - <env-entry> - All Primitive wrappers - Enum - Class - String - DataSource - JMS - ConnectionFactory (JMS) - Topic - Queue - @EJB - @Local - @LocalBean - @Remote - JPA - @PersistenceContext - @PersistenceUnit - CDI - @Inject - WS - @WebServiceRef Then all of the above in the exact component class, then again in a parent class to make sure subclassing and injection works. Should give us some basic coverage. JMS and WS injection would be the lowest priority since they are not in the web profile. -David
