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

Add section on dependency management for Spring Data modules and Spring Framework to the reference documentation [DATACMNS-687] #1154

Closed
spring-projects-issues opened this issue May 1, 2015 · 4 comments
Assignees

Comments

@spring-projects-issues
Copy link

@spring-projects-issues spring-projects-issues commented May 1, 2015

Caleb Cushing opened DATACMNS-687 and commented

I'm having trouble telling if this is a valid bug from the documentation because I'm not sure if Spring Data 1.7+ should actually work on 3.2, but it does say that it should work without spring so I assume Spring 3.2 is a valid target. This error does not exist in 1.6.5

I'm getting the following exception trying to autowire an empty repository (meaning I haven't defined additional methods) that extends PagingAndSortingRepository

org.springframework.beans.factory.UnsatisfiedDependencyException: Error creating bean with name 'organizationActivityLogDtoSupplier' defined in file [/Users/ccushing/IdeaProjects/dex/dex-service-api/target/classes/com/mckesson/dex/service/resource/OrganizationActivityLogDtoSupplier.class]: Unsatisfied dependency expressed through constructor argument with index 0 of type [com.mckesson.dex.repository.OrganizationActivityLogRepository]: : Error creating bean with name 'organizationActivityLogRepository': Cannot resolve reference to bean 'jpaMappingContext' while setting bean property 'mappingContext'; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'jpaMappingContext': Invocation of init method failed; nested exception is java.lang.NoClassDefFoundError: org/springframework/core/DefaultParameterNameDiscoverer; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'organizationActivityLogRepository': Cannot resolve reference to bean 'jpaMappingContext' while setting bean property 'mappingContext'; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'jpaMappingContext': Invocation of init method failed; nested exception is java.lang.NoClassDefFoundError: org/springframework/core/DefaultParameterNameDiscoverer

Affects: 1.8.5 (Dijkstra SR5), 1.9.2 (Evans SR2), 1.10 GA (Fowler)

Issue Links:

  • DATAJPA-714 Include new section on Spring Data and Spring Framework dependencies in reference documentation

  • DATAMONGO-1213 Include new section on Spring Data and Spring Framework dependencies in reference documentation

Backported to: 1.10.1 (Fowler SR1), 1.9.3 (Evans SR3)

@spring-projects-issues
Copy link
Author

@spring-projects-issues spring-projects-issues commented May 1, 2015

Oliver Drotbohm commented

The Dijkstra release train (and thus Spring Data JPA 1.6.5) is the last one compatible with Spring 3.x. Both Evans and Fowler require Spring 4.0, the upcoming release train Gosling will require Spring 4.1

@spring-projects-issues
Copy link
Author

@spring-projects-issues spring-projects-issues commented May 1, 2015

Caleb Cushing commented

so I read through the changelog linked from the site, could these (minimum) dependencies be made more clear there or maybe in the docs somewhere? this seems like a trial and error process currently

@spring-projects-issues
Copy link
Author

@spring-projects-issues spring-projects-issues commented May 2, 2015

Oliver Drotbohm commented

Good point. We'll tweak the reference documentation accordingly

@spring-projects-issues
Copy link
Author

@spring-projects-issues spring-projects-issues commented May 4, 2015

Oliver Drotbohm commented

I took the chance to add a more in-depth section to the reference documentation in Spring Data Commons to describe ways of selecting the right combination of Spring Data modules and Spring Framework dependencies. Downstream dependencies need to explicitly include this section and will follow up with the according commits. I've already adapted JPA and MongoDB and deployed a snapshot build of the new sections.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
2 participants
You can’t perform that action at this time.