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

[ARIES-1992] Fix loss of PU override properties #9

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

sunshinebeauty93
Copy link

Memorize override PU props even if the required DataSource is not yet
available. Always merge the memorized props into the static PU props
before publishing an EntityManagerFactory.
We have hold on to the override props although we might not yet be able
to create an EntityManagerFactory, since we will not be notified about
the updated props again.

Resolves: ARIES-1992

Memorize override PU props even if the required DataSource is not yet
available. Always merge the memorized props into the static PU props
before publishing an EntityManagerFactory.
We have hold on to the override props although we might not yet be able
to create an EntityManagerFactory, since we will not be notified about
the updated props again.

Resolves: ARIES-1992
@sunshinebeauty93 sunshinebeauty93 changed the title Fix loss of PU override properties [ARIES-1992] Fix loss of PU override properties Feb 11, 2021
@sunshinebeauty93
Copy link
Author

How can we continue with this?
Travis does not seem to like it, but I am not able to establish a connection between the Travis-CI error and this change. Can someone help please?
Also, this does not seem to generate a lot of interest. Would it help to provide a Karaf itest via PR to demonstrate that overriding properties via .cfg file does not work in versions past 2.6.1

@@ -83,6 +83,7 @@

private boolean complete;

private Map<String, Object> overrides;
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

if i get it right this is normally set only once at a time (when the config changes), so maybe make it an AtomicReference ?

@jbonofre jbonofre self-requested a review July 26, 2021 14:27
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