[
https://issues.apache.org/jira/browse/AXIS2-5340?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sagara Gunathunga updated AXIS2-5340:
--------------------------------------
Description:
Axis2 ServiceDeployer implements Deployer interface like any other Axis2
deployers but it does not use axis2.xml file instead ServiceDeployer is hard
coded in DeploymentEngine. This approach having some limitations.
1.) It is not possible to disable ServiceDeployer if a user only wants to use
any other deployer. ( e.g - only JAX-WS deployer) but other deployers grant
such features.
2.) It is not possible to use newly introduced custom ServiceBuilderExtension
feature with ServiceDeployer.
3.) Standard axis2.xml based <deployer> element use "extension" and
"directory" attributes to define deployment unit type ( file extension) and
container directory. But ServiceDeployer only work with AAR or exploded AAR
archives also use "ServicesDirectory" parameter to specify directory this is no
longer required with proposed solution.
4.) It's kind of bad practice to have two deployment architectures within a
single framework. It would be nice to port ServiceDeployer into well designed
Deployer interface + axis2.xml based approach.
5.) With above 3. it is possible to use customized ServiceDeployers easily.
Following entry need to be added to axis2.xml files of existing applications to
keep backward comparability if the applications upgraded to Axis2 1.7.0 or
later versions.
<deployer extension=".aar" directory="services"
class="org.apache.axis2.deployment.ServiceDeployer">
<serviceBuilderExtension name ="jwsbuilderExt"
class="org.apache.axis2.jaxws.framework.JAXWSServiceBuilderExtension"/>
<serviceBuilderExtension name ="wsdlbuilderExt"
class="org.apache.axis2.deployment.WSDLServiceBuilderExtension"/>
</deployer>
was:
Axis2 ServiceDeployer implements Deployer interface like any other Axis2
deployers but it does not use axis2.xml file instead ServiceDeployer is hard
coded in DeploymentEngine. This approach having some limitations.
1.) It is not possible to disable ServiceDeployer if a user only wants to use
any other deployer. ( e.g - only JAX-WS deployer) but other deployers grant
such features.
2.) It is not possible to use newly introduced custom ServiceBuilderExtension
feature with ServiceDeployer.
3.) Standard axis2.xml based <deployer> element use "extension" and
"directory" attributes to define deployment unit type ( file extension) and
container directory. But ServiceDeployer only work with AAR or exploded AAR
archives also use "ServicesDirectory" parameter to specify directory this is no
longer required with proposed solution.
4.) It's kind of bad practice to have two deployment architectures within a
single framework. It would be nice to port ServiceDeployer into well designed
Deployer interface + axis2.xml based approach.
5.) With above 3. it is possible to use customized ServiceDeployers easily.
Following entry need to be added to axis2.xml files of existing applications to
keep backward comparability if the applications upgraded to Axis2 1.7.0 or
later versions.
<deployer extension=".aar" directory="services"
class="org.apache.axis2.deployment.ServiceDeployer">
<serviceBuilderExtension name ="jwsbuilderExt"
class="org.apache.axis2.jaxws.framework.JAXWSServiceBuilderExtension"/>
<serviceBuilderExtension name ="jwsbuilderExt"
class="org.apache.axis2.deployment.WSDLServiceBuilderExtension"/>
</deployer>
> ServiceDeployer should follow the standard deployment architecture
> -------------------------------------------------------------------
>
> Key: AXIS2-5340
> URL: https://issues.apache.org/jira/browse/AXIS2-5340
> Project: Axis2
> Issue Type: Improvement
> Components: kernel
> Affects Versions: 1.6.2
> Reporter: Sagara Gunathunga
> Assignee: Sagara Gunathunga
> Fix For: 1.7.0
>
>
> Axis2 ServiceDeployer implements Deployer interface like any other Axis2
> deployers but it does not use axis2.xml file instead ServiceDeployer is hard
> coded in DeploymentEngine. This approach having some limitations.
> 1.) It is not possible to disable ServiceDeployer if a user only wants to use
> any other deployer. ( e.g - only JAX-WS deployer) but other deployers grant
> such features.
> 2.) It is not possible to use newly introduced custom
> ServiceBuilderExtension feature with ServiceDeployer.
> 3.) Standard axis2.xml based <deployer> element use "extension" and
> "directory" attributes to define deployment unit type ( file extension) and
> container directory. But ServiceDeployer only work with AAR or exploded AAR
> archives also use "ServicesDirectory" parameter to specify directory this is
> no longer required with proposed solution.
>
> 4.) It's kind of bad practice to have two deployment architectures within a
> single framework. It would be nice to port ServiceDeployer into well designed
> Deployer interface + axis2.xml based approach.
>
> 5.) With above 3. it is possible to use customized ServiceDeployers easily.
> Following entry need to be added to axis2.xml files of existing applications
> to keep backward comparability if the applications upgraded to Axis2 1.7.0 or
> later versions.
> <deployer extension=".aar" directory="services"
> class="org.apache.axis2.deployment.ServiceDeployer">
> <serviceBuilderExtension name ="jwsbuilderExt"
> class="org.apache.axis2.jaxws.framework.JAXWSServiceBuilderExtension"/>
> <serviceBuilderExtension name ="wsdlbuilderExt"
> class="org.apache.axis2.deployment.WSDLServiceBuilderExtension"/>
> </deployer>
--
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]
