You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm using this in a Spring (Boot) application so have followed the instructions to create the JsonViewSupportFactoryBean Bean however its not excluding the excluded entity field at all. The excluded field is a reference to another domain entity.
However the resulting REST response has the runidentity instance which by the way contains a reference to Attitudestate. I want to simply ignore runidentity in the REST response as it already has runidentityId. I can do this with which I can do with @JsonIgnore in the entity but I would prefer to not change my entities.
The text was updated successfully, but these errors were encountered:
I'm using this in a Spring (Boot) application so have followed the instructions to create the JsonViewSupportFactoryBean Bean however its not excluding the excluded entity field at all. The excluded field is a reference to another domain entity.
Here is the entity:
`public class Attitudestate
implements java.io.Serializable,
UniquelyIdentified
{
private Long id;
private Runcatalog runidentity;
private Integer runidentityId;
private Double gpstime;
private Date utctimestamp;
private transient Double[] attitude;
private Float attitudeerror;
private Float currentangularrate;
private Float angularrateerror;
In my controller I have:
`private JsonResult json = JsonResult.instance();
public Page findByRunIdentityId(Integer runidentityId, Pageable pageable)
{
Page attitudestates = repository.findByRunIdentityId(runidentityId, pageable);
However the resulting REST response has the runidentity instance which by the way contains a reference to Attitudestate. I want to simply ignore runidentity in the REST response as it already has runidentityId. I can do this with which I can do with @JsonIgnore in the entity but I would prefer to not change my entities.
The text was updated successfully, but these errors were encountered: