Closed GoogleCodeExporter closed 9 years ago
[deleted comment]
Hi,
I'm going to have a look. There must be an issue with circular relationship.
Beside, do you need bidirectional relationships are not usually a good idea. Do
you really need bi-directionnal relation between your classes ?
best regards
Original comment by pascal.leclercq
on 6 Apr 2014 at 9:07
Can you please attach a sample docx that you use ?
This would help me.
Thx.
Original comment by pascal.leclercq
on 7 Apr 2014 at 7:42
[deleted comment]
Hi,
I experimented a little more. Found out that it's not list of chilfren reason
deceleration. In my opinion the cause of my very complex data model. Very many
bidirectional relationships and in original my model is hibernate entities i.e.
we have more sophisticated annotations. Apparently slowing quite normal for
your processing algorithm.
I attache full data model classes and template docx. Slowdown occurs when I
call
fieldsMetadata.load("passport", Passport.class);
Before document generation.
Best regards.
Original comment by cimo...@gmail.com
on 8 Apr 2014 at 4:32
Hi,
I can reproduce but I don't think we should fix this issue. Your model is too
complex IMHO with a lot of circular references between classes. This lead us to
24242 fields for fieldsMetadata and a huge 6 Mb fieldsMetadata.xml
file.
I think you should map your model to a simpler one dedicated to the report you
want to produce and/or remove bidirectional relationships in your model.
Best regards
Original comment by pascal.leclercq
on 8 Apr 2014 at 9:32
At first I thought fieldsMetadata.load was necessary for the use of the model
in the template, but then realized that enough use fieldsMetadata.addfild metod
(I do not use a macro). I call it twice. For the entire model and its field
list. This for my project is complete enough.
Thank you very much for your advice!
Best regards.
Original comment by cimo...@gmail.com
on 9 Apr 2014 at 4:00
Hi Pascal,
Many thank's for your investigation about this issue. I tell me, perhaps (if
it's possible), we should throw an exception when there is too circular
references :
1) use a default max circular references value.
2) customize this max value with FieldsMetadata#setMaxCircularReferences
What do you think about that?
Regards Angelo
Original comment by angelo.z...@gmail.com
on 9 Apr 2014 at 5:09
cleanup
Original comment by pascal.leclercq
on 10 Oct 2014 at 7:37
Original issue reported on code.google.com by
cimo...@gmail.com
on 6 Apr 2014 at 10:38