Content-Length: 213558 | pFad | http://github.com/objectify/objectify/issues/412

41 In PolymorphicGenericClassTests, member name in class Car is considered a generic type at registration time · Issue #412 · objectify/objectify · GitHub
Skip to content

In PolymorphicGenericClassTests, member name in class Car is considered a generic type at registration time #412

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

Open
Meffi42 opened this issue Dec 15, 2018 · 0 comments

Comments

@Meffi42
Copy link

Meffi42 commented Dec 15, 2018

Hello team, I was looking at the Objectify unit tests:

When class Car in PolymorphicGenericClassTests.java is registered,
it is already known at registration time that the generic type parameter T from superclass Vehicle is really a String. This information is readily accessible via Car.class.getGenericSuperclass().

However, the registration process does not consider this.
Instead, it seems Objectify must resolve at runtime how the name property is to be stored in Datastore.

I was wondering whether it is a worhwhile optimization to adapt the registration process.

Thanks.

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

No branches or pull requests

2 participants








ApplySandwichStrip

pFad - (p)hone/(F)rame/(a)nonymizer/(d)eclutterfier!      Saves Data!


--- a PPN by Garber Painting Akron. With Image Size Reduction included!

Fetched URL: http://github.com/objectify/objectify/issues/412

Alternative Proxies:

Alternative Proxy

pFad Proxy

pFad v3 Proxy

pFad v4 Proxy