Hi An SCA application is contained within one or more contributions. A contribution defines a tree structure space (directory, JAR, ZIP, WAR etc) within which the SCA runtime can find resources. IIRC when a WAR resource is deployed to a container the whole WAR is assumed to be the contribution so the root of the tree is the root of the web app rather than WEB-INF/classes. Does that make sense?
Having said the the implementation.spring spec does specify some extra rule for locating the spring context and the resources within it: >From line 80 of sca-springci-draft-20070926.doc =================== The only part of this that is specific to Spring is the <implementation.spring> element. The location attribute of that element specifies the target uri of an archive file or directory that contains the Spring application context files. The resource paths to the Spring application context configuration files that are used to create the application context are then identified as follows: If the resource identified by the location attribute is an archive file, then the file META-INF/MANIFEST.MF is read from the archive. If the location URI identifies a directory, then META-INF/MANIFEST.MF must exist underneath that directory. 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 set of paths specified in the header identify the context configuration files. 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 all the *.xml files in the META-INF/spring directory. =================== Not sure if that's answered your question or not? Regards Simon
