Hi Andrew, I am fairly new to Axis2 so I can offer non-Sage advice ... but some real experience information...
I am building multiple services that get bundled into one .aar file. I have a servcies.xml file that uses this structure <serviceGroup> <service name=... </service> <service name=... </service> </serviceGroup> And a build system using legacy makefiles and ant to build each service separately. I have directory that contains the services, each in a separate package and a directory that contains the test clients, each in a separate package. This works well for me. I can compile all the services using java2wsdl and then compile all the clients using wsdl2java. I use eclipse too and all the services are in one project but the compiling is all done with the legacy makefiles/ant system on the command line / cygwin shell. The only draw back to this is that sometimes I have to refresh Eclipse to see the stub changes. I hope this helps ... if you have additional questions please feel free to contact me directly. Jon -----Original Message----- From: Andrew Clegg [mailto:[EMAIL PROTECTED] Sent: Friday, June 20, 2008 5:49 AM To: [email protected] Subject: Multiple services from one WSDL... advice? Morning folks, a new Axis2 user here seeking some sage advice. I'm working on a new WS interface for a scientific compute farm, using Axis2 to generate server classes from WSDLs. The WSDLs currently define three services: Submit, Monitor and Retrieve. Submit offers various operations for submitting jobs of various kinds to the farm for processing, each of which returns a JobID. Monitor provides operations for checking the status of jobs, nodes etc. Retrieve contains operations for getting the results of finished jobs back in several different formats. Submit, Monitor and Retrieve are currently separate services but I would be happy putting them in as separate ports within one service. Ideally, I'd like to be able to run the code generator once on a single master WSDL, and generate stubs for all three services/ports -- but this isn't allowed. (At least in 1.3, which we are using -- has this changed in 1.4?) So instead I'm planning on keeping them in separate services, and writing a custom Ant task that runs the code generator three times and deploys three separate services to the server. Each of the three would need separate directories for src, resources and bin, in order to avoid clashes. We're working in Eclipse but don't want to set up completely separate projects for the three services, because of (a) the amount of back-end code that'll be shared between them and (b) the fact that we want to keep them together in Subversion to simplify versioning. In your experience, would this work, or can you think of a better way? Are there any other 'gotchas' I should look out for? Thanks in advance, Andrew. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
