Skip to content

Why is annotating mappable classes necessary? #2970

Description

@bendherville

We are migrating from morphia 1.x to 2.4 and having to add annotations to all of our classes that are used as top-level or embedded types (there are lots of them). Not complaining about doing work :) but the question is why is this necessary in v2.4? Can't it be assumed that a type being persisted is mappable and use the same defaults as applied to classes annotated with @Entity?

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Fields

    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions