Created attachment 526236 [details] Class to reproduce bug Description of problem: Empty column header in decision table throws NPE. Happens both with conditions and actions. Happens both with XLS and CSV. Error can be seen in attached example. The example contains error, but parser should not fail with NPE, but should respond with appropriate error message understandable by user. Version-Release number of selected component (if applicable): BRMS 5.2.0 ER5 How reproducible: Run attached test case. Steps to Reproduce: 1. Unzip test case. 2. Run as Java app. Actual results: XLS and CSV parsers throws NPE in described situation. Expected results: XLS and CSV should always respond with appropriate error message.
I have added a pull request with test case: https://github.com/droolsjbpm/drools/pull/86
Fixed as requested: "respond with appropriate error message". I've also looked extensively it is possible to support such an empty column header as that looks to be a valid use case, but the code design doesn't allow it easily.
https://github.com/droolsjbpm/drools/compare/8aa9caa...7cd7730
Please verify the issue on 5.3 ER4.
Verified in 5.3 ER4.
Technical note added. If any revisions are required, please edit the "Technical Notes" field accordingly. All revisions will be proofread by the Engineering Content Services team. New Contents: Previously including an empty column header in a Decision Table resulted in a NullPointerException being thrown. The issue has been resolved by including an error message that warns the user not to leave the column header blank.