WANTED: Feature Requests! .. and opinions!

[jason]

Some gaping hole in docx4j's features?

Please post your feature request to just-created http://docx4j.userecho.com/, though of course feel free to discuss here first.

As that page says:

Here you can suggest features you'd like to see added to docx4j, or vote for features already suggested.

The idea is to be able to prioritise development efforts.

Use your votes wisely...

If it is for pptx or xlsx components, please put [pptx] or [xlsx] in the title.

Please use the real docx4j forums or StackOverflow for general questions, and GitHub for bugs/issues. To keep things clean, anything of that nature posted here will be deleted.

Developers: if you are working on one of the nominated features in a fork on GitHub, please feel free to comment here to that effect.

[andyflint]

Think that docx4j is a great tool.

One addition I would like to see is the ability to return the entire document or parts as a byteArrayOutputStream

There WordProcessingMLDocument has a load method that can receive a byteArrayInputStream so why can't it have a method for returning a byteArrayOutputStream.

Many thanks


Andy

[andyflint]

Urgently need support for more fields particularly IF fields

[marcel_cap]

If it not exists :
- A way to insert external jpeg in a .docx. (in order to have all jpeg in an external directory)

[jason]

I've just closed down http://docx4j.userecho.com/, since in the 18 months since it was created, for whatever reason it has been little used relative to the number of docx4j users. Maybe yet another login is just too much effort..

In any case, the three top rated suggestions have all been implemented:

- XHTML import: font color (6 votes)

- Feedback - Logging, Free choice of logging framework (4 votes)

- Support number of pages when convert Docx to PDF (4 votes)

If anyone has a suggestion for a better way of quantifying demand for new features, please suggest..

The natural thing to use is https://github.com/plutext/docx4j/issues?state=open .. it doesn't seem to have votes though, so we'd have to use "most commented" as a proxy.

[nicky]

Request: Clean up the dependencies. They are very complicated. And because of this complicated dependecies it is difficult to use docx4j in a JBoss AppServer.

[jason]

Thanks for the suggestion.

Here is the dependency tree (for current nightly):

Code: Select all

org.docx4j:docx4j
+- org.plutext:jaxb-svg11:jar:1.0.2
+- org.plutext:jaxb-xslfo:jar:1.0.1
+- org.plutext:jaxb-xmldsig-core:jar:1.0.0

+- net.engio:mbassador:jar:1.1.10   <-----------new!
+- org.slf4j:slf4j-api:jar:1.7.5
+- commons-lang:commons-lang:jar:2.4
+- commons-codec:commons-codec:jar:1.3
+- commons-io:commons-io:jar:1.3.1
+- org.apache.xmlgraphics:xmlgraphics-commons:jar:1.5

+- org.apache.xmlgraphics:fop:jar:1.1
|  +- org.apache.xmlgraphics:batik-svg-dom:jar:1.7
|  |  +- org.apache.xmlgraphics:batik-anim:jar:1.7
|  |  +- org.apache.xmlgraphics:batik-css:jar:1.7
|  |  +- org.apache.xmlgraphics:batik-dom:jar:1.7
|  |  +- org.apache.xmlgraphics:batik-parser:jar:1.7
|  |  \- org.apache.xmlgraphics:batik-util:jar:1.7
|  +- org.apache.xmlgraphics:batik-bridge:jar:1.7
|  |  +- org.apache.xmlgraphics:batik-script:jar:1.7
|  |  \- org.apache.xmlgraphics:batik-xml:jar:1.7
|  +- org.apache.xmlgraphics:batik-awt-util:jar:1.7
|  +- org.apache.xmlgraphics:batik-gvt:jar:1.7
|  +- org.apache.xmlgraphics:batik-transcoder:jar:1.7
|  |  \- org.apache.xmlgraphics:batik-svggen:jar:1.7
|  +- org.apache.xmlgraphics:batik-extension:jar:1.7
|  \- org.apache.xmlgraphics:batik-ext:jar:1.7
+- commons-logging:commons-logging:jar:1.1.1
+- org.apache.avalon.framework:avalon-framework-api:jar:4.3.1
+- org.apache.avalon.framework:avalon-framework-impl:jar:4.3.1

+- xalan:xalan:jar:2.7.1
|  \- xalan:serializer:jar:2.7.1

+- net.arnx:wmf2svg:jar:0.9.0
+- org.apache.poi:poi-scratchpad:jar:3.8
|  \- org.apache.poi:poi:jar:3.8
+- org.antlr:antlr-runtime:jar:3.3
+- org.antlr:stringtemplate:jar:3.2.1
|  \- antlr:antlr:jar:2.7.7

      Optional:
       +- org.eclipse.persistence:org.eclipse.persistence.moxy:jar:2.5.1:compile
       |  +- org.eclipse.persistence:org.eclipse.persistence.core:jar:2.5.1:compile
       |  |  \- org.eclipse.persistence:org.eclipse.persistence.asm:jar:2.5.1:compile
       |  \- org.eclipse.persistence:org.eclipse.persistence.antlr:jar:2.5.1:compile



What is causing you problems in JBoss? You can answer that question in the deployment forum for JBoss.

We try not to add extra dependencies lightly, and have succeeded in getting rid of some in the past. That said, there's not a lot of scope for trimming them:-

1. A lot of the dependencies come from FOP. You might be able to get away without them if you don't use XSL FO output.
2. Currently you need the 'real' Xalan; eventually you won't, but don't hold your breath!
3. POI could be made optional