|
From: Peter S. <co...@pe...> - 2007-07-23 07:25:44
|
Hi Roberto, Read inline comments. On 7/20/07, Roberto Milev <rob...@gm...> wrote: > > Hi Peter, > > Read comments inline. > > On 7/20/07, Peter Salomonsen <co...@pe...> wrote: > > > > Hi Roberto, > > > > The XML servlet is great, and it's much better to use in iReport. Did > > you > > manage to use the remote xml datasource? (I had some problems with it..) > > This > > would be even better. > > > I did not consider a remote xml datasource. Does this refer to loading > form URL? > Yes it's an iReport feature.. You can specify an xml datasource from a url. One downside with the xml datasource, is that the Report Wizard won't accept > > > > it. Is there a way around this? Suggestions? > > > Do you mean the report wizart inside the metalog applet? If yes, then this > is covered because xml datasources correspond to saved searches. > No, the report wizard in iReport. Somehow it doesn't seem to support xml datasources. No big deal though. About this: > > > > http://localhost:8080/lmas-addons-example/reportservlet?reportName=Report_1 > > > > > > It does always delete my report - and I know it's because of the "Print > > current report" function - but could we make it possible get an > > on-demand pdf > > without deleting? > > > > Further - in addition to pdf - could we also get an Excel doc - just > > like when > > using the excel preview function in iReport? > > > > Maybe introduce some switches? : > > > > http://localhost:8080/lmas-addons-example/reportservlet?reportName=Report_1&type=excel&delete=false > > > > (other types pdf, and the print current report could use delete=true) > > > yes the type and delete switches sound ok. > > And - regarding xsl transformation (to google kml's and other htmls) - any > > suggestions on how to solve this? Should we introduce xsl template > > uploading? > > We can use the reportservlet for also viewing xsl reports, the servlet > > will > > figure out if the template used is xsl? > > > I suggest we expand the report template table and add fields for content > type and file extension. For content type we would support: pdf, excel, xml > (xml would be used for xsl templates, and the file extension could be html, > klm, etc.). the xsl templates could be loaded in the same manner, > additionally the file extension should be specified on the upload page. I > see the foolwing possibilities for using the URL switches: > > -reportName > - type: pdf, excel, xml > - delete: true, false > > -searchName > - type: excel, xml > - template: (any saved template in the db) > - delete: true, false > > What do you think? > Sounds ok to me. cheers, Peter |