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

[transaction] [map] TransactionalMapProxy depends on MapContainer #10254

Closed
vbekiaris opened this issue Apr 7, 2017 · 3 comments
Closed

[transaction] [map] TransactionalMapProxy depends on MapContainer #10254

vbekiaris opened this issue Apr 7, 2017 · 3 comments

Comments

@vbekiaris
Copy link
Contributor

@vbekiaris vbekiaris commented Apr 7, 2017

Creating a TransactionalMapProxy should not also trigger creation of the backing MapContainer.

@mmedenjak
Copy link
Contributor

@mmedenjak mmedenjak commented Jul 10, 2017

@vbekiaris can this be closed now?

@vbekiaris
Copy link
Contributor Author

@vbekiaris vbekiaris commented Jul 11, 2017

The fix for TransactionalMap is still pending.

@mmedenjak mmedenjak changed the title TransactionalMapProxy depends on MapContainer [transaction] [map] TransactionalMapProxy depends on MapContainer Jul 11, 2017
@Donnerbart Donnerbart self-assigned this Aug 22, 2017
@Donnerbart
Copy link
Contributor

@Donnerbart Donnerbart commented Aug 22, 2017

I started to work on this, but I'm stuck a bit on the RecordFactory dependency. All other fields could be initialized via the MapConfig, without the MapContainer: #11192

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.

3 participants
You can’t perform that action at this time.