Home/ Questions/Q 6669337
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-26T03:08:16+00:00

I am a little confused about integration testing of a simple EJB. If I

  • 0

I am a little confused about integration testing of a simple EJB. If I want to test the EJB’s local interface/no-interface do I need to use Arquillian? I stumbled upon Arquillian but I have never used it. I have a Maven directory structure/Glassfish and Eclipse Indigo

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    If I want to test the EJB’s local interface/no-interface do I need to use Arquillian?

    It is not necessary to use Arquillian, but there are certain things made easier when you do so.

    Ordinarily, you would merely use the EJBContainer API available in EJB 3.1 for testing of EJBs in an embedded container (that runs in the same JVM as the tests). In the case of embedded Glassfish, this typically results in deployment of EJBs that are found in the classpath of the application.

    Arquillian allows you to do a lot more than execute tests in a container. It manages the lifecycle of the container, thus not requiring any writing of code beyond setting the properties in the arquillian.xml file. It allows you to manage deployments to a container in a far more easier manner; using the ShrinkWrap API, one can programmatically perform different context-sensitive deployments to a container. Furthermore, injection of dependencies (test enrichment) can also be performed, so long as they’re supported by Arquillian.

    It would suffice to know that the embedded Glassfish container support for Arquillian, uses the same APIs that are exposed by the embedded Glassfish API; usually you might end up duplicating the work of Arquillian, except in certain unique scenarios.

    If you’re interested in taking a look at examples using Arquillian, this GitHub project would help.

    • 0