I reviewed that article and still don't see how that would help. Sure I could set a <parameter> at various levels, Global, Service or Module, but I'm trying to do more than that. I have files like *.xsd, *.xml files & other customer configuration *.property data files. I don't want customers to be able to go into the aar file and make configuration changes and then we update them and blow all those changes away.
We sell our software to customers which we install from our office. So what I need to have is a set of files to meet these requirements: 1. Default settings (which could be done in the axis2.xml file) but the problem with those is they don't get deployed with the service but only installed when setting up a new server. I could live with that if I had to. 2. Files that can be updated by the customers. These files can't be part of the aar file since the customer would have to extract the files, and repackage them. This would be a support nightmare, I could deliver this application in the extracted format to overcome this issue. 3. My SOAP server from Axis v1 included a customized welcome page, a tutorial, JavaDocs for the SOAP services and a link to get the services. So for this it appears that I'll have to package the entice Axis2 web so I can include web pages that are up to date for the current SOAP services. 4. We use Liquibase to manage the schemas. This means that we need to include and read *.xml files for the schema information that I'll need to read when the SOAP service starts up. 5. We have xslt file that are used for formatted responses that need to be read from the file system. Regards, Rick Cromer -----Original Message----- From: Deepal jayasinghe [mailto:[email protected]] Sent: Monday, February 23, 2009 2:26 PM To: [email protected] Subject: Re: AXIS2 - property file locations when creating aar file have a look at http://www.developer.com/open/article.php/10930_3557741_2 You just need to add your property file into your aar file, and you can access them as you access from a jar file. Thank you! Deepal > When I build an aar file and I need to deploy files that support the > web services. For example, general site configuration *.properties > file and files that the customer receiving the packaged web service > will need to configure. Where do these files go and is there a > recommended technique to create the path to these files? > > > Regards, > Rick Cromer > > -- Thank you! http://blogs.deepal.org http://deepal.org
