> I’ve been playing around with Axis2 in the last few days to see if it > could fit the SOAP stack needs of the project I’m working on. > Great. > > One of the features I’m looking for is the possibility to organize my > web services (archives, POJOs, etc…) under the services repository > (i.e. sub directories), but this feature doesn’t seams to be available > yet… > You can do that As I can understand you want to add service aar file and POJOs into the same directory repository services foo.aar xyz.aar MyPojo.class module
However you have to configure the deployers in your axis2.xml. > A simple test made with this morning SNAPSHOT: > > > *This Web axisService has deployment faults* > As I can see the error is due to you are trying to deploy an invalid service , and that service does not have META-INF directory which is essential to be a valid service. Thanks Deepal > > > ** > > Error: org.apache.axis2.deployment.DeploymentException: Invalid > service. META-INF directory not found. at > org.apache.axis2.deployment.repository.util.ArchiveReader.processWSDLs(ArchiveReader.java:297) > at > org.apache.axis2.deployment.ServiceDeployer.deploy(ServiceDeployer.java:66) > at > org.apache.axis2.deployment.repository.util.DeploymentFileData.deploy(DeploymentFileData.java:136) > at > org.apache.axis2.deployment.DeploymentEngine.doDeploy(DeploymentEngine.java:584) > at > org.apache.axis2.deployment.repository.util.WSInfoList.update(WSInfoList.java:141) > at > org.apache.axis2.deployment.RepositoryListener.update(RepositoryListener.java:330) > at > org.apache.axis2.deployment.RepositoryListener.checkServices(RepositoryListener.java:227) > at > org.apache.axis2.deployment.RepositoryListener.startListener(RepositoryListener.java:324) > 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:83) > at > > … > > I need to evaluate the amount of work required to get this kind of > feature available, keep in mind that I’m only beginning in the Axis2 > codebase so I still have a lot of things to learn about the > architecture… My question now, other than extending > org.apache.axis2.deployment.ServiceDeployer so that I can get the web > services deployed, what would be required for this repository > “hierarchy” to work with all of the other components of Axis : > run-time, management, etc? > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
