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

DATACMNS-557 - Add support for custom implementations in CDI #92

Closed
wants to merge 5 commits into from
Closed

Conversation

mp911de
Copy link
Member

@mp911de mp911de commented Aug 7, 2014

This PR is a prerequisite for further adoption in the spring-data-* modules.

@odrotbohm
Copy link
Member

That looks decent, Mark. I think I can take it from there. Would you mind signing the CLA and report the confirmation number back here?

@mp911de
Copy link
Member Author

mp911de commented Aug 7, 2014

Cool, thank you. The confirmation no is 88820140806073332

@odrotbohm
Copy link
Member

Brilliant, thanks. I've polished the stuff slightly and have it ready to push. I'll take the test cases from your PR in the JPA module to adapt it right away.

odrotbohm pushed a commit that referenced this pull request Aug 7, 2014
…tructure.

The CDI extension now discovers a custom implementation class similarly to the detection when using Spring Data in a Spring container. Extracted the custom implementation detection for re-use. The CDI extension discovers the potentially available bean and hands it to the CdiRepositoryBean for further usage.

Implementations should implement the extended variant of the create(…) method we introduce with this commit to be able to forward the resolved custom implementation bean.

Original pull request: #92.
odrotbohm added a commit that referenced this pull request Aug 7, 2014
Renamed CdiRepositoryConfigurationSource to CdiRepositoryConfiguration. Turned anonymous inner default implementation into dedicated enum to avoid repeated instantiation.

Changed the CdiRepositoryBean to rather take a Bean instance of the custom implementation instead of the resolved object to make sure both instances (the custom implementation and the repository proxy) are instantiated at the same time.

Fixed imports. Some early returns to avoid unnecessary nesting.

Adapted architecture description to allow CDI module accessing the configuration module.

Related pull request: #92.
@odrotbohm
Copy link
Member

That's applied, JPA parts coming ASAP.

@odrotbohm odrotbohm closed this Aug 7, 2014
@odrotbohm odrotbohm changed the title DATACMNS-557 Custom JPA repositories with CDI DATACMNS-557 - Add support for custom implementations in CDI Aug 7, 2014
Aloren pushed a commit to Aloren/spring-data-commons that referenced this pull request Jun 20, 2019
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.

None yet

2 participants