Scott wrote: > > Maybe we change the RPM to install sipxconfig.(jar/war) with a .new > > suffix, and then have the start-up script move the files when the > > process is re-started? > > No... that's not the issue. > > You need to look at how the refresh is being done on that > page. If the page is maintaining a connection to the server > and the server is periodically sending new content, then > doing the upgrade will break the refresh. If the refresh is > being done by a local script on the page periodically > checking for new content, it can be made to work. The > periodic check needs to be to some URL that does not require > any jetty context to fetch (a REST api, probably); something > that returns a value that will be updated after the reboot is > complete.
Ah, I see. The code is WaitingPage.html/.script at http://sipxecs.sipfoundry.org/rep/sipXecs/main/sipXconfig/web/context/WE B-INF/admin/ It is indeed a local script that uses the URL from which the restart was invoked. It isn't obvious to me though how it determines that the restart is complete. -Paul [email protected] _______________________________________________ sipx-dev mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-dev Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-dev sipXecs IP PBX -- http://www.sipfoundry.org/
