So you mean you would like: repo/services/finance/fs1.aar repo/services/accounting/acctserv1,2,3.aar etc
I think this would be a fantastic improvement. +1 from me. Paul On 1/22/08, Guillaume Cauchon <[EMAIL PROTECTED]> wrote: > > 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. 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… > > > > A simple test made with this morning SNAPSHOT: > *This Web axisService has deployment faults* > > 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? > > > > Thanks > > > ------------------------------ > > Guillaume Cauchon | DataDirect Technologies inc. > > -email: > > [EMAIL PROTECTED] > > -mobile: > > 418.952-7357 > > -work: > > 418.649-1551 > > > -- Paul Fremantle Co-Founder and VP of Technical Sales, WSO2 OASIS WS-RX TC Co-chair blog: http://pzf.fremantle.org [EMAIL PROTECTED] "Oxygenating the Web Service Platform", www.wso2.com
