Skip to content

Fixes the usage of this plugin by Grails applications that do not have a relational DB data source#5

Open
aruizca wants to merge 1 commit intocandrews:masterfrom
aruizca:master
Open

Fixes the usage of this plugin by Grails applications that do not have a relational DB data source#5
aruizca wants to merge 1 commit intocandrews:masterfrom
aruizca:master

Conversation

@aruizca
Copy link
Copy Markdown

@aruizca aruizca commented Jul 9, 2015

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

…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
@aruizca
Copy link
Copy Markdown
Author

aruizca commented Jul 9, 2015

@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

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant