Skip to content

MappingMongoConverterParser is incorrectly rejecting field-naming-strategy-ref XML configuration [DATAMONGO-925] #3526

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
spring-projects-issues opened this issue May 2, 2014 · 2 comments
Assignees
Labels
in: core Issues in core support type: bug A general bug

Comments

@spring-projects-issues
Copy link

Neil Rutherford opened DATAMONGO-925 and commented

We are using the latest 1.5.0.BUILD-SNAPSHOT and when trying to use the new field naming strategy xml configuration from DATAMONGO-866 like so:

<mongo:mapping-converter field-naming-strategy-ref="namingStrategy" />

We are getting rejected by the MappingMongoConverterParser check for using both abbreviate-field-names and field-naming-strategy-ref.

This seems to happen when the abbreviate-field-names attribute is read and because we haven't set it - it defaults to what is defined in the schema which is "false" and because we have set field-naming-strategy-ref we get the "Only one of the attributes abbreviate-field-names and field-naming-strategy-ref can be configured!" error.

We have worked around this by setting the abbreviate-field-names attribute to "", like so:

<mongo:mapping-converter field-naming-strategy-ref="namingStrategy" abbreviate-field-names="" />


Issue Links:

Referenced from: pull request #177, and commits 0f821eb, e3aadd6, 84e6504, 57d5eb2

@spring-projects-issues
Copy link
Author

Thomas Darimont commented

Please review

@spring-projects-issues
Copy link
Author

Oliver Drotbohm commented

See DATAMONGO-928 for comments

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
in: core Issues in core support type: bug A general bug
Projects
None yet
Development

No branches or pull requests

2 participants