[
https://issues.apache.org/jira/browse/AXIS2-5079?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13055160#comment-13055160
]
nadir amra commented on AXIS2-5079:
-----------------------------------
I verified that this works in 1.6.
> 1.5.5 (and probably 1.6) does not alow exploaded services to be dropped in
> services directory
> ---------------------------------------------------------------------------------------------
>
> Key: AXIS2-5079
> URL: https://issues.apache.org/jira/browse/AXIS2-5079
> Project: Axis2
> Issue Type: Bug
> Components: deployment
> Affects Versions: 1.5.5, 1.6.0
> Environment: windows tomcat 7
> Reporter: nadir amra
> Priority: Critical
>
> Dropped 1.5.5 WAR file in tomcat webapp directory.
> Everything looks good. Then I deleted the version aar file shipped, and it
> gets undeployed. I ended the tomcat server and restarted the server. Then I
> exploaded the version aar file, and then moved the directory to the axis2
> services directory. I click on the list webservices link and I get:
> Available services
> Faulty Services
> C:\Program Files\Apache Software Foundation\Tomcat
> 7.0\webapps\axis2-1.5.5\WEB-INF\services\version
> In the tomcat stdout log file, I see the following:
> INFO] Deploying module: jaxws-1.5.5 - file:/C:/Program Files/Apache Software
> Foundation/Tomcat
> 7.0/webapps/axis2-1.5.5/WEB-INF/modules/axis2-jaxws-mar-1.5.5.mar
> [INFO] Deploying module: metadataExchange-1.5.5 - file:/C:/Program
> Files/Apache Software Foundation/Tomcat
> 7.0/webapps/axis2-1.5.5/WEB-INF/modules/mex-1.5.5.mar
> [INFO] Deploying module: mtompolicy-1.5.5 - file:/C:/Program Files/Apache
> Software Foundation/Tomcat
> 7.0/webapps/axis2-1.5.5/WEB-INF/modules/mtompolicy-1.5.5.mar
> [INFO] Deploying module: ping-1.5.5 - file:/C:/Program Files/Apache Software
> Foundation/Tomcat 7.0/webapps/axis2-1.5.5/WEB-INF/modules/ping-1.5.5.mar
> [INFO] Deploying module: script-1.5.5 - file:/C:/Program Files/Apache
> Software Foundation/Tomcat
> 7.0/webapps/axis2-1.5.5/WEB-INF/modules/scripting-1.5.5.mar
> [INFO] Deploying module: soapmonitor-1.5.5 - file:/C:/Program Files/Apache
> Software Foundation/Tomcat
> 7.0/webapps/axis2-1.5.5/WEB-INF/modules/soapmonitor-1.5.5.mar
> [INFO] The version service, which is not valid, caused
> java.lang.ClassCastException: org.apache.axis2.classloader.JarFileClassLoader
> incompatible with org.apache.axis2.deployment.DeploymentClassLoader
> at
> org.apache.axis2.deployment.ServiceBuilder.populateService(ServiceBuilder.java:131)
> at
> org.apache.axis2.deployment.repository.util.ArchiveReader.buildServiceGroup(ArchiveReader.java:101)
> at
> org.apache.axis2.deployment.repository.util.ArchiveReader.processServiceGroup(ArchiveReader.java:178)
> at
> org.apache.axis2.deployment.ServiceDeployer.deploy(ServiceDeployer.java:82)
> at
> org.apache.axis2.deployment.repository.util.DeploymentFileData.deploy(DeploymentFileData.java:136)
> at
> org.apache.axis2.deployment.DeploymentEngine.doDeploy(DeploymentEngine.java:661)
> at
> org.apache.axis2.deployment.repository.util.WSInfoList.update(WSInfoList.java:144)
> at
> org.apache.axis2.deployment.RepositoryListener.update(RepositoryListener.java:337)
> at
> org.apache.axis2.deployment.RepositoryListener.checkServices(RepositoryListener.java:241)
> at
> org.apache.axis2.deployment.RepositoryListener.startListener(RepositoryListener.java:331)
> at
> org.apache.axis2.deployment.scheduler.SchedulerTask.checkRepository(SchedulerTask.java:64)
> at
> org.apache.axis2.deployment.scheduler.SchedulerTask.run(SchedulerTask.java:71)
> at
> org.apache.axis2.deployment.scheduler.Scheduler$SchedulerTimerTask.run(Scheduler.java:90)
> at java.util.Timer$TimerImpl.run(Timer.java:291)
> [INFO] org.apache.axis2.deployment.DeploymentException:
> org.apache.axis2.classloader.JarFileClassLoader incompatible with
> org.apache.axis2.deployment.DeploymentClassLoader
> This works using Axis 1.5.4. The only major differences between the 1.5.4
> source and the 1.5.5 source is the addition of code relating to:
> <parameter name="EnableChildFirstClassLoading">false</parameter>
> which seems to affect lots of the files relating to deployment.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
