Things were looking good until I expanded my test and found that there is a
64KB bytecode limit on methods. Rats.
From: darren@xxxxxxxxx
To: java400-l@xxxxxxxxxxxx,
Date: 09/28/2012 10:38 AM
Subject: Dynamic java for Excel spreadsheet
Sent by: java400-l-bounces@xxxxxxxxxxxx
We have run into various memory and performance issues using the JNI
interface from RPG to Java to generate spreadsheets using the POI HSSF
API's. Sometimes to get around this, we generate the spreadsheet in a .CSV
format, but this obviously generates a pretty ugly output when imported
into Excel. I'm currently researching generating the java code dynamically
in an RPG program, compiling it, and running that, meaning that the there
would be at least one java code source record for every cell on the
spreadsheet. I believe that the resulting program would perform much
better than the JNI interface does. Does anyone see any show stoppers with
this approach? Anyone tried something like this before?
--
This is the Java Programming on and around the IBM i (JAVA400-L) mailing
list
To post a message email: JAVA400-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit:
http://lists.midrange.com/mailman/listinfo/java400-l
or email: JAVA400-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at
http://archive.midrange.com/java400-l.
midrange.com
