If you configure a Groovy or Aspectj class in the spring configuration file, you must follow these conventions:

• Use the classpath protocol:

  script-source="classpath:"
  

  Using a relative file path is not possible because the SCA package is not treated as a regular JAR file for the class loader. For example, the following classpath protocol indicates to find the Groovy file from the class path.

  script-source="classpath:service/GroovyGreeter.groovy"
  

• Add Groovy and Aspectj files in any of the following directories when using the classpath protocol. No other directories are possible.

  • SCA-INF/classes

  • SCA-INF/lib

  • Shared SOA lib

  If your build scripts are configured to clean the classes directory, either put the Groovy files in the SCA-INF/lib directory or design your build scripts to prevent cleaning.

• Add spring extension JAR file libraries for Groovy or Aspectj to the class path of the managed server's setDomainENV.sh or setDomainENV.bat file and restart the server. This ensures that deployment is successful. The restart is required because spring uses Java reflection to instantiate aspect-oriented programming (AOP). The use of reflection restricts the search for classes to the system class loader. Any changes to the system class loader require a server restart.