Bug 1273330 - NPE dialog shown when generating additional properties file
Summary: NPE dialog shown when generating additional properties file
Keywords:
Status: CLOSED EOL
Alias: None
Product: JBoss BRMS Platform 6
Classification: Retired
Component: Installer
Version: 6.2.0
Hardware: Unspecified
OS: Unspecified
urgent
urgent
Target Milestone: ER5
: 6.2.0
Assignee: Miroslav Sochurek
QA Contact: Dominik Hanak
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-10-20 08:54 UTC by Dominik Hanak
Modified: 2020-03-27 20:03 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-03-27 20:03:04 UTC
Type: Bug
Embargoed:

Attachments (Terms of Use)

Description Dominik Hanak 2015-10-20 08:54:22 UTC 
Description of problem:
NPE error dialog risen when "Generate ... additional properties file" is pressed

Version-Release number of selected component (if applicable):
brms-6.2.0.ER4

How reproducible:
Install with Business Central datasource configuration and generate properties file

Steps to Reproduce:
1. Run installer
2. Perform Business Central DS configuration.
3. Finish installation
4. Click "Genererate installation script and addition..."

Actual results:
Error dialog is shown.

Expected results:
No error dialog is shown.

Additional info:
Properties file is created. I don't know from where did this NPE have emerged.
Comment 2 Dominik Hanak 2015-10-23 08:26:31 UTC 
Looks like there is a problem emerging from this.

The file generated by this, is totally empty, which means 
auto installation can't be performed. 

Therefore I am setting severity to urgent as this BZ prevents auto-installation.
Comment 3 Thomas Hauser 2015-10-27 14:43:08 UTC 
This error only occurs on the BRMS installer.
Comment 5 Thomas Hauser 2015-10-27 15:12:05 UTC 
Fixed for ER5 builds and beyond.
Comment 6 Dominik Hanak 2015-11-04 09:32:01 UTC 
Generated file after installation is not empty and the auto-installation performed by it finishes successfully.

Verified in 6.2.0.ER5.
Note You need to log in before you can comment on or make changes to this bug.