I know that 23.10 version work without problem
And I tried to check changes in 23.11 and fix problem in WORDSJR-367, WORDSJR-371, WORDSJR-375.
All my changes and fixes didn’t work for this task.
In WORDSJR-377 I will test Customer Web project that reproduce this error and tried to find origin of this problem.
Ok. thanks for the information. Additionally I am attaching my stacktrace from version 23.11 (which as I mentioned is very similar) and it appears when the code executes the last instruction:
AWDocxExporter exporter = new AWDocxExporter();
exporter.reset();
exporter.setExporterInput(new SimpleExporterInput(jp));
File exportReportFile = new File( outputFileNameNew );
exporter.setExporterOutput(new SimpleOutputStreamExporterOutput(exportReportFile));
exporter.exportReport();
Exception in thread "main" java.lang.VerifyError: Bad type on operand stack
Exception Details:
Location:
com/aspose/words/jasperreports/internal/awjr274.a(Lcom/aspose/words/jasperreports/internal/awjr48;Ljava/lang/StringBuilder;)I @113: invokespecial
Reason:
Type 'com/aspose/words/jasperreports/internal/awjr48' (current frame, stack[0]) is not assignable to 'com/aspose/words/jasperreports/internal/awjr274'
Current Frame:
bci: @113
flags: { }
locals: { 'com/aspose/words/jasperreports/internal/awjr48', 'java/lang/StringBuilder', integer, 'com/aspose/words/jasperreports/internal/awjr295', 'com/aspose/words/jasperreports/internal/awjr6362', 'com/aspose/words/jasperreports/internal/awjr252', 'com/aspose/words/jasperreports/internal/awjr295', top, 'com/aspose/words/jasperreports/internal/awjr48', 'com/aspose/words/jasperreports/internal/awjr295' }
stack: { 'com/aspose/words/jasperreports/internal/awjr48', 'com/aspose/words/jasperreports/internal/awjr295', integer }
Bytecode:
0x0000000: 033d 014e 013a 042a 593a 08b4 005c 3a05
0x0000010: 1905 c600 9f19 05b6 0076 1015 a000 6a19
0x0000020: 05c0 0015 3a06 2dc6 0059 1906 1021 b800
0x0000030: ec3a 0719 04c7 000b 2d10 21b8 00ec 3a04
0x0000040: 1907 1904 b800 f999 0031 2bb6 0106 9a00
0x0000050: 0c2b 2db6 00a3 b800 6a57 2b19 06b6 00a3
0x0000060: b800 6a57 8402 012a 2d3a 0959 3a08 1909
0x0000070: 03b7 00e1 57a7 000b 2d2b b800 7b01 3a04
0x0000080: 1906 4ea7 000d 2d2b b800 7b01 4e01 3a04
0x0000090: 1905 b600 7610 1ca0 000d 1905 c000 1b2b
0x00000a0: b800 7c57 1905 593a 08b4 004c 3a05 a7ff
0x00000b0: 622d 2bb8 007b 1cac
Stackmap Table:
full_frame(@16,{Object[#42],Object[#63],Integer,Object[#21],Object[#52],Object[#17]},{})
append_frame(@64,Object[#21],Object[#52])
chop_frame(@90,1)
full_frame(@120,{Object[#42],Object[#63],Integer,Object[#21],Top,Object[#17],Object[#21]},{})
full_frame(@128,{Object[#42],Object[#63],Integer,Top,Object[#52],Object[#17],Object[#21]},{})
full_frame(@134,{Object[#42],Object[#63],Integer,Object[#21],Top,Object[#17]},{})
full_frame(@144,{Object[#42],Object[#63],Integer,Object[#21],Object[#52],Object[#17]},{})
same_frame(@164)
full_frame(@177,{Top,Object[#63],Integer,Object[#21]},{})
at com.aspose.words.jasperreports.internal.awjr6420.aBw(Unknown Source)
at com.aspose.words.jasperreports.internal.awjr4370.n(Unknown Source)
at com.aspose.words.jasperreports.internal.awjr4370.a(Unknown Source)
at com.aspose.words.jasperreports.internal.awjr4370.a(Unknown Source)
at com.aspose.words.jasperreports.internal.awjr4370.a(Unknown Source)
at com.aspose.words.jasperreports.internal.awjr4370.lV(Unknown Source)
at com.aspose.words.jasperreports.internal.awjr3683.acT(Unknown Source)
at com.aspose.words.jasperreports.internal.awjr5775.acT(Unknown Source)
at com.aspose.words.jasperreports.internal.awjr65.b(Unknown Source)
at com.aspose.words.jasperreports.internal.awjr65.a(Unknown Source)
at com.aspose.words.jasperreports.internal.awjr65.c(Unknown Source)
at com.aspose.words.jasperreports.internal.awjr65.<init>(Unknown Source)
at com.aspose.words.jasperreports.internal.awjr65.<init>(Unknown Source)
at com.aspose.words.jasperreports.internal.awjr67.<init>(Unknown Source)
at com.aspose.words.jasperreports.internal.awjr3239.<init>(Unknown Source)
at com.aspose.words.jasperreports.AWAbstractExporter.exportReport(Unknown Source)
at com.bitsa.jasper_test.Jasper_test.ExportToDOCX_NEW(Jasper_test.java:133)
at com.bitsa.jasper_test.Jasper_test.main(Jasper_test.java:61)
Command execution failed.
org.apache.commons.exec.ExecuteException: Process exited with an error: 1 (Exit value: 1)
at org.apache.commons.exec.DefaultExecutor.executeInternal (DefaultExecutor.java:404)
at org.apache.commons.exec.DefaultExecutor.execute (DefaultExecutor.java:166)
at org.codehaus.mojo.exec.ExecMojo.executeCommandLine (ExecMojo.java:1000)
at org.codehaus.mojo.exec.ExecMojo.executeCommandLine (ExecMojo.java:947)
at org.codehaus.mojo.exec.ExecMojo.execute (ExecMojo.java:471)
at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo (DefaultBuildPluginManager.java:126)
at org.apache.maven.lifecycle.internal.MojoExecutor.doExecute2 (MojoExecutor.java:328)
at org.apache.maven.lifecycle.internal.MojoExecutor.doExecute (MojoExecutor.java:316)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:212)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:174)
at org.apache.maven.lifecycle.internal.MojoExecutor.access$000 (MojoExecutor.java:75)
at org.apache.maven.lifecycle.internal.MojoExecutor$1.run (MojoExecutor.java:162)
at org.apache.maven.plugin.DefaultMojosExecutionStrategy.execute (DefaultMojosExecutionStrategy.java:39)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:159)
at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject (LifecycleModuleBuilder.java:105)
at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject (LifecycleModuleBuilder.java:73)
at org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build (SingleThreadedBuilder.java:53)
at org.apache.maven.lifecycle.internal.LifecycleStarter.execute (LifecycleStarter.java:118)
at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:261)
at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:173)
at org.apache.maven.DefaultMaven.execute (DefaultMaven.java:101)
at org.apache.maven.cli.MavenCli.execute (MavenCli.java:906)
at org.apache.maven.cli.MavenCli.doMain (MavenCli.java:283)
at org.apache.maven.cli.MavenCli.main (MavenCli.java:206)
at sun.reflect.NativeMethodAccessorImpl.invoke0 (Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke (NativeMethodAccessorImpl.java:62)
at sun.reflect.DelegatingMethodAccessorImpl.invoke (DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke (Method.java:498)
at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced (Launcher.java:283)
at org.codehaus.plexus.classworlds.launcher.Launcher.launch (Launcher.java:226)
at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode (Launcher.java:407)
at org.codehaus.plexus.classworlds.launcher.Launcher.main (Launcher.java:348)
Hi @TomiLi123
I can’t find solution for VerifyError and now we have to update version without error.
Now I added several version of 23.10 release with latest features and bug fixes that we added in regular version.
https://releases.aspose.com/words/jasperreports/new-releases/aspose.words-for-jasperreports-23.10.3/
Thanks @anatoly.sidorenko
I checked version 23.10.3 and it seems this bug doesn’t occur.
I have another important question: does Aspose.Words for JasperReports support bullets/paragraph numbering in the body?
In our example, we used HTML formatting ([ol], [li] tags) in the TextField, but the output document doesn’t contain bullets at all. How can we fix this?
Hi @TomiLi123
for including bullet and numbering list you should use
currentExporter.setParameter(AWExporterParameter.ALLOW_HTML_LISTS, true);
@anatoly.sidorenko OK. can I set this somehow also by properties in our templete - jrxml file?
ex. [property name=“net.sf.jasperreports.export.docx.flexible.row.height” value=“true”/]
because we generate output files from jasperserver via rest API and not directly from Java
Hi @TomiLi123
All parameters can be set in applicationContext.xml with JasperServer
For example this is instruction to set License:
https://docs.aspose.com/words/jasperreports/licensing/#set-the-licensefile-exporter-parameter-in-applicationcontextxml
In our case we can set parameters similarly:
<bean id="aw_exportParameters" class="com.aspose.words.jasperreports.AWExportParametersBean">
<property name="allowHtmlLists" value="true"/>
</bean>
Also you can try [property name=“com.aspose.words.allow.html.lists” value=“true”/] in jrxml file, but I can’t be sure that it works.
@anatoly.sidorenko
curently in file \apache-tomcat\webapps\jasperserver\WEB-INF\applicationContext.xml I have:
<bean id="aw_exportParameters" class="com.aspose.words.jasperreports.AWExportParametersBean">
<property name="fontMap">
<util:map id="fontMap">
<entry key="sansserif" value="Arial"/>
<entry key="serif" value="Times New Roman"/>
<entry key="monospaced" value="Courier"/>
</util:map>
</property>
<!-- Uncomment to apply a license. Check the license path. -->
<property name="licenseFile" value="/opt/Aspose.WordsforJasperReports.lic"/>
<property name="allowHtmlLists" value="true"/>
</bean>
but when I started JasperServer I see errors:
2025-10-23T21:58:48,940 ERROR ContextLoader,Catalina-utility-3:313 - Context initialization failed org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'aw_exportParameters' defined in ServletContext resource [/WEB-INF/applicationContext.xml]: Error setting property values; nested exception is org.springframework.beans.NotWritablePropertyException: Invalid property 'allowHtmlLists' of bean class [com.aspose.words.jasperreports.AWExportParametersBean]: Bean property 'allowHtmlLists' is not writable or has an invalid setter method. Does the parameter type of the setter match the return type of the getter?
Setting this property in jrxml file also not working.
@anabellepaulson
We have opened the following new ticket(s) in our internal issue tracking system and will deliver their fixes according to the terms mentioned in Free Support Policies.
Issue ID(s): WORDSJR-402
You can obtain Paid Support Services if you need support on a priority basis, along with the direct access to our Paid Support management team.
@alexey.noskov ok. thank you, we are looking forward to hearing about this, we need to evaluate how this functionality works in our environment before purchasing a commercial license.
Best regards
TL>
The issues you have found earlier (filed as WORDSJR-402) have been fixed in this Aspose.Words for JasperReports 25.10 update.
@alexey.noskov @anatoly.sidorenko
That’s great, but the last version I managed to run in our environment was 23.10.3 (all newer versions cause the startup errors described earlier in this thread).
Therefore, I kindly ask you to add this fix to version 23.10.3 as well.
@TomiLi123 The issues you have found earlier (filed as WORDSJR-402) have been fixed in this Aspose.Words for JasperReports 23.10.4 hotfix.
@alexey.noskov
I tried version 23.10.4, but unfortunately, it didn’t work.
Jasper Server with the option
<property name="allowHtmlLists" value="true"/>
started correctly this time, but the resulting docx file still lacks bullet points. I have no idea what could be wrong.
I’m attaching a fragment of the document template from Jasper Studio, the Preview in Jasper Server/pdf, and after saving to docx.
Hi @TomiLi123
I see similar behavior in our tests,
can you wrap your list in to span tag like this:
<span style=\"display:left\">
<ul>
<li>Test1</li>
<li>Test2</li>
<li>Test3</li>
</ul>
</span>
In out tests it help to write several lists in one paragraph.
Also I will notice that html list features didn’t work then list wrapped from one page to another. Page Break broke list structure, so we emulate list with symbols and indents.
Unfortunately, adding <span> tags doesn’t change anything in our environment; we still don’t see bullet points ( <ul> or <ol>) in the docx files.
We’re using the library: aspose.words.jasperreports-23.10.4-7.8.0-8.0.0.jar
on JasperServer 8.1.1
I also tried a new, blank report without any additional elements.
I have no other ideas.
@TomiLi123 Anatoly is currently busy with Aspose.Words for java release preparations. Could you please attach your simple test jrprint and problematic output document produced on your side? This will help us to investigate the problem further.