News of WebSphere (and Domino)

Hi,
We have a strange case using importXHTML. We have a process deployed in websphere where we build a html document and then convert this html to docx. On the server we deploy the following libs:

docx4j-core-8.3.14.jar
docx4j-ImportXHTML-8.3.11.jar
jaxb-runtime-2.3.2.jar
docx4j-JAXB-ReferenceImpl-8.3.14.jar

(with others)

When we run the process we have the exception:

Exception creating document: java.lang.RuntimeException: javax.xml.bind.PropertyException: property "com.sun.xml.bind.namespacePrefixMapper" must be an instance of type com.sun.xml.bind.marshaller.NamespacePrefixMapper, not org.docx4j.jaxb.ri.NamespacePrefixMapper
at org.docx4j.XmlUtils.marshaltoString(XmlUtils.java:941)
at org.docx4j.XmlUtils.marshaltoString(XmlUtils.java:857)
at org.docx4j.XmlUtils.marshaltoString(XmlUtils.java:797)
at org.docx4j.convert.in.xhtml.XHTMLImporterImpl.addParagraphProperties(XHTMLImporterImpl.java:2471) ...

Hi all

To jump right into it: My current understanding is that docx4j does not work with Webpshere Liberty . Please prove me wrong :-) More below.

We're migrating away from Websphere to Liberty. Docx4j worked on Websphere 8.5, with docx4j 3.3.3.

I cannot get things to work on Liberty. Running latest AdoptOpenJDK 8 hotspot version, and tried Liberty kernel versions 8.5.5.9 through 20.0.0.8, and docx4j ...

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/

I am able to run docx4j within Eclipse. But when I deploy to WebSphere 7+, along with dependent JAR files, I get the following exception. I noticed there was an article for this for Weblogic 12c indicating updating eclipselink.jar. I don't see this under Websphere. I have spent several hours debugging this and am not sure if I am running into conflicts with including JAR files into this app with existing jar files. Any suggestions ...

Interesting post on changing the ClassLoader context during the PDF conversion

See http://guedebyte.wordpress.com/2013/02/ ... oi4xpages/

Hi Jason,
I am also facing the same issue,is it possible to skip the class loader for the JAXB in context.java

Code: Select all

try {
          Class.forName("com.sun.xml.bind.marshaller.MinimumEscapeHandler");
          log.info("JAXB: Using RI");

       } catch (ClassNotFoundException cnfe) {
          // JAXB Reference Implementation not present
         log.info("JAXB: RI not present.  Trying Java 6 implementation.");

and try the Java 6 implementation,as our deployment environment is on java6 .

if its possible could you give me the new build of doc4j with this change

Hello All,

I try to implement docx4j 2.7.1 in an Lotus Domino 8.5.3 Xpages Environment. On Windows 32-Bit with Java 1.6 Runtime.

If I try to create a Package with

Code: Select all

WordprocessingMLPackage wordMLPackage = WordprocessingMLPackage.createPackage();

I get an Exception. It seems, that the Class org.docx4j.jaxb.Context gets an uncaught Exception during the class loading process.

It seems further, that this exception occurs during this statement in org.docx4j.jaxb.Context.java on line 71

// JBOSS might use a different ...

Hello!

In IBM WebSphere i got javax.xml.parsers.FactoryConfigurationError: Provider com.sun.org.apache.xerces.internal.jaxp.DocumentBuilderFactoryImpl not found.
org.docx4j.openpackaging.parts.XmlPart makes:

Code: Select all

System.setProperty("javax.xml.parsers.DocumentBuilderFactory",
"com.sun.org.apache.xerces.internal.jaxp.DocumentBuilderFactoryImpl");

Is it possible to use org.apache.xerces.jaxp.DocumentBuilderFactoryImpl from xerces2?

Thanks.