I would have expected it to transparently generate a boolean AND query on two (more) Spatial queries, using the same center and radius; to implement it, that's very simple.. but ok I'll avoid that as it doesn't make practical sense to search on multiple coordinates (I can't find a convincing example).

Emmanuel Bernard suggested to use an explicit

onDefaultCoordinates()

and we agreed to change the default field name:

<emmanuel> Well @Spatial has two default cases
<emmanuel> one for properties and the default value is clear here
<emmanuel> one for class level and then we need an arbitrary name
<emmanuel> "_hibernate_class" is what we use for classes
<emmanuel> maybe we should sue the same convention
<emmanuel> "_hibernate_default_coordinates"
<sannegrinovero> looks good to me, but it's postfixed by HSSI and then Latitude / Longitude
<emmanuel> k

Nicolas Helleringer we have your blessing?

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira