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 "Jarek Gawor (JIRA)" <ji...@apache.org> on 2008/10/27 22:01:45 UTC
[jira] Created: (AXIS2-4101) Confclit with multiiple deployers for
the same extension
Confclit with multiiple 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: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org
[jira] Updated: (AXIS2-4101) Conflict with multiple deployers for
the same extension
Posted by "Jarek Gawor (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AXIS2-4101?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jarek Gawor updated AXIS2-4101:
-------------------------------
Description:
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().
was:
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().
Summary: Conflict with multiple deployers for the same extension (was: Confclit with multiiple deployers for the same extension)
> 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: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org
[jira] Commented: (AXIS2-4101) Conflict with multiple deployers for
the same extension
Posted by "Jarek Gawor (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AXIS2-4101?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12644397#action_12644397 ]
Jarek Gawor commented on AXIS2-4101:
------------------------------------
I committed a partial fix this problem (revision 709529). With this patch the right Deployer will be used based on the file extension and the directory. Also, changed the code so that 'directory' parameter for a Deployer entry is required (to match schema) and the Deployer entries without the 'directory' or 'extension' parameters won't abort processing of the remaining Deployer entries.
The only remaining issue is how the RepositoryListener.findServicesInDirectory() should behave when it finds a non-service module. That's currently under a discussion on the mailing list.
> 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: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org
[jira] Reopened: (AXIS2-4101) Conflict with multiple deployers for
the same extension
Posted by "Jarek Gawor (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AXIS2-4101?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jarek Gawor reopened AXIS2-4101:
--------------------------------
Deepal,
Please take a look at the code. The code assumes there is one deployer per extension and things are broken.
> 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: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org
[jira] Resolved: (AXIS2-4101) Conflict with multiple deployers for
the same extension
Posted by "Deepal Jayasinghe (JIRA)" <ji...@apache.org>.
[ 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: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org
[jira] Updated: (AXIS2-4101) Conflict with multiple deployers for
the same extension
Posted by "Deepal Jayasinghe (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AXIS2-4101?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Deepal Jayasinghe updated AXIS2-4101:
-------------------------------------
Fix Version/s: (was: 1.5)
nightly
> 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: nightly
>
>
> 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.