axis-java-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From j...@apache.org
Subject [jira] Commented: (AXIS-1389) Ability to Suspend and Resume Specific Services
Date Mon, 14 Jun 2004 10:41:13 GMT
The following comment has been added to this issue:

     Author: Davanum Srinivas
    Created: Mon, 14 Jun 2004 3:40 AM
       Body:
- enable adminservlet in your web.xml. 
- add an init-param to your adminservlet named axis.development.system and set it to true
- start tomcat and browse to http://localhost:8080/axis/servlet/AdminServlet

-- dims
---------------------------------------------------------------------
View this comment:
  http://issues.apache.org/jira/browse/AXIS-1389?page=comments#action_36138

---------------------------------------------------------------------
View the issue:
  http://issues.apache.org/jira/browse/AXIS-1389

Here is an overview of the issue:
---------------------------------------------------------------------
        Key: AXIS-1389
    Summary: Ability to Suspend and Resume Specific Services
       Type: New Feature

     Status: Closed
   Priority: Major
 Resolution: FIXED

    Project: Axis
 Components: 
             Deployment / Registries
   Fix Fors:
             current (nightly)
   Versions:
             1.1

   Assignee: Davanum Srinivas
   Reporter: Brian Dillon

    Created: Fri, 11 Jun 2004 9:14 AM
    Updated: Mon, 14 Jun 2004 3:40 AM

Description:
Hi,

If a Service is deployed on Axis there currently seems to be no way of suspending and resuming
the service (without undeploying and redeploying).

I understand from looking through the API that there are calls;

 handlers.soap.SOAPService.enableTransport(HTTP)
 handlers.soap.SOAPService.disableTransport(HTTP)
 
So my issue is how to get a reference to this SOAPService handler since we don't have direct
access to the running AxisServer ? There seems to be now way to get access to either the AxisServer
or the SOAPService handler from outside of Axis.

The reason for not going down the route of deploy and undeploy is because of the need for
wsdd files. If the ability to suspend and resume the service was allowed then we could present
a JMX interface to list and control (stop/suspend and restart/resume) the services as required.

Thanks,

Brian Dillon


---------------------------------------------------------------------
JIRA INFORMATION:
This message is automatically generated by JIRA.

If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa

If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira


Mime
View raw message