Skip to content

DATAMONGO-892 - Provide meaningful error message when registering converter as nested bean. #165

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

Closed
wants to merge 3 commits into from

Conversation

christophstrobl
Copy link
Member

Mapping information is potentially required by multiple instances and should not be registered within a Template as nested bean. The current solution did throw a misleading error which has been corrected.

Register mapping converter as uniquely named bean in context and wire conversions correctly to avoid overriding existing ones.
…verter as nested bean.

Mapping information is potentially required by multiple instances and should not be registered within a template as nested bean. The current solution did throw a misleading error which has been corrected.

Original Pull Request: #165
@artembilan
Copy link
Member

LGTM!

christophstrobl added a commit that referenced this pull request Apr 15, 2014
Mapping information is potentially required by multiple instances and thus must not be registered as nested bean. We now actively check for such an invalid scenario and explicitly reject it.

Original pull request: #165.
christophstrobl added a commit that referenced this pull request Apr 15, 2014
Mapping information is potentially required by multiple instances and thus must not be registered as nested bean. We now actively check for such an invalid scenario and explicitly reject it.

Original pull request: #165.
@odrotbohm odrotbohm closed this Apr 15, 2014
@odrotbohm odrotbohm deleted the issue/DATAMONGO-892 branch April 15, 2014 07:11
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.

3 participants