Justin Lee
Justin Lee
There are references in the annotation to classes outside the annotations (reference related mostly). Those classes, obviously, have references to other classes and so on. So simply extracting out the...
Any time. If nothing else, that reminder about jackson's mixins (which I'd forgotten about) is a good thing to consider for the next version. 2.3 should be a big one.
Feature wise. No API changes like 1.6->2.0. i knew 2.0 was going to be a huge shift and was meant to be. it tried to clean up years of cruft....
OK. so morphia.next should have this. I know i've been kicking this can down the road but things are in better shape for a clean separation. I'm not sure if...
Where did this one end up, @dfjones ?
I don't have an update, per se, I just wanted to check that this issue hadn't already been resolved via another effort. There was a flurry of discussions and issues...
So I'm finally digging in to this and this is actually how it *should* work. If you don't want the discriminators you can set `useDiscriminator = false` on your `@Entity`...
That's a fair point actually. We're up against a few conflicting goals and I'm not sure I have the data to make the decision myself. Historically, `useDiscriminator` has just applied...
the discriminators are used heavily for polymorphic containers (Lists, Sets, Maps, etc.) and polymorphic collections and queries. Given 2.0's ability to define custom (read: small) discriminator values, I'm actually leaning...
probably will close either this one or #829 as a duplicate but for now i'll track both for 2.2