Stickies

To get docx4j working in any of these environments, you do 2 things in your project.

First, use maven to add docx4j-JAXB-ReferenceImpl as a dependency

Second, create src/main/webapp/WEB-INF/jboss-deployment-structure.xml containing

<jboss-deployment-structure>
<deployment>
<dependencies>
<module name="com.sun.xml.bind" />
</dependencies>
</deployment>
</jboss-deployment-structure>


See further https://access.redhat.com/solutions/4284651

We have tested/confirmed this config on EAP 7.2.9, 7.3, 7.3.3 and WildFly 20.0.1

There is no need to make any system-wide config change.

https://www.docx4java.org/blog/2020/09/ ... x4j-8-2-3/ contrasts 3 alternatives for getting PDF output.

If you are generating documents and PDF is your one and only output format, then you might be interested in https://www.docx4java.org/blog/2020/09/ ... ng-xsl-fo/

Current docx4j works with WebSphere versions 8.5.5.9 and 9.0.0.5 in WebSphere’s default configuration (ie no need to change anything outside of your ear/war, except your security policy if enforced). docx4j v3.3.7 is recommended, since it contains an IBM JAXB specific fix.

For more, see https://www.docx4java.org/blog/2018/03/ ... here-2018/

Docx4j4Android4 is an Android Studio docx4j sample app.

Its a proof of concept of docx4j 3.3.2 (with a couple of minor changes) running on Android.

See further https://github.com/plutext/Docx4j4Android4

JBoss AS7 has a class loading mechanism which is different from previous versions. See generally:

https://docs.jboss.org/author/display/A ... ing+in+AS7

It includes a module named javax.xml.bind.api; to get docx4j working in your WAR, you just need to include WEB-INF/jboss-deployment-structure.xml containing:


<jboss-deployment-structure xmlns="urn:jboss:deployment-structure:1.1">

<deployment>
<dependencies>

<module name="com.sun.xml.bind" />

</dependencies>
</deployment>
</jboss-deployment-structure>


Details/discussion

jboss-as-7.1.1.Final\modules\javax\xml\bind\api\main says:


<module xmlns="urn:jboss:module:1.1" name="javax.xml.bind.api">


<dependencies>
<module name="javax.activation.api" export="true"/>
<module name="javax.xml.stream.api"/>
<module name="com.sun.xml.bind" services="import"/>
<module name="javax.api"/>
</dependencies> ...

This post brings together some web wisdom on getting docx4j working in WebLogic, where old JAXB implementations cause problems.

Rather than comment on this thread, please use a discussion with subject:

"WebLogic x.y.z with EclipseLink MOXy"

OR

"WebLogic x.y.z with Glassfish RI JAXB"

as appropriate.

Background

For Oracle WebLogic Server 12c Release 1 (12.1.1), http://docs.oracle.com/cd/E24329_01/web ... _types.htm says:

WebLogic Server provides two data binding and JAXB providers:

EclipseLink ...

FOP 1.0 and 1.1 are affected by an issue documented and partially worked around by:


// Workaround for https://issues.apache.org/bugzilla/show ... i?id=54094
// You can comment this out if you are using FOP post 1.1
// (see pom.xml for tips on how to configure that)
Object o = wordMLPackage.getMainDocumentPart().getContent().get(0);
if (o instanceof P
&& ((P)o).getPPr()!=null) {
PPr pPr = ((P)o).getPPr();
BooleanDefaultTrue val = new BooleanDefaultTrue();
val.setVal(Boolean.FALSE);
pPr.setPageBreakBefore(val);
}
...