[
https://issues.apache.org/jira/browse/FELIX-1003?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12689921#action_12689921
]
Filippo Diotalevi commented on FELIX-1003:
------------------------------------------
It seems to be a "natural" problem.
When an updated configuration is saved, the method
OsgiManager.updateConfiguration(..) is called.
At OsgiManager, line 765 the servlet is unregistered and it's registered with a
new configuration shortly after. That's correct and I don't see how it could be
improved (I tried to move unbind and binding "closer", but with no luck... I
guess the re-registration takes some millisec to be effective).
Since the redirect happens while the new servlet registration is not effective
yet, the 404 error is returned.
The only workaround I could find is to place a Thread.sleep(200l) (conditioned
to the fact that the Console configurations are changed) just before the
this.sendRedirect(request, response, redirect);
at ConfigManager, line 115
Ugly hack. Can anybody suggest a better solution?
> Saving Apache Felix OSGI Management Console on Safari cause Error 404
> ---------------------------------------------------------------------
>
> Key: FELIX-1003
> URL: https://issues.apache.org/jira/browse/FELIX-1003
> Project: Felix
> Issue Type: Bug
> Components: Web Console
> Affects Versions: webconsole-1.2.2, webconsole-1.2.8
> Environment: Safari 3.2.1, Mac Os X 10.5.6
> Reporter: Filippo Diotalevi
> Priority: Minor
>
> 1- Click on Configuration Tab
> 2- Choose Configurations: Apache Felix OSGI Management Console (...
> OsgiManager)
> 3- Click on Configure
> 4- Click on Save
> I get:
> HTTP ERROR: 404
> NOT_FOUND
> RequestURI=/system/console/configMgr/org.apache.felix.webconsole.internal.servlet.OsgiManager
> On Firefox the same functionality works well.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
