We also use that. We also saved the old version of the HSSF prototypes,
and it used to be jshort, which is what some of our programs were compiled
with. I don't think I can tell which ones they were, so I'll either have
to guess by compile date, or just recompile all the 100+ programs.
From: "Mark Murphy/STAR BASE Consulting Inc."
<mmurphy@xxxxxxxxxxxxxxx>
To: Java Programming on and around the IBM i
<java400-l@xxxxxxxxxxxx>
Date: 03/22/2016 01:25 PM
Subject: Re: POI HSSF Windows Server X11 error resolved
Sent by: "JAVA400-L" <java400-l-bounces@xxxxxxxxxxxx>
Fortunately, for us anyway, the HSSF prototypes from Scott K already use
the setColumnWidth(jint, jint) method rather than the heretofore deprecated
setColumnWidth(jshort, jshort).
Mark Murphy
STAR BASE Consulting, Inc.
mmurphy@xxxxxxxxxxxxxxx
-----Darren Strong <darren@xxxxxxxxx> wrote: -----
To: Java Programming on and around the IBM i <java400-l@xxxxxxxxxxxx>
From: Darren Strong <darren@xxxxxxxxx>
Date: 03/22/2016 01:03PM
Subject: Re: POI HSSF Windows Server X11 error resolved
This upgrade has been a hoot. Turns out that POI dropped support for
setColumnWidth(jshort,jshort) at version 3.14. The preferred and only
method for this now is setColumnWidth(jint,jint). You've been warned.
From: Darren Strong <darren@xxxxxxxxx>
To: java400-l@xxxxxxxxxxxx
Date: 03/21/2016 12:59 PM
Subject: POI HSSF Windows Server X11 error resolved
Sent by: "JAVA400-L" <java400-l-bounces@xxxxxxxxxxxx>
We're currently running the Jakarta POI HSSF Excel generation java methods,
version 3.10.1. I attempted to replace this with the current version,
which is 3.14. Identical programs on different IBM i servers reacted
differently to this upgrade. Some worked as on the previous version, but
our production server blew up on an error about Windows Server X11 could
not be located. I found that some other install had created an environment
variable "DISPLAY" with an attribute of "localhost:10" on the production
server. Removing this environment variable let the new version (3.14) work
correctly. This DISPLAY variable has something to do with defining a
display device to Java, which I presume does not exist for an IBM i job
running in batch.
I'm posting this for someone else that may have experienced a similar
issue, so that it might help you.
--
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.
--
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.
--
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
