ws-soap-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Chris Francis <>
Subject RE: Reloading services.
Date Mon, 06 Nov 2000 11:20:07 GMT

Yes, but there aren't many choices available. We can't have a service
doing it because we can't get hold of the servlet context. We could use the
post method
quite easily, and maybe assume a non-soap post or error results in services
reloaded. Or something. Lot's of things possible. I just chose the easiest


-----Original Message-----
From: Steve Graham/Raleigh/IBM []
Sent: 03 November 2000 14:37
Subject: Re: Reloading services.

I agree this is possible, however it strikes me that a get on the RPCRouter
resulting in reloading of services is an unexpected semantic.

Steve Graham
(919)254-0615 (T/L 444)
<<Pithecanthropus Erectus>>
Emerging Internet Technologies

Chris Francis <> on 11/03/2000 09:14:46 AM

Please respond to

To:   "''" <>
Subject:  Reloading services.

Can we use the doGet () method of RPCRouterServlet to enable live reloading
services. Currently we have to shutdown and restart the servlet engine or
the servlet to reload somehow.
Is there a problem with this?

public void doGet (HttpServletRequest req, HttpServletResponse res) throws
ServletException, IOException {
    ServletConfig config = getServletConfig ();
    ServletContext context = config.getServletContext ();
    synchronized (context) {
      RPCRouter rpcRouter = new RPCRouter ();
      ServiceManager serviceManager = new ServiceManager ();
      context.setAttribute (RPC_ROUTER_ID, rpcRouter);
      context.setAttribute (SERVICE_MANAGER_ID, serviceManager);

Chris Francis,
Software Engineer,
Static 2358, Ltd.
+44 (0) 20 7250 1244

View raw message