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

2.0.x. Issue #27 about default JMS plugin configuration #28

Merged
merged 5 commits into from
Jan 2, 2017

Conversation

aulea
Copy link
Contributor

@aulea aulea commented Nov 15, 2016

No description provided.

Alar Aule added 3 commits November 15, 2016 13:04
… master branch DefaultJmsBeans.groovy and merging it and application specific configuration together before registering spring beans.
… branch it doesn't register JMS beans, when it is disabled from configuration.
… master branch DefaultJmsBeans.groovy and merging it and application specific configuration together before registering spring beans.
@rlovtangen
Copy link
Contributor

When upgrading from 2.0.0.M1 to 2.0.0.RC1 in a Grails 3.1.11 application I get "Could not resolve parent bean definition 'standardJmsListenerAdapter'" during startup.
These defaults seems to fix that problem.

@antoineroux
Copy link
Contributor

I had the same issue and I would find it useful to have such defaults.

@aulea
Copy link
Contributor Author

aulea commented Nov 25, 2016

I updated my pull request now with better merge local and default configs.
Added also some unit tests to validate it.

@graemerocher graemerocher merged commit 479324d into gpc:2.0.x Jan 2, 2017
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.

4 participants