[ https://hibernate.onjira.com/browse/HSEARCH-1130?page=com.atlassian.jira.... ] Emmanuel Bernard updated HSEARCH-1130: -------------------------------------- Description: Today, entities must depend on Coordinates (implementing or via a property returning Coordinates). We can imagine the following {code} @Spatial(name=home") class User { @Latitude(for="home") Double homeLatitude; @Longitude(for="home") Double homeLongitude; } {code} 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 was: Today, entities must depend on Coordinates (implementing or via a property returning Coordinates). We can imagine the following {code} @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 -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira