Opened 10 years ago
Closed 10 years ago
#1823 closed defect (fixed)
Extensions overview display incorrect error message
Reported by: | Nicklas Nordborg | Owned by: | everyone |
---|---|---|---|
Priority: | minor | Milestone: | BASE 3.3 |
Component: | core | Version: | |
Keywords: | Cc: |
Description
In the picture the yubikey.jar icon is clearly marked with an error icon. The details also has a red error section, but the message is not the error message, but parts of what would have been displayed after a successful installation.
Attachments (1)
Change History (5)
by , 10 years ago
Attachment: | successful-error.png added |
---|
comment:1 by , 10 years ago
comment:2 by , 10 years ago
Using the "Install/uninstall" wizard and forcing a re-install of YubiKey reveals the actual error in the GUI:
Failed to load extension(s): Can't find the configuration file. Make sure '/yubikey.properties' is in the CLASSPATH.
I think the problem is related to #1777, but in this case, the first scan is done when BASE is starting up (from the Application.start()
method) and later in the startup sequence, a second scan is made from ExtensionsControl.init()
. There error is encountered in the first scan and forgotten in the second. The reason for this is a bit unclear...
comment:3 by , 10 years ago
(In [6501]) References #1823: Extensions overview display incorrect error message
This was caused by multiple "cooperating" issues.
- The yubikey package contain extensions both to the web interface and to the core, thus it is loaded in two different parts of the application.
- The error messsage in the initial scan from
Application.start()
was never saved. - When
ExtensionsControl
continue to load the gui extensions it will continue with gui-related installation and this is successful and stored, but the error flag is never reset.
The fix is to save core statup results in ExtensionsManager
, and use those results also in the second scan (gui startup from ExtensionsControl
). The second scan should not continue if there is an error from the first scan (fixed in InstalledFilter
). Then, when forcing a manual re-installation the old error must be cleared (fixed in ResetErrorFlagProcessor
).
comment:4 by , 10 years ago
Resolution: | → fixed |
---|---|
Status: | new → closed |
From Tomcat's log file: