Understood, and I recognize that (the act of persisting an embedded document was due to an error in my code originally which led me to the noted odd behavior). So, if I do persist and embedded document (and subsequently flush it) shouldn't the act of doing a `persist ()`(and possible `flush()`) on an embedded document be a no-op? And the data would be persisted/flushed when the parent document is persisted/flushed?

What I'm noticing in the case where I explicitly (albeit, erroneously) call `persist()` and `flush()` is that the embedded document is not getting committed to the database _only when I also explicitly assign an ID manually_. Please let me know if you're not seeing that behavior in the database collection when running the tests.