-
Notifications
You must be signed in to change notification settings - Fork 344
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Blank cells throwing null pointer exception while reading #33
Comments
I had a similar issue, I solved it like this:
this just creates a StreamingCell with null value and you can go from there. edit// formatting (indentation does not seem to work here) |
@andreasellervee thank you so much for your post. It helped me a lot. I was at the same issue and I could fix it by using your solution. Just to exempify, I was considering the code below:
than I've changed to this, in order to work well:
|
Hello abhilashreddy1289 Cell cell = row.getCell(i, Row.CREATE_NULL_AS_BLANK) is now supported and resolves the issue. Hope this is good news. |
Row.CREATE_NULL_AS_BLANK not working |
Can you confirm that you are using the latest maven version 1.1.0. If you are please provide the sheet and code. Then we can help you. |
Any thoughts on implementing
on |
Hello @dlandis I haven't really looked into the code too much. Committed the change to fix a bug I had encountered in a personal project. Have a crack at it. |
I am using this api and rows contains blank cells causing null pointer issue. Below is the stack trace.
com.monitorjbl.xlsx.exceptions.NotSupportedException
java.lang.NullPointerException
at test.XLSXToCSVConverterStreamer.xlsx(XLSXToCSVConverterStreamer.java:67)
at test.XLSXToCSVConverterStreamer.main(XLSXToCSVConverterStreamer.java:164)
if I use Cell cell = row.getCell(i, Row.CREATE_NULL_AS_BLANK) to read empty cells as blank I am getting below issue. Kindly help me in resolving this
com.monitorjbl.xlsx.exceptions.NotSupportedException
at com.monitorjbl.xlsx.impl.StreamingRow.getCell(StreamingRow.java:108)
The text was updated successfully, but these errors were encountered: