axis-java-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Amila Chinthaka Suriarachchi (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (AXIS2-5314) loadServicesFromUrl(URL repoURL) and loadRepositoryFromURL(URL repoURL) methods on DeploymentEngine are outdated.
Date Tue, 08 May 2012 11:49:51 GMT

    [ https://issues.apache.org/jira/browse/AXIS2-5314?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13270383#comment-13270383
] 

Amila Chinthaka Suriarachchi commented on AXIS2-5314:
-----------------------------------------------------

IIRC these methods were used to load modules and services from a url. structure of the repository
should be same as a normal file system repository url. 

it uses the module.list and services.list files since there is no way to get the existing
service or module file names as in a file system. But for an embeded jar it is not the case.



                
> 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 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: java-dev-unsubscribe@axis.apache.org
For additional commands, e-mail: java-dev-help@axis.apache.org


Mime
View raw message