Forum Discussion
I downloaded the ooxml-schemas-1.3.jar file and placed it into bin/ext along with all the other poi jars.
But I still have the same problem : CTExtensionList error
I meet the same problem. When I use " def wb= new XSSFWorkbook(file)", the error prompt which is the same as above pops up. When I use " def wb= WorkbookFactory.reate(file);", there is no response. I mean there is no error popping up or log printing. In fact, the same script runs properly in my groovy IDE. I am not sure if the soapui 5.4 can not use the poi 4.0.
- Camerlock6 years agoNew Contributor
My aim is to read and write and xlsx file from Groovy Test Step.
For xls files everything worked fine.
Trying upgrading to poi vers. > 3.12 is not that helpful because on ReadyAPI or SOAPUI Pro version this will break Test Step Datasource with Excel for loading data. The Test Step is then failed.
I then rolback and have to face the multiple issues described here. I was unsuccessful everytime.
After trying all available API in POI and also trying using the additional OOXML Schemas lib I must admitted too: Handling / updating xlsx files in Groovy step is not currently possible.
ERROR: An error occurred [org/openxmlformats/schemas/spreadsheetml/x2006/main/CTExtensionList], see error log for details
- mityfai5 years agoMember
I've been struggling with this issue for a while and trying it again with every new Release and hoping it's been solved. By the current release, unfortunately not!
Anonymous: Ist there any hope that this well known issue will be solved:
can ReadyAPI be inproved to handle xlsx file in groovy script or should will exclude that combination from test cases implementation at all.
- Nastya_Khovrina5 years agoSmartBear Alumni (Retired)
Please try the solution from this article:
- bompeacock5 years agoNew Contributor
I am also stuck with this issue, any pro or Nastya_Khovrina have any ideas, please tell me,
But my solution is changing .xlsx to xls, it does work. But I want to use .xlsx instead of .xls file. - Nastya_Khovrina5 years agoSmartBear Alumni (Retired)
Hi bompeacock.,
Do you use a script from this KB article: https://smartbear-cc.force.com/portal/KbArticleViewer?name=Example-of-using-third-party-Java-libraries-in-Groovy-script-reading-from-Excel-file-using-Apache-POI&sp=all?
It's working fine for me with .xslx file with ReadyAPI 2.8.0 and Apache POI 4.1.0.
What versions do you use?
Do you have the exact same error in the log as the error from the first post?
- ayonchoudhury5 years agoNew Contributor
Apart from the poi jars, download the jar
ooxml-schemas-1.3.jar
Place this jar in your SmartBear\SoapUI-5.4.0\bin\ext
and restart SOAP UI. Should work now!!
You can find more on my blog - https://testbuster309148348.wordpress.com/blog/
Let me know if this helps
- bompeacock5 years agoNew Contributor
Hi Nastya_Khovrina ,
I tried, and 4.0.1 throw an another Exception and all DataSource steps (using excel file) were broken with the same error message as below:It still only works for .xls.
Why don't Ready API 2.8.0 Pro install lib POI 4.0.1 or working exactly version already instead of 3.12 that somtime not working with .xlsx? Because when I release script Ready API for my customer I can not decide to choose which version for POI lib.
- JustinM895 years agoContributor
Just a heads up, in %READYAPI_HOME%/lib, there is poi-ooxml-schemas-3.12.jar -- if you are adding a different version to bin/ext, both of these JARs are probably getting added to the classpath and could cause issues.
I ran into this same issue with bouncy-castle (specifically bcprov-jdk) -- we needed this dependency to encrypt passwords, so we added it into bin/ext, but we kept getting this strange Arrays.concatenate([B][B][B]) error. After some poking around we realized that there was another version of this same JAR in lib/ and it seemed that when we were calling our encrypt method, it was using the method from this JAR, and not the one we had placed in bin/ext.
We simply replaced the version of bouncy-castle in the lib directory with the same version we had in bin/ext and this resolved the issue -- however, I'm pretty sure doing this has the potential to break something in SoapUI if it is relying on a class from a specific version of a JAR and you go and swap it out with a different version, so do this at your own risk.
- Nastya_Khovrina5 years agoSmartBear Alumni (Retired)
Please try the solutions from here:
But, Justin is right, using libraries versions which differ from versions in ReadyAPI installation may cause issues.
- bompeacock5 years agoNew Contributor
Your answer is not resolving my issue. Thank, maybe I should still use POI ver 3.12 and .xls files.