Hello all. I still have classpath issues with my deployed aar archive file and am hoping for some guidance. (My original post is below and mentions log4j configuration as part of my issue, but that a side effect of my classpath issue.) I've reviewed the docs, faqs and wiki entries on the Axis2 site and cannot find any topics on this, so I probably am just missing something.
There are XML configuration files that my service needs access to when deployed; however, with the aar configuration below, it does not find them on the classpath once deployed. How do I deploy my service with configuration files so that it can find and access those resources? Do I need to deploy the service differently? Any guidance (and your time) is appreciated. Thank you. ________________________________ From: Michael Lepine [mailto:[EMAIL PROTECTED] Sent: Tuesday, June 19, 2007 10:23 AM To: [email protected] Subject: service classpath I'm not overly familiar with web services, but I've created a POJO-based web service and am having difficultly logging from the service. The aar archive has the following top-level directory structure: com - class files under the com.xxx.xxx... package META-INF - folder containing the services.xml lib - folder containing library (jar/zip) files for service commons-logging.properties - property file for logging configuration log4j.properties - property file for log4j configuration other.xml - other xml files that need to be accessible via the classpath I'm deploying the aar file to the following folder under the tomcat (version 5.0.28) installation directory: [TOMCAT_HOME]\webapps\axis\WEB-INF\services The service is being deployed correctly and appears to be working. So, should my properties and xml files be accessible via the classpath or am I doing something wrong? Any guidance is appreciated. Thank you. - Mike
