You are viewing a plain text version of this content. The canonical link for it is here.
Posted to java-dev@axis.apache.org by "nadir amra (JIRA)" <ji...@apache.org> on 2007/04/11 07:09:32 UTC
[jira] Created: (AXIS2-2504) Have indication of active/inactive
service in services.xml
Have indication of active/inactive service in services.xml
----------------------------------------------------------
Key: AXIS2-2504
URL: https://issues.apache.org/jira/browse/AXIS2-2504
Project: Axis 2.0 (Axis2)
Issue Type: Improvement
Components: deployment
Affects Versions: 1.1.1
Reporter: nadir amra
Assigned To: nadir amra
The idea is to add an "activate" attribute in services.xml to the "service" element that indicates whether the service should be activated or not - i.e. a persistent property that will allow the AXIS2 engine to determine whether the service should be activated on startup. In addition, if management APIs come to fruition that updates the services.xml file so that the state is changed from active to inactive and vice-versa, the AXIS2 engine can pick this up and activate/deactivate the service. Again, in a persistent way.
The code needed to do this affects two Java files:
DeploymentConstants.java -- simply to add attribute name "activate" and possible values for "true" and "false"
ServiceBuilder.java -- a few lines to get the attribute and set the active flag via AxisService::setActive() for the service depending on the "state" attribute.
An example of what the service element would look like:
<service name="StockQuoteService" activate="true" scope="application" targetNamespace="http://quickstart.samples/">
Before I make the changes and test it out, wondering if there are anything I am overlooking?
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org
[jira] Commented: (AXIS2-2504) Have indication of active/inactive
service in services.xml
Posted by "nadir amra (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AXIS2-2504?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12489296 ]
nadir amra commented on AXIS2-2504:
-----------------------------------
I added code in ServiceBuilder::populateService() to check for the attribute and set the active flag via AxisService::setActive().
Things look good. If the activate attribute is "false", the service is not activated on AXIS2 startup. However, when I try to active the service from the AXIS2 admin page, the service goes to activate and then back to deactivate state. From what I can tell, this has to do with the fact that the periodic loading of the service results in the service being deactivated because of the activate="false" attribute that is in the service.xml.
So I am wondering how I can rectify this? Even without my changes, I am wondering how does AXIS2 know when a service is active/inactive? A pointer where I can look would be helpful.
> Have indication of active/inactive service in services.xml
> ----------------------------------------------------------
>
> Key: AXIS2-2504
> URL: https://issues.apache.org/jira/browse/AXIS2-2504
> Project: Axis 2.0 (Axis2)
> Issue Type: Improvement
> Components: deployment
> Affects Versions: 1.1.1
> Reporter: nadir amra
> Assigned To: nadir amra
>
> The idea is to add an "activate" attribute in services.xml to the "service" element that indicates whether the service should be activated or not - i.e. a persistent property that will allow the AXIS2 engine to determine whether the service should be activated on startup. In addition, if management APIs come to fruition that updates the services.xml file so that the state is changed from active to inactive and vice-versa, the AXIS2 engine can pick this up and activate/deactivate the service. Again, in a persistent way.
> The code needed to do this affects two Java files:
> DeploymentConstants.java -- simply to add attribute name "activate" and possible values for "true" and "false"
> ServiceBuilder.java -- a few lines to get the attribute and set the active flag via AxisService::setActive() for the service depending on the "state" attribute.
> An example of what the service element would look like:
> <service name="StockQuoteService" activate="true" scope="application" targetNamespace="http://quickstart.samples/">
> Before I make the changes and test it out, wondering if there are anything I am overlooking?
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org
[jira] Resolved: (AXIS2-2504) Have indication of active/inactive
service in services.xml
Posted by "nadir amra (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AXIS2-2504?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
nadir amra resolved AXIS2-2504.
-------------------------------
Resolution: Fixed
Fix Version/s: nightly
1.2
Marking this as resolved. I also copied the changes into 1.2 release. I think it is critical that there is a persistent way to ensure a deployed service is not activated during startup if it is so desired.
> Have indication of active/inactive service in services.xml
> ----------------------------------------------------------
>
> Key: AXIS2-2504
> URL: https://issues.apache.org/jira/browse/AXIS2-2504
> Project: Axis 2.0 (Axis2)
> Issue Type: Improvement
> Components: deployment
> Affects Versions: 1.1.1
> Reporter: nadir amra
> Assigned To: nadir amra
> Fix For: 1.2, nightly
>
>
> The idea is to add an "activate" attribute in services.xml to the "service" element that indicates whether the service should be activated or not - i.e. a persistent property that will allow the AXIS2 engine to determine whether the service should be activated on startup. In addition, if management APIs come to fruition that updates the services.xml file so that the state is changed from active to inactive and vice-versa, the AXIS2 engine can pick this up and activate/deactivate the service. Again, in a persistent way.
> The code needed to do this affects two Java files:
> DeploymentConstants.java -- simply to add attribute name "activate" and possible values for "true" and "false"
> ServiceBuilder.java -- a few lines to get the attribute and set the active flag via AxisService::setActive() for the service depending on the "state" attribute.
> An example of what the service element would look like:
> <service name="StockQuoteService" activate="true" scope="application" targetNamespace="http://quickstart.samples/">
> Before I make the changes and test it out, wondering if there are anything I am overlooking?
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org
[jira] Commented: (AXIS2-2504) Have indication of active/inactive
service in services.xml
Posted by "nadir amra (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AXIS2-2504?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12487989 ]
nadir amra commented on AXIS2-2504:
-----------------------------------
Forgot to add that if the attribute is missing, the default would be to activate the service.
> Have indication of active/inactive service in services.xml
> ----------------------------------------------------------
>
> Key: AXIS2-2504
> URL: https://issues.apache.org/jira/browse/AXIS2-2504
> Project: Axis 2.0 (Axis2)
> Issue Type: Improvement
> Components: deployment
> Affects Versions: 1.1.1
> Reporter: nadir amra
> Assigned To: nadir amra
>
> The idea is to add an "activate" attribute in services.xml to the "service" element that indicates whether the service should be activated or not - i.e. a persistent property that will allow the AXIS2 engine to determine whether the service should be activated on startup. In addition, if management APIs come to fruition that updates the services.xml file so that the state is changed from active to inactive and vice-versa, the AXIS2 engine can pick this up and activate/deactivate the service. Again, in a persistent way.
> The code needed to do this affects two Java files:
> DeploymentConstants.java -- simply to add attribute name "activate" and possible values for "true" and "false"
> ServiceBuilder.java -- a few lines to get the attribute and set the active flag via AxisService::setActive() for the service depending on the "state" attribute.
> An example of what the service element would look like:
> <service name="StockQuoteService" activate="true" scope="application" targetNamespace="http://quickstart.samples/">
> Before I make the changes and test it out, wondering if there are anything I am overlooking?
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org
[jira] Commented: (AXIS2-2504) Have indication of active/inactive
service in services.xml
Posted by "nadir amra (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AXIS2-2504?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12490670 ]
nadir amra commented on AXIS2-2504:
-----------------------------------
I also want to update the services.xsd file so that this entry is added:
<xs:attribute name="activate" type="xs:boolean" use="optional"/>
However, I am unsure where to update the file. I have updated it in the 1.2 branch:
xdocs/@axis2_version_dir@/resources/schemas/services.xsd
But I am unsure if I need to update something in the trunk. Please let me know if I do and which directory.
> Have indication of active/inactive service in services.xml
> ----------------------------------------------------------
>
> Key: AXIS2-2504
> URL: https://issues.apache.org/jira/browse/AXIS2-2504
> Project: Axis 2.0 (Axis2)
> Issue Type: Improvement
> Components: deployment
> Affects Versions: 1.1.1
> Reporter: nadir amra
> Assigned To: nadir amra
> Fix For: 1.2, nightly
>
>
> The idea is to add an "activate" attribute in services.xml to the "service" element that indicates whether the service should be activated or not - i.e. a persistent property that will allow the AXIS2 engine to determine whether the service should be activated on startup. In addition, if management APIs come to fruition that updates the services.xml file so that the state is changed from active to inactive and vice-versa, the AXIS2 engine can pick this up and activate/deactivate the service. Again, in a persistent way.
> The code needed to do this affects two Java files:
> DeploymentConstants.java -- simply to add attribute name "activate" and possible values for "true" and "false"
> ServiceBuilder.java -- a few lines to get the attribute and set the active flag via AxisService::setActive() for the service depending on the "state" attribute.
> An example of what the service element would look like:
> <service name="StockQuoteService" activate="true" scope="application" targetNamespace="http://quickstart.samples/">
> Before I make the changes and test it out, wondering if there are anything I am overlooking?
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org