Opened 11 years ago
Closed 10 years ago
#364 closed defect (fixed)
Serialization annotation's body
Reported by: | olhsha | Owned by: | olhsha |
---|---|---|---|
Priority: | major | Milestone: | |
Component: | DASISH backend | Version: | |
Keywords: | Cc: | olhsha |
Description (last modified by )
There must be some serialization/deserialization mechanism for annotation bodies:
-- "body" in the DB is just a text;
-- "body" in a JAXB-generated class is a list of objects.
Moreover, the server needs to change annotation's body when replacing temporary new-source references in the body with the persistent ones, when these sources are added to the DB.
For now, I use simple "serialize" and "deserialize" Helpers' procedures which should be replaced by some proper marshalling-demarshalling. For simple serialization I treat the first element of the list
of objects above as a text whcich corresponds to the DB column "body_xml".
Change History (7)
comment:1 Changed 11 years ago by
Cc: | olhsha added |
---|
comment:2 Changed 11 years ago by
Description: | modified (diff) |
---|---|
Summary: | Serialization/Marchalling the body → Serialization annotation's body |
comment:3 Changed 11 years ago by
Description: | modified (diff) |
---|
comment:4 Changed 11 years ago by
Description: | modified (diff) |
---|
comment:5 Changed 11 years ago by
Description: | modified (diff) |
---|
comment:6 Changed 11 years ago by
comment:7 Changed 10 years ago by
Resolution: | → fixed |
---|---|
Status: | new → closed |
So, according to our 18/09 meeting the schema is changed! It looks as follows:
The database is changed so that the column "body_xml" in the table "annotation" is replaced with two ones: "body_text" and "body_mimetype". The corresponding adjustments in the code and in the unit tests are done. So far, no special serialization menachisme is used. The question: what does the client need to do to be able to represent the annotation body properly?