StimVinsh / xdocreport

Automatically exported from code.google.com/p/xdocreport
0 stars 0 forks source link

Persist reports (templates) #15

Open GoogleCodeExporter opened 8 years ago

GoogleCodeExporter commented 8 years ago
We should be able to persist (in a DB for instance) the report.

Reports should be still available after to redeploy of the webapp..

Original issue reported on code.google.com by pascal.leclercq on 6 Jun 2011 at 9:52

GoogleCodeExporter commented 8 years ago
[deleted comment]
GoogleCodeExporter commented 8 years ago
Hi, 
I have a proposal, What you think if for this purposes will link DataModel with 
some report using annotations, and in annotation will be indicated the template 
loader?

 For example:
@MetadataModelDescription(reportTemplateBaseName="default-template",
                templateType="ODT",
                templateLoader=SomeTemplateLoaderImplimentation.class
        value="Default Proof Dod Tempalte Model."                
)

This annotation for the moment is attached to the root class of 
templateDataModel.

For the moment I use this annotation for generate fields.xml with description 
for the model. Later I have to implement the persistence functionality(in any 
case but I would like to see functionality inside of XDocReport).

And I agree, but in this case we will have some restriction: One model one 
template, but it will not be a problem to manage manually(like is now) the 
template and templateDataModel.

Original comment by ruslancu...@gmail.com on 21 Feb 2013 at 6:57

GoogleCodeExporter commented 8 years ago
I think to use annotation in the model to help the generation of fields 
metadata is a good idea but not for the persist feature. As you have said you 
can have one template and N model.

I think the original idea of this issue was to set JPA annotations in the 
IXDocReport classes to store the report config (template engine, docx/odt 
template, etc).

Original comment by angelo.z...@gmail.com on 21 Feb 2013 at 8:55