Hi All, Location attribute of <implementation.spring> element basically refers to the location of spring context file, with the current implementation we accept only the spring context file path as input.
As as per the specs, the location attribute should be able to identify the resources from an archive file and from a directory. This issue has been now fixed with TUSCANY-2493. Now the location URI can identify the following resources: 1. A file path pointing directly to the spring context file. 2. A directory path containing spring context files, assuming that this directory exists within the contribution. 3. A archive(.jar) file path containing the spring context files, assuming that the archive(.jar) file exists within the contribution. NOTE: When the location URI identifies a directory OR an archive file, then META-INF/MANIFEST.MF must exist underneath. If the manifest file contains a header "Spring-Context" of the format: Spring-Context ::= path ( ';' path )*, Where path is a relative path with respect to the location URI, then the path specified in the header identify the context configuration file. If there is no MANIFEST.MF file or no Spring-Context header within that file, then the default behaviour is to build an application context using "application-context.xml" file in the META-INF/spring directory. TUSCANY-2493, also includes a JUNIT test with implementation-spring module to demonstrate, how we read a resource from a directory path. -- Thanks & Regards, Ramkumar Ramalingam
