Re: Excel Generator

[Johan Kok]

Yves, That means you will have to use POI to read the files and then go for conversion to XML... Look at the following: "If you're merely reading spreadsheet data, then use the eventmodel api in the org.apache.poi.hssf.eventusermodel package."  (from the POI HSSF page) Johan Kok Yves Vindevogel wrote: I agree that converting Excel to XML would be better. BUT, it's out of the question for this project. I need to read the real files. -----Original Message----- From: Johan Kok [mailto:[EMAIL PROTECTED]] Sent: zaterdag 10 januari 2004 12:29 To: [EMAIL PROTECTED] Subject: Re: Excel Generator I've used chaperon for csv transformations, but are a long way from something usable. - Hopefully chaperon's new version for csv tranformation on cocoon would be usable, and provide a base to work from. Geoff: I would be interested in what you have done thus far. I was also considering taking excell's xml output to convert it for use with forrest as a first cut (i.e. converting it to a doc v12 format), or alternatively strip all the stylesheet information but keep the table,cell,data definitions, and define an xsl tranformation which is a mix of doc v12 and the ms excell formats. Geoff Howard wrote: Yves Vindevogel wrote: And through XSP ? <xsp:logic> Code in Java to open the file with POI and generate xml?</xsp:logic> -----Original Message----- From: Joerg Heinicke [mailto:[EMAIL PROTECTED]] Sent: donderdag 8 januari 2004 21:40 To: [EMAIL PROTECTED] Subject: Re: Excel Generator On 08.01.2004 18:15, [EMAIL PROTECTED] wrote: Is it possible to use Excel files as input for a pipeline ? No, it isn't. I guess POI itself is able to do it, but it's not implemented in the Cocoon components. I've done something like this but in context just needed to put out a final document (not sax stream) and so used dom and did not implement it as a Generator. I almost went ahead and did a separate implementation for Cocoon but started feeling like the various ways one might want to interpret a series of excel spreadsheets as xml was too infinitely variable to warrant a quick solution of general use. Because my parsing requirements were complex, it would not be of general use even if I were free to release the code (which I'm not). Still, if you (or someone else) want to tackle it I could help. Geoff --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]