Currently, the bean properties used in @Spatial fields must either be public or have a public getter, while other, more standard fields don't have this limitation (we use setAccessible() as necessary).

That's because we don't use the same techniques to access fields in SpatialFieldBridge as we do everywhere else. We probably should, but this will require breaking APIs (yes, the SpatialFieldBridge class is API...).