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
Attachments
Issue Links
- is related to
-
AXIS2-4611 JAX-WS services can no longer be deployed as AAR
- Resolved
-
AXIS2-4045 Ability to specify session scope in jaxws services
- Resolved