Erraticity in state of applicationConfig

Sulka made the following observation:

"During the 60+ minute import my browser timed out. When I tried to load a page from Confluence during this time I get a System Error: com.opensymphony.xwork.config.ConfigurationException: There is no Action mapped for namespace /setup and action name complete. The error didn't go away until I restarted Confluence after it had seemed to finish the importing - I have no way of knowing since the import/setup process doesn't issue a "import complete" type messages into the log."

It's a potential flaw in the design of the setupwizard (both versions) that we write <setupStep>complete</setupStep> in a field which is otherwised associated with xwork configured actions, but it is a side effect of a check on bootstrapManager.isSetupComplete() returning a false, after setupPersister.finishSetup() has been called; the latter sets the setupComplete flag on applicationConfig, the former reads it.

So either the wrong value is being set or the wrong value is being read.

Confirm and fix for 1.3.1 .

It's worthwhile to remember that this bug is being reported after a 60 minute setup procedure ...