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

ProjectionDefinitionConfiguration does not select projection for most concrete type [DATAREST-747] #1119

Closed
spring-projects-issues opened this issue Jan 11, 2016 · 0 comments
Assignees
Labels
type: bug

Comments

@spring-projects-issues
Copy link

@spring-projects-issues spring-projects-issues commented Jan 11, 2016

Oliver Drotbohm opened DATAREST-747 and commented

If two projections of the same name are registered for an inheritance hierarchy, the current projection selection algorithm doesn't necessarily prefer the projection defined for the most concrete type


Affects: 2.4.2 (Gosling SR2)

Issue Links:

  • DATAREST-739 Using different projection for each entity subtype
    ("is depended on by")

Referenced from: commits c49754e, 3c411d1

Backported to: 2.4.4 (Gosling SR4)

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

No branches or pull requests

2 participants