Skip to content
This repository has been archived by the owner on Jun 29, 2021. It is now read-only.

METAMODEL-1133: Made PojoDataContext thread-safe with CopyOnWrite list #138

Closed
wants to merge 1 commit into from
Closed

METAMODEL-1133: Made PojoDataContext thread-safe with CopyOnWrite list #138

wants to merge 1 commit into from

Conversation

kaspersorensen
Copy link
Contributor

My Suggested fix for METAMODEL-1133.

Copy link
Contributor

@tomaszguzialek tomaszguzialek left a comment

Choose a reason for hiding this comment

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

LGTM.

Copy link
Contributor

@LosD LosD left a comment

Choose a reason for hiding this comment

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

LGTMtoo. Merging

@LosD
Copy link
Contributor

LosD commented Dec 27, 2016

Errr... Apparently I am not. Having some permission issues from my home computer to the Apache Git repo.

If someone feels like doing the last step of the merge, you can pull the "squashed" (not much real squashing done, more or less just auto-closes this PR 😄) commit from my repo, then push to ASF repo.

@kaspersorensen kaspersorensen deleted the METAMODEL-1133/thread-safe-pojodatacontext branch January 28, 2017 04:09
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
3 participants