Those pesky @XmlRootElement annotations
Posted: Tue Jan 26, 2010 10:53 am
Hello, everyone,
First, thank you for the docx4j library.
I'm using the library to generate Word documents based on data retrieved from an application's database, and the library is streamlining the process quite a bit.
One nuisance I've encountered is in creating tables. It seems a couple of the table-related nodes don't have the @XmlRootElement annotation and so generate an error when trying to save the document (and implicitly marshal the XML).
I saw that someone else in another thread (link below) ran into an issue with the missing @XmlRootElement annotations. In that case, there was a workaround since the marshaling was being done explicitly. However, in my case, the marshaling is being done when the WordprocessingMLPackage.save() call gets down to that particular element.
I realize that these classes org.docx4j.wml.* are generated automatically, and I am downloading the source so that I can add in the annotations and rebuild the library. Is there any quicker way to handle this case? It is a bit tedious to rebuild the library from source every time I encounter a new one of these.
Missing @XmlRootElement annotations; deepCopy (cloning) thread: http://dev.plutext.org/forums/viewtopic.php?f=6&t=206&start=0&hilit=annotation&sid=6a2cd4245f7348a3d340c669d02da4f0
First, thank you for the docx4j library.
I'm using the library to generate Word documents based on data retrieved from an application's database, and the library is streamlining the process quite a bit.
One nuisance I've encountered is in creating tables. It seems a couple of the table-related nodes don't have the @XmlRootElement annotation and so generate an error when trying to save the document (and implicitly marshal the XML).
I saw that someone else in another thread (link below) ran into an issue with the missing @XmlRootElement annotations. In that case, there was a workaround since the marshaling was being done explicitly. However, in my case, the marshaling is being done when the WordprocessingMLPackage.save() call gets down to that particular element.
I realize that these classes org.docx4j.wml.* are generated automatically, and I am downloading the source so that I can add in the annotations and rebuild the library. Is there any quicker way to handle this case? It is a bit tedious to rebuild the library from source every time I encounter a new one of these.
Missing @XmlRootElement annotations; deepCopy (cloning) thread: http://dev.plutext.org/forums/viewtopic.php?f=6&t=206&start=0&hilit=annotation&sid=6a2cd4245f7348a3d340c669d02da4f0