Fixes the usage of this plugin by Grails applications that do not have a relational DB data source #5
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…e a relational DB data source. Eg: front-end that only uses web services to access data When no datasource is present in the DataSource.groovy file, a transaction manager is not created and therefore the services with a @transaction annotation fails at runtime It is the same scenario as the one described in this stackoverflow entry http://stackoverflow.com/questions/10296382/developing-grails-plugin-no-bean-named-transactionmanager-is-defined-in-inte Regardless of this error, since all the DB operations performed to generate a report are read-only, a transactions is not required
|
@candrews Are you still maintaining this plugin? |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Eg: front-end app that only uses web services to access data
When no datasource is present in the DataSource.groovy file, a transaction manager is not created and therefore the services with a @transaction annotation fail at runtime
It is the same scenario as the one described in this stackoverflow entry: http://stackoverflow.com/questions/10296382/developing-grails-plugin-no-bean-named-transactionmanager-is-defined-in-inte
Regardless of this error, since all the DB operations performed to generate a report are read-only, a transaction is not required.
Cheers