Should Throw Error When No ID Field Exists/Is Specified about ravendb-jvm-client HOT 3 CLOSED

This is by design. You are not forced to use id field, and if you don't specify one (or override the defaults), RavenDB will manage the id for you internally.
You can get the document id after the store using session.advanced().getDocumentId(testOrder);

from ravendb-jvm-client.

@ayende Thanks for the clarification. It would be more dev friendly if this were prominently documented somewhere (I culdn't find this on your website), and even better if a Warning got logged when you call store that it's being managed internally.

from ravendb-jvm-client.

That is a feature, not an issue. There is a valid use case for not making the entity id as a field on the entity.
This is the same as Hibernate or JPA model. For example, in Hibernate, see: https://docs.jboss.org/hibernate/orm/3.5/javadocs/org/hibernate/Session.html#getIdentifier(java.lang.Object)

from ravendb-jvm-client.