[email protected] wrote: > On Mon, 27 Apr 2009, [email protected] wrote: > > Will POI 3.5 final API be compatible with current POI 3.2? > > The aim is for it to be source compatible, but not always binary > compatible. > > (See http://poi.apache.org/spreadsheet/converting.html for how to convert > existing hssf code into the generic ss code, but if you just want to stick > with hssf, all you should need to do is recompile your application)
Does that mean that jar files like JasperReports will have to provide a 3.5 compatible jar and a 3.2 compatible jar? Why not having a transition period having both APIs? Who decided to deprecate the current API and go for a new one just in one release? I understand that Microsoft want to undermine every Java software and to implement their badly designed file formats, but there are other office packages like OpenOffice that can read XLS and do not need the pointless OOXML. Will Microsoft also implement OpenDocument Spreadsheet? Should we force OpenDocument to be implemented to allow Microsoft include their pointless and badly designed OOXML? Ahora también puedes acceder a tu correo Terra desde el móvil. Infórmate pinchando aquí.
