Hibernate & JAXB / JSON (message model and data model)

Question

This is a matter of philosophy of philosophy on how to closely tie messaging to your data model.

Given the pojo object, I can annotate it with Hibernate, JAXB, and JSON annotations so that the same class can be written to the database, as well as serialized / deserialized for messaging. The convenience factor is really high, because it means that I do not need to write translation classes to convert messages to classes that are used for the database (which is important for boredom and maintenance).

However, this has always bothered me, because it links your interface and messages to the structure and design of your data model. For certain types of applications, messages may be exactly what you want to save in the database, and in other cases it is a subset of the database fields.

Is there a better way to separate them without exposing myself to the tedious translation / conversion classes? Is there a pattern that I can use to at least better combine message and data?

Answer 1

I completely agree with your concern ... this is one gray area, because it really depends on the problems of your domain that you are trying to solve.

, . , (, Javascript) , . JSON/XML , .

, -, , ( ). JSON/XML, . , . , beans, , , beans. , JSON/XML .

Answer 2

@XmlPath EclipseLink JAXB (MOXy), ( MOXy):

• JAXB2: Java