Open GoogleCodeExporter opened 9 years ago
I am not familiar with XSSF. You should take a look at the ExcelView and
JExcelView and find out if there is anything that we could change to get past
the maximum number of lines.
If you had to you could limit the number of lines that are exported or create
another excel view that put data in multiple worksheets.
Original comment by jeff.johnston.mn@gmail.com
on 27 Sep 2011 at 12:19
Hi Mr Johnston,
I checked the implementation of the class ExcelView, and I changed the render
method to use XSSF, but the problem now is that when the export is call,
the jmesa implementation invoke the method exports of the class
ExcelViewExporter that, explicitly, use the class HSSFWorkbook, when it
should use the interface Workbook.
How can I solve the problem by calling my custom exports method ?
Original comment by pusa...@gmail.com
on 15 Nov 2011 at 4:36
>>How can I solve the problem by calling my custom exports method ?
Not at the moment. Its unfortunate as it is pretty much the only thing in JMesa
that is not easily exposed. But it is still possible...here is a link to a
thread that is a similar flavor of this problem.
http://groups.google.com/group/jmesa_forum/browse_thread/thread/860aa8cf8049e5ac
In a nutshell you could change the code to use the interface, or get a patch
into JMesa to make the feature plugable, or follow the thread (above) and do
that.
If you wanted I could recompile the code with the interface change and I could
send you a custom jar file too...just send me an email at
jeff.johnston.mn@gmail.com.
As that thread talks about at the beginning of next year I am going to get some
time to improve this too.
Original comment by jeff.johnston.mn@gmail.com
on 15 Nov 2011 at 9:18
Original issue reported on code.google.com by
pusa...@gmail.com
on 26 Sep 2011 at 11:06