Re: POI3.14 Change to AddMergedRegion

And if you want the change history of
org.apache.poi.hssf.usermodel.HSSFSheet just check out the source and use
the svn commands to view file history.

On Sun, Oct 22, 2017 at 10:13 AM, Jack Woehr <
jwoehr@xxxxxxxxxxxxxxxxxxxxxxxx> wrote:

From the Javadocs:


- addMergedRegion

public int addMergedRegion(CellRangeAddress <https://poi.apache.org/apidocs/org/apache/poi/ss/util/CellRangeAddress.html> region)

Adds a merged region of cells on a sheet.
Specified by:addMergedRegion
<https://poi.apache.org/apidocs/org/apache/poi/ss/usermodel/Sheet.html#addMergedRegion-org.apache.poi.ss.util.CellRangeAddress-> in
interface Sheet
<https://poi.apache.org/apidocs/org/apache/poi/ss/usermodel/Sheet.html>
Parameters:region - to mergeReturns:index of this regionThrows:
java.lang.IllegalArgumentException - if region contains fewer than 2
cellsjava.lang.IllegalStateException - if region intersects with a
multi-cell array formulajava.lang.IllegalStateException - if region
intersects with an existing region on this sheet


On Sun, Oct 22, 2017 at 9:56 AM, Jack Woehr <jwoehr@absolute-performance.
com> wrote:

Read the source code?

On Sat, Oct 21, 2017 at 10:27 PM, Don Brown <DBrown@xxxxxxxxxx> wrote:

System is at V7R2 and running Java 7

I upgraded poi classes from 3.8 to 3.14 and most things worked fine.

We are generating some very large spreadsheets and the streaming function
available at this version is great!

A job crashed today with the java error ...

Message . . . . : Java exception received when calling Java method.
Cause . . . . . : RPG procedure SS_MERGE in program XAPSW/HSSFR4
received
Java exception "java.lang.IllegalArgumentException: Merged region C12
must
contain 2 or more cells" when calling method "addMergedRegion" with
signature "(Lorg.apache.poi.ss.util.CellRangeAddress;)I" in class
"org.apache.poi.ss.usermodel.Sheet". Recovery . . . : Contact the
person
responsible for program maintenance to determine the cause of the
problem.

So this is telling me there is a problem with the cell range for the
merge
function.

Digging further in the program dump I find that is actually the case and
the program is trying to merge a single cell.

Ok I can correct that with a check in the program but this code worked at
poi 3.8

So there must have been a change in the java class to error if the region
was for a single cell or with the reading I have been doing I think if
you
want to merge a single cell you have to specify the region differently.
(Why merge a single cell or what is the result of merging a single cell -
I have no idea)

How can I find the validation rules for the AddMergedRegion or when this
was changed - searching the poi site is not yielding the information I
was
hoping for - like a list of changes for each method by release.

Any suggestions welcomed.


Don Brown


--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/midrange-l.

Please contact support@xxxxxxxxxxxx for any subscription related
questions.

Help support midrange.com by shopping at amazon.com with our affiliate
link: http://amzn.to/2dEadiD

--
Absolute Performance, Inc.
12303 Airport Way, Suite 100
Broomfield, CO 80021

NON-DISCLOSURE NOTICE: This communication including any and all
attachments is for the intended recipient(s) only and may contain
confidential and privileged information. If you are not the intended
recipient of this communication, any disclosure, copying further
distribution or use of this communication is prohibited. If you received
this communication in error, please contact the sender and delete/destroy
all copies of this communication immediately.

--
Absolute Performance, Inc.
12303 Airport Way, Suite 100
Broomfield, CO 80021

NON-DISCLOSURE NOTICE: This communication including any and all
attachments is for the intended recipient(s) only and may contain
confidential and privileged information. If you are not the intended
recipient of this communication, any disclosure, copying further
distribution or use of this communication is prohibited. If you received
this communication in error, please contact the sender and delete/destroy
all copies of this communication immediately.