[
https://issues.apache.org/jira/browse/AXIS2-4101?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Deepal Jayasinghe resolved AXIS2-4101.
--------------------------------------
Resolution: Fixed
This is not an issues , because what unique is combination of both the
extension and the directory. So it is ok to have two deployer looking at the
same extension but in different folders.
Thank you!
Deepal
> Conflict with multiple deployers for the same extension
> --------------------------------------------------------
>
> Key: AXIS2-4101
> URL: https://issues.apache.org/jira/browse/AXIS2-4101
> Project: Axis 2.0 (Axis2)
> Issue Type: Bug
> Components: kernel
> Affects Versions: nightly
> Reporter: Jarek Gawor
> Priority: Critical
> Fix For: 1.5
>
>
> The axis2.xml contains the following entries for two deployers for the same
> extension:
> <deployer extension=".jar" directory="servicejars"
> class="org.apache.axis2.jaxws.framework.JAXWSDeployer"/>
> <deployer extension=".jar" directory="transports"
> class="org.apache.axis2.deployment.TransportDeployer"/>
> Once would think that any jar files found in the "servicejars" directory
> would be handled by the JAXWSDeployer and jar files found in the "transports"
> directory would be handled by the TransportDeployer. However, this is not
> implemented that way. In fact, the code assumes that there is only one
> Deployer for a given extension. So effectively the JAXWSDeployer will never
> be called/used. See AxisConfigBuilder.processDeployers() or
> DeploymentEngine.getDeployerForExtension().
--
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: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
