Hi all,
I’m having a strange issue with Aspose.Words where dateTime fields are sometimes (randomly) parsed incorrectly.
I have a Java class with some Date fields like:
@XmlElement(name = "my_date", required = false, nillable = false)
private Date myDate;
From this class I use a jaxb Marshaller to create the xml (ByteArrayOutputStream). I save the xml for debug purposes and I can see that the date is ALWAYS correct in the xml.
Then I create the XmlDataSource from the xml and the xsd:
XmlDataSource dataSource = new XmlDataSource(xmlData, xsdData);
In the xsd the date field is defined like this:
<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema">
<xs:element name="my_datasource">
<xs:complexType>
<xs:sequence>
...
<xs:element name="my_date" type="xs:dateTime" nillable="true" minOccurs="0"/>
...
Finally I do:
ReportingEngine engine = new ReportingEngine();
engine.buildReport(document, dataSource, "my_datasource");
where document is the word template.
When I open the document sometimes I find 01.01.0001 instead of the correct date, for example 28.02.2025 (in the template I have <<[my_date]:“dd.MM.yyyy”>>).
Since the date in the xml is ALWAYS correct (for example 2025-02-28T00:00:00+01:00) I thought I would output the content of the dataSource like this:
Object zzYdX = FieldUtils.readField(dataSource, "zzYdX", true);
DataRow zzWrp = (DataRow) FieldUtils.readField(zzYdX, "zzWrp", true);
String content = zzWrp.toString();
System.out.println(content);
zzYdX and zzWrp are the names of the compiled fields (may differ). This was the only way read the dataSource content since all its fields are private.
To my surprise that’s where I found the error: when I get 01.01.0001 in the final document then I also get Sat Jan 01 01:00:00 CET 1 in the dataSource.
So the problem is that sometimes the same date is parsed incorrectly when creating the dataSource.
I must add that I’m working in a multithreaded environment although a single document is always handled by only one thread.
I’m running Aspose.Words version 23.3
Do you have any clue why this is happening?