[ARCHETYPE-585] Missing null check causes NullPointerException

• Type: Bug
• Status: Closed
• Priority: Minor
• Resolution: Fixed
• Affects Version/s: 3.1.2
• Fix Version/s: 3.2.0
• Component/s: Archetypes
• Assignee: Sylwester Lachiewicz
• Reporter: Tony Homer
• Created: 02/Jan/20 21:37
• Updated: 13/Jul/20 20:18
• Resolved: 13/Jul/20 20:18

Description

RemoteCatalogArchetypeDataSource.getArchetypeCatalog calls RemoteCatalogArchetypeDataSource.getMirror.
RemoteCatalogArchetypeDataSource.getMirror calls legacySupport.getSession, then invokes getRequest on the returned value with no null check.
When the legacySupport session is null, this results in a NullPointerException.

The fix is to add a null check before calling session.getRequest.

Issue Links

• links to: GitHub Pull Request #34