by davebrown » Thu Apr 28, 2011 9:11 am
I spent some time trying to minimize the delay, to no avail. There are just too many classes in the docx4j/JAXB hierarchy, and there's no way around loading a lot of them before you can do anything. Jason did some work separating some classes into separate JAXB context, presumably in an effort to minimize this delay.
The product where I use docx4j is in a server, so the delay is not too bad.