Forum Discussion
FlyBe_-_soapUI_
New Contributor
Hello
So we are 5 years later now and this is what you get from the current SoapUI (we are using v4.5.1)
From the following page, none of the methods to do with columns work correctly.
http://www.soapui.org/apidocs/pro/com/e ... Model.html
Try to remove the column. Nothing will happen visually and getColumnCount() will return the same value.
Try however to write to the last column index (getColumnCount()-1). This will return out of bounds exception .
Even worse situation is when you try to change column's order. You may end up values getting swapped between them. Although it may look ok on the screen, getColumnName(int column) it will give you false idea which column you are actually reading the values from.
When all of the sudden your project starts behaving crazy, I can only wish you success trying to debug that kind of thing with the groovy facilities provided within this proprietary application.
So we are 5 years later now and this is what you get from the current SoapUI (we are using v4.5.1)
From the following page, none of the methods to do with columns work correctly.
http://www.soapui.org/apidocs/pro/com/e ... Model.html
Try to remove the column. Nothing will happen visually and getColumnCount() will return the same value.
Try however to write to the last column index (getColumnCount()-1). This will return out of bounds exception .
Even worse situation is when you try to change column's order. You may end up values getting swapped between them. Although it may look ok on the screen, getColumnName(int column) it will give you false idea which column you are actually reading the values from.
When all of the sudden your project starts behaving crazy, I can only wish you success trying to debug that kind of thing with the groovy facilities provided within this proprietary application.
JKambli
9 years agoStaff
Ole commented in 2007 that it was fixed in snapshot, so it must have been fixed long back. The fix is never done to the main build, its either done in maintenance or future builds, the latest version of Ready API 1.6.0 SoapUI NG Pro, doesnt have this bug.
Thanks