Should "persistent" field appear in serialized PanacheEntity?

Question

I am building a simple Jaxrs api in quarkus. When I call my index method it looks like jackson serializes the objects with the persistent field, that it gets from the PanacheEntityBase. Example: [ { "persistent": true, "id": 1, "createdAt": "2019-03-18", "updatedAt": "2019-03-18" }, { "persistent": true, "id": 2, "createdAt": "2019-03-18", "updatedAt": "2019-03-18" } ] The persistent field isn't saved to the database, but it shows up in the response. I have looked into using @jsonIgnore and jackson mixins, but I would rather not have to do this, especially if this is just a configuration issue. I am curious if Panache should be doing this, or if anyone else is having this problem. JavaScript questions and answers, JavaScript questions pdf, JavaScript question bank, JavaScript questions and answers pdf, mcq on JavaScript pdf, JavaScript questions and solutions, JavaScript mcq Test , Interview JavaScript questions, JavaScript Questions for Interview, JavaScript MCQ (Multiple Choice Questions)

Answer 1

This happens when we use 3-rd party libraries as returned data type and provide it to Jackson serialisation process. PanacheEntity extends PanacheEntityBase which contains isPersistent method which is treated by Jackson like a POJO getter method. public boolean isPersistent() { return JpaOperations.isPersistent(this); } Jackson automatically takes all get* and is* methods and try to serialise it and include to result JSON. There is no way to configure it on quarkus level. Your solution with JsonIgnore and MixIn feature is good approach.