KAF-487:Added checks to handle null filings

[vaibhavcompanieshouse]

*This pr will add go like behavior where instead of null pointer go automatically overrides object to be empty the same will happen in Java resolves:KAF-487

Describe the changes

Related Jira tickets

Jira Ticket

Developer check list

General

• Is the PR as small as it can be?
• Has the Jira ticket been updated with any relevant comments?
• Is the README up to date?
• Has the POM been updated for the latest versions of dependencies?
• Has the code been double-checked against main?
• Does the code adhere standards in this repository, including SonarQube checks?

Testing

• Do the code changes have unit and integration tests with code coverage > 80%?
• Has the code been tested locally and/or passed the API Karate tests on docker-chs-development?
• Have mandatory manual test cases been run?
• Are extra Karate tests required?
• Are all the test data resources up to date?

Release preparation

Where possible, add links to the respective Jira tickets when an item is checked

• Have these changes been included in a release ticket?
• Are changes required to the docker-chs-development deployment or test data?
• Are any changes required to the environment added to chs-configs?

Notes to the tester

Add any testing hints or instructions here.

[Copilot]

Pull request overview

Adds defensive null-handling across the filing resource handling pipeline so that null filings, resources, transaction IDs, submission IDs, filing types/links, and individual FilingApi array entries no longer cause NullPointerExceptions. Expands unit test coverage in SubmissionIdServiceTest / FilingResourceProcessorServiceTest and adds a Kafka integration test for the filings == null path.

Changes:

• SubmissionIdService now guards against null/empty filings, null submission IDs, null transaction IDs, null filing types/links, and additionally catches StringIndexOutOfBoundsException when parsing offsets.
• FilingResourceProcessorService skips null entries within the FilingApi[] returned by the Filing API and logs an info message.
• ResourceMapFactory returns an empty map when transaction resources are null, and guards iteration against null resources.

Reviewed changes

Copilot reviewed 6 out of 6 changed files in this pull request and generated 4 comments.

Show a summary per file

File	Description
src/main/java/.../service/SubmissionIdService.java	Null-safe handling of transaction id, filings map, submission ids, filing type/links; broader exception catch.
src/main/java/.../service/FilingResourceProcessorService.java	Skips and logs null entries in the FilingApi[] response.
src/main/java/.../factory/ResourceMapFactory.java	Returns empty map when resources are null; guards iteration in populateResourceMap.
src/test/java/.../service/SubmissionIdServiceTest.java	New tests for null/empty filings, null submission/transaction ids, SIOOBE path, null type/links/resource.
src/test/java/.../service/FilingResourceProcessorServiceTest.java	New test for null entry inside FilingApi[].
src/test/java/.../kafka/ConsumerIT.java	Integration test verifying successful processing when transaction.filings is null.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[chsonarqubeprchecks]

Quality Gate passed

Issues
0 New issues
0 Fixed issues
0 Accepted issues

Measures
0 Security Hotspots
95.8% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube