Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

TransactionService bean is not registered after upgrade to 4.0.4 or 4.1.0.M2 #1389

Closed
arixmkii opened this issue Sep 30, 2020 · 0 comments
Closed
Assignees
Milestone

Comments

@arixmkii
Copy link

After upgrade application fails to start with bean not resolved exception. The bean represents a service from Gorm Hibernate: grails.gorm.transactions.TransactionService

Code example which fails in Grails 4.0.4 or 4.1.0 milestones:

  • Add this snippet to any service in a grails project with Gorm Hibernate:
@Autowired
TransactionService transactionService

Actual result:

  • application will fail to start

Expected result:

  • bean is resolved, application works as before

Workaround (doesn't look suitable for production):

  • one can manually register an instance of org.grails.datastore.gorm.services.DefaultTransactionService as bean.

Details on what is TransactionService: http:https://gorm.grails.org/7.1.x/hibernate/manual/#_using_transactionservice

@puneetbehl puneetbehl self-assigned this Oct 12, 2020
@puneetbehl puneetbehl transferred this issue from grails/grails-core Oct 12, 2020
puneetbehl referenced this issue Oct 12, 2020
* Rename loadDataServices -> loadServices.
* Correctly load the services so that TransactionService and TenantService are also injected.
@puneetbehl puneetbehl transferred this issue from grails/gorm-hibernate5 Oct 25, 2020
@puneetbehl puneetbehl added this to the 7.0.8 milestone Oct 25, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants