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 "Deepal Jayasinghe (JIRA)" <ji...@apache.org> on 2008/07/04 13:39:34 UTC
[jira] Resolved: (AXIS2-2250) Cannot deploy a service through admin
console when a custom repository location is given in axis2.xml
[ https://issues.apache.org/jira/browse/AXIS2-2250?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Deepal Jayasinghe resolved AXIS2-2250.
--------------------------------------
Resolution: Won't Fix
> Cannot deploy a service through admin console when a custom repository location is given in axis2.xml
> -----------------------------------------------------------------------------------------------------
>
> Key: AXIS2-2250
> URL: https://issues.apache.org/jira/browse/AXIS2-2250
> Project: Axis 2.0 (Axis2)
> Issue Type: Bug
> Components: admin console
> Affects Versions: nightly
> Environment: winxp, jdk1.5, tomcat 5.5.16
> Reporter: Charitha Kankanamge
> Assignee: Deepal Jayasinghe
>
> A service cannot be deployed using admin console upload facility when a custom repository location is specified in axis2.xml.
> Steps to reproduce:
> ===============
> 1. Edit the axis2.xml as follows.
> <parameter name="ServicesDirectory" locked="false">C:\Temp</parameter>
> 2. Restart tomcat and access axis2 admin page
> 3. Upload a service archive
> The uploaded service will not be listed in the available services list and cannot be seen under the custom repository.
--
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