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 "Hudson (JIRA)" <ji...@apache.org> on 2016/03/19 19:49:33 UTC
[jira] [Commented] (AXIS2-5314) loadServicesFromUrl(URL repoURL)
and loadRepositoryFromURL(URL repoURL) methods on DeploymentEngine are
outdated.
[ https://issues.apache.org/jira/browse/AXIS2-5314?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15202908#comment-15202908 ]
Hudson commented on AXIS2-5314:
-------------------------------
FAILURE: Integrated in Axis2 #3404 (See [https://builds.apache.org/job/Axis2/3404/])
AXIS2-5747: Fix DeploymentFileData#getName() so that it returns a consistent value for instances created from URLs. This should fix an issue introduced by AXIS2-5314. (veithen: rev 1735795)
* axis2/modules/kernel/pom.xml
* axis2/modules/kernel/src/org/apache/axis2/deployment/repository/util/DeploymentFileData.java
* axis2/modules/kernel/test/org/apache/axis2/deployment/repository
* axis2/modules/kernel/test/org/apache/axis2/deployment/repository/util
* axis2/modules/kernel/test/org/apache/axis2/deployment/repository/util/DeploymentFileDataTest.java
* axis2/pom.xml
> loadServicesFromUrl(URL repoURL) and loadRepositoryFromURL(URL repoURL) methods on DeploymentEngine are outdated.
> ------------------------------------------------------------------------------------------------------------------
>
> Key: AXIS2-5314
> URL: https://issues.apache.org/jira/browse/AXIS2-5314
> Project: Axis2
> Issue Type: Bug
> Components: kernel
> Affects Versions: 1.6.2
> Reporter: Sagara Gunathunga
> Assignee: Sagara Gunathunga
> Fix For: 1.7.0
>
>
> loadServicesFromUrl(URL repoURL) and loadRepositoryFromURL(URL repoURL) methods on DeploymentEngine are outdated. I found following issues.
> 1.) Above two methods try to deploy modules/services based on files called services.list and modules.list without depend on repository. AFAIK these concepts were used very beginning and haven't maintain for many years.
> 2.) These two methods do not respect to deployment features such as hot deployment, hot update etc.
> 3.) Above methods do not compatible with other deployment approaches and completely ignore Axis2 Deployer architecture. In fact, above method populate Axis2 modules and service within method body themselves instead of calling corresponding Deployer.
> 4.) Above methods do not care/related to repository scheduler job.
> Also I haven't notice any hint that someone use these methods for last few years. I don't see much advantage promoting another deployment approach ( i. e based on services.list and modules.list) again that we haven't maintain for many years. Hence I suggest to remove these methods in future releases. For next release let's keep these methods but sync method bodies with current deployment architecture.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: java-dev-unsubscribe@axis.apache.org
For additional commands, e-mail: java-dev-help@axis.apache.org