Spring aspectj jar not configured correctly

Question

I am getting this error when I tried to use a JPA object created by Roo.

Entity manager has not been injected (is the Spring Aspects JAR configured as an AJC/AJDT aspects library?)

I have followed some online advice to add the spring-aspects.jar to aspectj path in Eclipse but I still get this error. Does anyone know how to solve this?

The environment I am using is Spring 3.0.5, Hibernate 3.6 and JBoss 6.0.0.Final.

I encountered same problem. I'm using ant (instead of pom) to build the project, could this be the root cause of the problem? — Aaron Yang, Jun 10 '12 at 02:52

score 1 · Answer 1 · answered Jun 21 '12 at 18:12

1

Go to STS ROO console (right click in the project in STS, then Spring Tools, then Open Spring Roo) Type in the prompt perform clean (will perform Maven clean) Then type perform eclipse

It should work!

answered Jun 21 '12 at 18:12

Michel Bilodeau

19
1

When I try this, I can't type in the prompt. The window shows "Roo installation 'Roo 1.2.1.RELEASE' points to non-existing path 'C:\SpringSource\spring-roo-1.2.1.RELEASE\'." – pete the pagan-gerbil Apr 09 '13 at 10:09

score 1 · Answer 2 · answered Aug 16 '12 at 20:54

Looks like you haven't injected Entity Manager.

Webapps (possible causes):

You didn't add entity manager factory to your applicationContext.xml

Java Applications:

You didn't add entity manager factory to your applicationContext.xml

Wrong application initialization (see below)

public class SampleApp {
    public static void main(String[] args) {
        SampleApp obj = new SampleApp();

        // Injecting dependencies into application
        ConfigurableApplicationContext applicationContext = 
                new ClassPathXmlApplicationContext("<PATH-TO>/applicationContext.xml");
        applicationContext.registerShutdownHook();
        applicationContext.getBeanFactory().autowireBeanProperties(
                obj, AutowireCapableBeanFactory.AUTOWIRE_NO, false);

        // Do the work
    }
}

How can one check the applicationContext.xml to tell if an entity manager factory has been added correctly? — pete the pagan-gerbil, Apr 09 '13 at 10:11

score 1 · Answer 3 · answered Jul 23 '13 at 10:08

I had this problem too, and found the answer here: http://whyjava.wordpress.com/2012/02/13/fixing-exception-entity-manager-has-not-been-injected-is-the-spring-aspects-jar-configured-as-an-ajcajdt-aspects-library/

In my case, I needed to create a file called <classname>_Roo_Configurable.aj with the following content:

privileged aspect <classname>_Roo_Configurable { declare @type: <classname>: @Configurable; }

This explained why existing classes worked but new ones that I had created did not. The _Configurable.aj file did not (and still does not) show up in the package explorer in STS.

(I know this answer is incredibly late but I hope it helps someone else!)

score 0 · Answer 4 · answered Aug 17 '15 at 09:34

0

You have to create the repository for the indicate domain.

In roo-terminal run the follow script

es.

 repository jpa --interface ~.dao.MyDomainDAO --entity ~.domain.MyDomain

answered Aug 17 '15 at 09:34

Flavio Troia

2,451
1
25
27

score 0 · Answer 5 · answered Jul 11 '11 at 04:10

0

I was having this same issue and fixed it by doing Spring Tools | Enable Spring Aspects Tooling on my project.

My classes were generated by Roo and pushed in (I was having way too many issues with it), and I simply added them to a brand new Google Web Application Project I created (so it uses GAE's app layout with a war directory, and no Maven for anything, at least not yet).

answered Jul 11 '11 at 04:10

minimo

1,396
1
9
9

I am having the same problem, and this solution did nothing. – pete the pagan-gerbil Apr 09 '13 at 10:10

Spring aspectj jar not configured correctly

5 Answers5