> > So the problem occurs when sipXconfig is updated while it is still > serving up the Installation page, which requires a Jetty context. > > How does the WaitingPage currently work without a Jetty context?
The WaitingPage does not need a Jetty context to run. Once the waiting page is displayed it calls (through Javascript/Ajax) a waitingListener method: afterRespondseSent that ultimately restarts the Jetty context. The Waiting Page checks (through Javascript/Ajax) the Jetty Context status. When Jettty is reachable means that restart was successful and it redirects to the login page. Take a look at WaitingPage.script that does the job Mircea > > -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/ > _______________________________________________ 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/
