Sign Up

Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.

Have an account? Sign In

Have an account? Sign In Now

Sign In

Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.

Sign Up Here

Forgot Password?

Don't have account, Sign Up Here

Forgot Password

Lost your password? Please enter your email address. You will receive a link and will create a new password via email.

Have an account? Sign In Now

You must login to ask a question.

Forgot Password?

Need An Account, Sign Up Here

Please briefly explain why you feel this question should be reported.

Please briefly explain why you feel this answer should be reported.

Please briefly explain why you feel this user should be reported.

Sign InSign Up

The Archive Base

The Archive Base Logo The Archive Base Logo

The Archive Base Navigation

  • SEARCH
  • Home
  • About Us
  • Blog
  • Contact Us
Search
Ask A Question

Mobile menu

Close
Ask a Question
  • Home
  • Add group
  • Groups page
  • Feed
  • User Profile
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Buy Points
  • Users
  • Help
  • Buy Theme
  • SEARCH
Home/ Questions/Q 7961035
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Editorial Team
Asked: June 4, 20262026-06-04T04:55:11+00:00 2026-06-04T04:55:11+00:00

I am upgrading current project from Roo 1.1.5 to 1.2.1. I have noticed there

  • 0

I am upgrading current project from Roo 1.1.5 to 1.2.1.

I have noticed there are some new features in Roo 1.2.1 to facilitate JPA functionality, i.e. @RooEntity to @RooJpaActiveRecord, but I thought when I open Roo shell in STS it could handler that conversion automatically…I can still achieve that manually, however, after I change the annotation name, no matter I use poll now or re-build the project, all the getter/setter/finder/entityManager are error out due to no AspectJ injection, actually I can see the aspectJ files are generated, STS just cannot identify them with the entity java file. So suddenly the whole project falls apart.

Please, geniuses on the stack, let me know how to fix that. Many thanks in advance.

  • 1 1 Answer
  • 0 Views
  • 0 Followers
  • 0
Share
  • Facebook
  • Report

Leave an answer
Cancel reply

You must login to add an answer.

Forgot Password?

Need An Account, Sign Up Here

1 Answer

  • Voted
  • Oldest
  • Recent
  • Random
  1. Editorial Team
    Editorial Team
    2026-06-04T04:55:13+00:00Added an answer on June 4, 2026 at 4:55 am

    I have figured out the solution:

    Simply speaking: make sure running the project as a Maven project.

    How: Right click project->Configure->Convert to Maven Project. Then run Right click project -> Maven -> Update Project Configuration.

    Maven will build the project once again with aspect injection. I think the problem is previously my project is compiled under Spring Tools -> Update Maven Dependencies where if the STS/AspectJ Tool stop working, then the project will suffer from missing aspect injection(still thinking it is could be a remaining bug of STS, this issue may be very specific but still STS fail the job).

    Sorry I have to answer my own question

    • 0
    • Reply
    • Share
      Share
      • Share on Facebook
      • Share on Twitter
      • Share on LinkedIn
      • Share on WhatsApp
      • Report

Sidebar

Related Questions

Upgrading from ASP.NET WebAPI Beta to RC has provided some amount of excitement and
I'm upgrading our project from Hibernate 3.0 to Hibernate 4.1.6. (And we are currently
I am having trouble upgrading my current project to use RIA Services. I added
While uploading my current project to our staging server I noticed that the Web.config
We are currently upgrading a current data import process we have written in C#.
A quick and easy answer I'm sure. I'm upgrading a Rails project from version
I'm working in a project that uses the new ASP.NET WebAPI. My current task
I have a problem in upgrading an old data model to a current model.
Is there a preferred method of gracefully upgrading a web site? I have a
I'm upgrading a script to make it crosss browser. The current code I have

Explore

  • Home
  • Add group
  • Groups page
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Users
  • Help
  • SEARCH

Footer

© 2021 The Archive Base. All Rights Reserved
With Love by The Archive Base

Insert/edit link

Enter the destination URL

Or link to existing content

    No search term specified. Showing recent items. Search or use up and down arrow keys to select an item.