Did your development team discusses about the recommendations for use of Hibernate / JPA? about springblog

[Raysmond]

Did you read my code or not?

[tacianosilva]

Hi @Raysmond,

I read your code. I tested the design rules recommended the Hibernate documentation and the JPA specification. I found the following results:

Rule NoArgumentConstructorRule: All entities passed (They are OK).
Rule ProvideIdentifierPropertyRule: All entities passed (They are OK).
Rule NoFinalClassRule: All entities passed (They are OK).
Rule ProvideGetsSetsFieldsRule: All entities passed (They are OK).

Rule HashCodeAndEqualsRule: All entities failed (Recommendation Hibernate Docs).
com.raysmond.blog.models.Tag
com.raysmond.blog.models.User
com.raysmond.blog.models.Setting
com.raysmond.blog.models.Post

Rule UseSetCollectionRule: Two entities failed.
com.raysmond.blog.models.Tag
com.raysmond.blog.models.User

Rule ImplementsSerializableRule: All entities failed (Recommendation of the JPA Spec).
com.raysmond.blog.models.Tag
com.raysmond.blog.models.User
com.raysmond.blog.models.Setting
com.raysmond.blog.models.Post

Do you think these software projects have latent bugs caused by the design rules violations or is the rule unnecessary?

[tacianosilva]

Hi @Raysmond,

What did you think of the results of Design Tests?

Best regards!

[Raysmond]

If you indeed study my code, you'll know there's no such problem.

[tacianosilva]

Really your code is correct. My tests did not check the superclass.

I have only one question:

Why the post attribute in the User class is List (ArrayList) and It is not Set (HashSet) as the others?

Thank you for your attention and your time. You helped me a lot.

[Raysmond]

Are there any big problems using List? Cause I think it's ok with me. Besides, the post list is user class is never used.