Skip to content

Unable to Implement Custom Tuplizer Due to Internal Constructor in DynamicMapEntityTuplizer #3602

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

Closed
Ganesh13024 opened this issue Aug 26, 2024 · 1 comment · Fixed by #3603

Comments

@Ganesh13024
Copy link

In the NHibernate documentation (Chapter 4.5. Tuplizers), it's mentioned that it's possible to extend NHibernate.Tuple.Entity.DynamicMapEntityTuplizer and create a custom tuplizer. However, when attempting to do so, I found that the constructor for this class is marked as internal, which prevents users from implementing a custom tuplizer if NHibernate is used as a NuGet package.

The constructor of DynamicMapEntityTuplizer should be public, allowing developers to extend this class and implement custom tuplizers as described in the documentation.

@fredericDelaporte
Copy link
Member

fredericDelaporte commented Sep 1, 2024

See this nhusers convertation which is partly about that.

Indeed, it is internal since 2007, and that was overlooked when this example was introduced in the documentation in 2009. Since the PocoEntityTuplizer has its constructor public, it would also be more consistent.

Component tuplizers, including the dynamic one, have their constructor public, too.

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

Successfully merging a pull request may close this issue.

2 participants