Support @Spatial without depending on the Coordinates class

Description

Today, entities must depend on Coordinates (implementing or via a property returning Coordinates).

We can imagine the following

1 2 3 4 5 6 7 8 @Spatial(name=home") class User { @Latitude(for="home") Double homeLatitude; @Longitude(for="home") Double homeLongitude; }

Note that we will need to support @Spatials as well in this case (check AbstractDocumentBuilder initializeMemberLevelAnnotations() and checkForFields() as we will need a checkForSpatials()

This feature can wait for after the main spatial pull request

Environment

None

Status

Assignee

Nicolas Helleringer

Reporter

Emmanuel Bernard

Labels

None

Suitable for new contributors

Yes, likely

Pull Request

None

Feedback Requested

None

Components

Fix versions

Priority

Major