The warnings were caused by duplication definition of the PICTURE_TYPE_*
constants. The problem should be fixed in r958563. Please try the latest
build from trunk. Daily builds can be downloaded from
http://encore.torchbox.com/poi-svn-build/
Initially these constants were defined in HSSFWorkbook. In POI-3.5 we
introduced support for OOXML files and defined a common interface
org.apache.poi.ss.usermodel.Workbook and two implementing classes:
HSSFWorkbook and XSSFWorkbook. The PICTURE_TYPE_* constants were copied
to the Workbook interface but never removed from HSSFWorkbook.
We are certainly interested in your benchmarks of Java Excel APIs.
Please send a link to your research when it is ready.
Yegor
Hi!
I've been using POI 3.6 with Ruby with great results so far (except for a
little border problem in merge cells but I'm working on it).
In fact I'm doring a little bechmark on POI, JExcel API and Aspose.Cells
using Java, Ruby and RJS (which is a great Java bridge for Ruby). If you're
interrested in it, the result will be published later on the blog of my
company.
The question I wanted to ask if maybe others have tried to run POI with Ruby
is if anyone has ever seen this warning:
"warning: already initialized constant PICTURE_TYPE_EMF"
It does not hurt it's just a warning caused by the inclusion of POI's Java
packages. And it is displayed 6 times (also
for PICTURE_TYPE_WMF, PICTURE_TYPE_PICT, PICTURE_TYPE_JPEG,
PICTURE_TYPE_PNG, PICTURE_TYPE_DIB).
Thank you
Michel
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
