Java – spring 3.0.5 library jars

javaspring

All,
I am starting with Spring and got the Spring 3.0.5 distribution.
I see the following jars:

org.springframework.aop-3.0.5.RELEASE.jar
org.springframework.asm-3.0.5.RELEASE.jar
org.springframework.aspects-3.0.5.RELEASE.jar
org.springframework.beans-3.0.5.RELEASE.jar
org.springframework.context.support-3.0.5.RELEASE.jar
org.springframework.context-3.0.5.RELEASE.jar
org.springframework.core-3.0.5.RELEASE.jar
org.springframework.expression-3.0.5.RELEASE.jar
org.springframework.instrument.tomcat-3.0.5.RELEASE.jar
org.springframework.instrument-3.0.5.RELEASE.jar
org.springframework.jdbc-3.0.5.RELEASE.jar
org.springframework.jms-3.0.5.RELEASE.jar
org.springframework.orm-3.0.5.RELEASE.jar
org.springframework.oxm-3.0.5.RELEASE.jar
org.springframework.test-3.0.5.RELEASE.jar
org.springframework.transaction-3.0.5.RELEASE.jar
org.springframework.web.portlet-3.0.5.RELEASE.jar
org.springframework.web.servlet-3.0.5.RELEASE.jar
org.springframework.web.struts-3.0.5.RELEASE.jar
org.springframework.web-3.0.5.RELEASE.jar

I want to know which jar is meant for which module of Spring (ORM, Core, MVC, AOP etc).
So that I can choose the correct set of jars for my project.

Is there a reference somewhere that explains each jar and it's use correctly?

Best Answer

There is a following chart (from Diagram of Spring 3.0 module dependencies):

alt text

As you can see, there are several groups of modules:

"Core Spring" - context and its dependencies (asm is missed, aop depends on it)
Web
- web - basic webapp integration
- webmvc (web.servlet) - Spring MVC Framework
- webmvc-portlet (web.portlet) - Spring MVC for portlets
- web.struts - Struts integration
Data access
- tx (transaction) - basic transaction support
- jdbc - JDBC support
- orm - ORM integration
Other modules
- context-support - integration with Quartz, Javamail, Ehcache, etc
- jms, oxm - JMS and object-XML mapping respectively
- test - for unit testing
- aspects - AspectJ intergration (usually not needed)
- instrument, instrument.tomcat - load-time weaving

So, if you use build tool that supports transitive dependencies (such as Maven), you usually only need to declare the required modules from web and data groups, and some from the other modules, if needed. Also you may need to declare context in order to configure logging.

For example, if you want to create a web application with Spring MVC and Hibernate, you declare webmvc (web.servlet) and orm. If you don't use Maven, you also need to import their transitive dependencies, as shown on the chart.

See also:

Related Solutions

Java – Problem with AnnotationSessionFactoryBean

You're are using SLF4J, but only have the SLF4j-API in the classpath. You also need an implementation of SLF4J, such as the SLF4j-NOP or SLF4j-Simplelogger.

You can see this by implementing a simple test case, which initializes the Spring ApplicationContext, and run it with Java 6 to see which Class cannot be found:

public class AppCtxTest {
    @Test
    public void testApplicationContext() throws Exception {
        FileSystemXmlApplicationContext ctx = new FileSystemXmlApplicationContext(
                "app/WEB-INF/services.xml");
        ctx.close();
    }
}

The output will show what is missing;

org.springframework.beans.factory.BeanCreationException:
    Error creating bean with name 'userService' defined in file [C:\Users\mhaller\workspace\Blog\app\WEB-INF\services.xml]:
    Cannot resolve reference to bean 'sessionFactory' while setting bean property 'sessionFactory';
    nested exception is ...
Caused by: org.springframework.beans.factory.BeanCreationException:
    Error creating bean with name 'sessionFactory' defined in file [C:\Users\mhaller\workspace\Blog\app\WEB-INF\services.xml]:
    Invocation of init method failed;
    nested exception is java.lang.NoClassDefFoundError: org/slf4j/impl/StaticLoggerBinder
Caused by: java.lang.NoClassDefFoundError: org/slf4j/impl/StaticLoggerBinder
Caused by: java.lang.ClassNotFoundException: org.slf4j.impl.StaticLoggerBinder

Indeed there are some more dependencies missing:

SLFJ4j Implementation (slf4j-xxx.jar)
Java Persistence API (jpa.jar): javax.persistence.ElementCollection

Java – What’s the difference between @Component, @Repository & @Service annotations in Spring

From Spring Documentation:

The @Repository annotation is a marker for any class that fulfils the role or stereotype of a repository (also known as Data Access Object or DAO). Among the uses of this marker is the automatic translation of exceptions, as described in Exception Translation.

Spring provides further stereotype annotations: @Component, @Service, and @Controller. @Component is a generic stereotype for any Spring-managed component. @Repository, @Service, and @Controller are specializations of @Component for more specific use cases (in the persistence, service, and presentation layers, respectively). Therefore, you can annotate your component classes with @Component, but, by annotating them with @Repository, @Service, or @Controller instead, your classes are more properly suited for processing by tools or associating with aspects.

For example, these stereotype annotations make ideal targets for pointcuts. @Repository, @Service, and @Controller can also carry additional semantics in future releases of the Spring Framework. Thus, if you are choosing between using @Component or @Service for your service layer, @Service is clearly the better choice. Similarly, as stated earlier, @Repository is already supported as a marker for automatic exception translation in your persistence layer.

Annotation	Meaning
`@Component`	generic stereotype for any Spring-managed component
`@Repository`	stereotype for persistence layer
`@Service`	stereotype for service layer
`@Controller`	stereotype for presentation layer (spring-mvc)

Best Answer

Related Solutions

Java – Problem with AnnotationSessionFactoryBean

Java – What’s the difference between @Component, @Repository & @Service annotations in Spring

Related Topic