[
https://issues.apache.org/jira/browse/AXIS2-5322?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sagara Gunathunga updated AXIS2-5322:
--------------------------------------
Description:
Refer the following discussion[1] to find objectives of this idea.
ServiceBuilderExtension can take following API.
public interface ServiceBuilderExtension {
public void init( ConfigurationContext configurationContext);
public Map<String,AxisService> buildAxisServices(DeploymentFileData
deploymentFileData) throws DeploymentException;;
}
and possible to register them with deployers as follows.
<deployer extension="" directory="" class="">
<serviceBuilderExtension name ="jwsbuilderExt"
class="org.apache.axis2.jaxws.framework.JAXWSServiceBuilderExtension">
</deployer>
* One deployer can have number of ServiceBuilderExtensions and will invoke them
in the order they defined in the axis2.xml file.
* For a given deploymentFile, if all ServiceBuilderExtensions fail to create
AxisService then base deployer will take care about the deployment of that
particular deploymentFile.
* For a given deploymentFile, if a ServiceBuilderExtension could create a
AxisService then stop execution of other ServiceBuilderExtensions registered
and return the AxisService immediately to the base deployer for the further
processing.
* Axis2 AbstractDeployer implement necessary helping methods for this idea so
that extended Deployer from AbstractDeployer can easily utilise
ServiceBuilderExtension concept.
* Immediate goal is to support JAX-WS artefacts through ServiceDeployer .
[1] - http://axis.markmail.org/thread/kvhvcvfufpo6zfe3
[2] -
http://axis.apache.org/axis2/java/core/api/org/apache/axis2/deployment/AbstractDeployer.html
was:
Refer the following discussion[1] to find objectives of this idea.
ServiceBuilderExtension can take following API.
public interface ServiceBuilderExtension {
public void init( ConfigurationContext configurationContext, String directory);
public Map<String,AxisService> buildAxisServices(DeploymentFileData
deploymentFileData) throws DeploymentException;;
}
and possible to register them with deployers as follows.
<deployer extension="" directory="" class="">
<serviceBuilderExtension name ="jwsbuilderExt"
class="org.apache.axis2.jaxws.framework.JAXWSServiceBuilderExtension">
</deployer>
* One deployer can have number of ServiceBuilderExtensions and will invoke them
in the order they defined in the axis2.xml file.
* For a given deploymentFile, if all ServiceBuilderExtensions fail to create
AxisService then base deployer will take care about the deployment of that
particular deploymentFile.
* For a given deploymentFile, if a ServiceBuilderExtension could create a
AxisService then stop execution of other ServiceBuilderExtensions registered
and return the AxisService immediately to the base deployer for the further
processing.
* Axis2 AbstractDeployer implement necessary helping methods for this idea so
that extended Deployer from AbstractDeployer can easily utilise
ServiceBuilderExtension concept.
* Immediate goal is to support JAX-WS artefacts through ServiceDeployer .
[1] - http://axis.markmail.org/thread/kvhvcvfufpo6zfe3
[2] -
http://axis.apache.org/axis2/java/core/api/org/apache/axis2/deployment/AbstractDeployer.html
> ServiceBuilderExtension for Axis2 Deployers
> -------------------------------------------
>
> Key: AXIS2-5322
> URL: https://issues.apache.org/jira/browse/AXIS2-5322
> Project: Axis2
> Issue Type: New Feature
> Components: kernel
> Reporter: Sagara Gunathunga
> Assignee: Sagara Gunathunga
> Fix For: 1.7.0
>
>
> Refer the following discussion[1] to find objectives of this idea.
> ServiceBuilderExtension can take following API.
> public interface ServiceBuilderExtension {
> public void init( ConfigurationContext configurationContext);
> public Map<String,AxisService> buildAxisServices(DeploymentFileData
> deploymentFileData) throws DeploymentException;;
> }
> and possible to register them with deployers as follows.
> <deployer extension="" directory="" class="">
> <serviceBuilderExtension name ="jwsbuilderExt"
> class="org.apache.axis2.jaxws.framework.JAXWSServiceBuilderExtension">
> </deployer>
> * One deployer can have number of ServiceBuilderExtensions and will invoke
> them in the order they defined in the axis2.xml file.
> * For a given deploymentFile, if all ServiceBuilderExtensions fail to create
> AxisService then base deployer will take care about the deployment of that
> particular deploymentFile.
> * For a given deploymentFile, if a ServiceBuilderExtension could create a
> AxisService then stop execution of other ServiceBuilderExtensions registered
> and return the AxisService immediately to the base deployer for the further
> processing.
> * Axis2 AbstractDeployer implement necessary helping methods for this idea so
> that extended Deployer from AbstractDeployer can easily utilise
> ServiceBuilderExtension concept.
> * Immediate goal is to support JAX-WS artefacts through ServiceDeployer .
> [1] - http://axis.markmail.org/thread/kvhvcvfufpo6zfe3
> [2] -
> http://axis.apache.org/axis2/java/core/api/org/apache/axis2/deployment/AbstractDeployer.html
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
