Skip to main content

EJB3 unit testing - part one - dependency injection

You might want to use an embeddable container for this - but why really - cause it's really simple. EJB3 session beans are POJO's and should be tested like POJO's.

However there are some issues in order to get EJB3 unit tests working. One of them are dependency injection.

How does dependency injection work? Take a look at this method using reflection:


/**
* @param targetBean - the bean to inject into
* @param annotationClass - the annotation class representing the injection
* @param objectToInject - the object to inject into targetBean
*/

private void inject(Object targetBean, Class annotationClass, Object objectToInject)
{
// Scan all (private and public fields) of the bean class
for(Field fld : targetBean.getClass().getDeclaredFields())
{
// See if the specified annotation is present for the field
if(fld.isAnnotationPresent(annotationClass))
{
// See if the field type is appropriate according to the object that is to be injected
if(fld.getType().isAssignableFrom(objectToInject.getClass()))
{
// Make sure that we can set the value of the field (e.g. if it's private)
fld.setAccessible(true);
try {
// Now set the field with the object to inject
fld.set(targetBean, objectToInject);
Logger.getLogger(getClass().getName()).info("Injected "+objectToInject.getClass().getName()+" into "+targetBean.getClass().getName());
} catch (IllegalArgumentException ex) {
Logger.getLogger(getClass().getName()).log(Level.SEVERE, null, ex);
} catch (IllegalAccessException ex) {
Logger.getLogger(getClass().getName()).log(Level.SEVERE, null, ex);
}
}
}
}
}


Now let's see how we can inject the entitymanager and invoke a stateless ejb3 session bean:


// Create session bean instance
MySessionBean mySessionBean = new MySessionBean();
// Inject new entity manager
inject(mySessionBean,PersistenceContext.class,Persistence.createEntityManagerFactory("myTestPU").createEntityManager());
// Invoke session bean method
mySessionBean.hello();

Comments

Uma Lade said…
Thank you so much, your example helped me a lot.

I was using EJB3Guice to inject the objects to a session bean and it doesn't work.

I was struggling how it make it work and found your example. Thanks a ton!!
Thanks for feedback. I will soon follow up with part two then...
Uma Lade said…
HI Peter,

Will be waiting for your part two..

another question regarding EJB3Unit.

My project uses eclipselink for persistence, and we are testing EJBs using EJB3Unit which uses hibernate for persistence.

So, we have some problems testing the beans.

For example: One of our entities have @Converter, to convert boolean to char or viceversa.

Im not able to test this entity, as hibernate throws constraintviolatedexception.
it cannot convert to boolean to char, and the related table has this field as 'char(1)'.

So, could you pls suggest any other alternative to test this kind of differences (between hibernate & persistence).

Thanks & Regards
Uma
I'd prefer testing with the same persistence provider as you use in your application - that is EclipseLink.

My colleague has made EJB3Unit use EclipseLink instead of hibernate - but I don't know the details around this myself.

As for my tests, I haven't used EJB3Unit - but rather implemented those parts of EJB3 needed for my tests (which is mostly only a fraction of a complete EJB3 container).

regards,

Peter

Popular posts from this blog

My VNC based development environment with Visual Studio Code running on Ubuntu

I've used this setup for my development environment for several years - giving me a developer desktop I can access anywhere. Even from my mobile phone. I've been fixing bugs, writing code and deployed emergency fixes from the bus, train and mountain tops. The setup is based on a lightweight desktop environment. There are lot of alternatives, but I've chosen fluxbox. From a plain AWS Amazon Ubuntu 16.04 ec2 instance I've started like this: sudo apt-get update sudo apt-get install fluxbox Download and extract tigervnc from https://github.com/TigerVNC/tigervnc/releases (I downloaded the binary file from https://bintray.com/tigervnc/stable/tigervnc/1.7.0 named tigervnc-1.7.0.x86_64.tar.gz ) then extract: tar -xvzf tigervnc-1.7.0.x86_64.tar.gz You need to install: sudo apt-get install x11-xkb-utils You need to edit .vnc/xstartup: nano .vnc/xstartup last line replace "twm &" with: fluxbox & Then you can start the

Angular components not reloading on route change

Spent a long time wondering why route changes caused strange effects on my component, and found out that it was because my component wasn't reloading at all. I had this assumption that when a route parameter changed (e.g. /projects/1 changed to /projects/2 ) the component for the route would be reloaded. But this is not the default behaviour of the Angular router. The default behaviour of the Angular router is to reuse the route if the configuration is the same (and not reload the component). But we can override this by providing a RouteReuseStrategy to our @NgModule: providers: [ { provide: RouteReuseStrategy, useClass: AARouteReuseStrategy } ] The full custom implementation of the RouteReuseStrategy will then be like this (and it's the shouldReuseRoute method that changes the behaviour so that the component is reloaded on route parameter change): export class AARouteReuseStrategy extends RouteReuseStrategy { shouldDetach(route: ActivatedRou

Intercepting and adjusting SQL generated by Eclipselink JPA

In some cases it might be useful to intercept and adjust the SQL generated by EclipseLink JPA. E.g. if you want to force an index in mysql you need to append force index (myindex) to the table name. If you create a query on the entitymanager: Query q = em.createQuery("select e from MyEntity"); you can cast it to the EclipseLink JpaQuery: JpaQuery jq = (JpaQuery)q; and the JpaQuery gives you access to the EclipseLink DataBaseQuery where you can prepare it before executing it: DatabaseQuery dbQuery = q.getDatabaseQuery(); dbQuery.prepareCall(((org.eclipse.persistence.jpa.JpaEntityManager)em).getActiveSession(),new DatabaseRecord()); You can now get the sql string and add the forced index: dbQuery.setSQLString(dbQuery.getSQLString()+" force index (myindex)"); and finally you can get the resultset using q.getResultList(). If you have parameters in the sql it's a bit more to it. Currently I've only found one option - probably not optimal since the query is transl