De: Tim Colson <[email protected]>
Para: [email protected] >Enviado: Viernes, 23 de agosto, 2013 6:31:15 >Asunto: Advice on using/extending ExcelExporter > > > >Hi everyone -- > > >We've built a Click app for Confluence wiki management, and we want to give >users an Excel export of a data table filled with metadata for wiki pages in >for a specific Confluence space key. I googled and was happily surprised to >find the Excel Export example for Apache Click. Woot! >(http://click.avoka.com/click-examples/general/excel-table-export.htm) > > >Looked easy enough, but the developer realized TableExporter was part of the >examples package, and needs additional supporting classes and properties >files, so he tried copying into our project, but ran into problems. > > > >Have you looked at the source code for the examples? It is available when you get click from svn, I see many properties files included along with supporting classes needed for the examples to work. > >I'm sorry but currently I'm too busy to look closely myself, maybe later since >this could be useful to me sometime. > > > > >1) TableExportContainer.renderExportBanner() >-- Provides the link to the report, but is failing to load the properties >file, is there some configuration that might need to be done? > > >2) Link with arguments >As a hack around #1, I replaced the banner code with a hard-coded >MessageFormat.format("<span class=\"{0}\">Export options: [{1}]</span>", args); >-- The link does not include the original URL parameter for SPACKEY which is >needed to load the pages for a particular space from the DB. >-- Looks like we need to try exportTable.setExportLink( ) to embed the params >in the URL? Setup an ActionLink? PageLink? Need to create a new method to get >the data? Confused here. > >3) Best way to Leverage the ExcelExporter classes >The classes are doing a lot of heavy lifting with POI, but copying them seems >like a bad idea long term. Suggestions? > > >-Tim > > > > > > > > >
