[Springframework-developer] Revised distribution jar files

[<jue...@we...>]

Hi everybody,

I've just revised our distribution jar files for 1.0 M1. There are now 6 =
of them: Each addresses a typical usage of the Spring Framework, =
specifying the respective contents and third-party dependencies. =
Libraries in brackets are optional, i.e. just necessary for certain =
functionality.

Quoting from the new section in our readme.txt:

<quote>

* "spring-beans" (~90 KB)
- Target: basic bean container for wiring up within restricted =
environments like applets
- Contents: bean container, core utilities
- Dependencies: Commons Logging

* "spring-aop" (~145 KB)
- Target: AOP-enabled bean container for wiring up and proxying any kind =
of components
- Contents: bean container, utilities, AOP framework
- Dependencies: Commons Logging, AOP Alliance (Log4J, CGLIB)

* "spring-jdbc" (~230 KB)
- Target: JDBC access library, e.g. for use within EJBs or to enrich =
existing applications
- Contents: bean container, utilities, JDBC support, EJB support
- Dependencies: Commons Logging (Log4J, EJB 2.0)

* "spring-orm" (~350 KB)
- Target: persistence and transaction library for JDBC/Hibernate/JDO, =
including AOP support
- Contents: bean container, utilities, AOP framework, transaction =
framework, JDBC support, O/R Mapping support, EJB access and support
- Dependencies: Commons Logging, AOP Alliance (Log4J, CGLIB; JTA, =
Hibernate, JDO, EJB 2.0)

* "spring-context" (~430 KB)
- Target: application framework for use within or outside a J2EE =
container, e.g. for serving as middle tier application context within =
Struts or Tapestry web applications, or for standalone applications
- Contents: bean container, utilities, AOP framework, transaction =
framework, JDBC support, O/R Mapping support, EJB access and support, =
application context, web application context, validation framework
- Dependencies: Commons Logging, AOP Alliance (Log4J, CGLIB; JTA, =
Hibernate, JDO, EJB 2.0; Servlet 2.2)

* "spring-full" (~550 KB)
- Target: web application framework for use within a J2EE container, =
including Spring's own web MVC and remoting support (and of course, =
suitable for any other usage where JAR size does not matter)
- Contents: bean container, utilities, AOP framework, transaction =
framework, JDBC support, O/R Mapping support, EJB access and support, =
application context, web application context, validation framework, web =
MVC framework, remoting support
- Dependencies: Commons Logging, AOP Alliance (Log4J, CGLIB; JTA, =
Hibernate, JDO, EJB 2.0; Servlet 2.3, JSP 1.2, JSTL, Velocity, iText, =
POI, Hessian, Burlap)

</quote>

I've hesitated a bit to introduce more jar files, but I guess such =
scenario-specific jars are easier to understand than fragmented =
package-level jars that need to be combined to make them work. Anyway, =
I'm open for feedback, of course: Does anyone miss a typical scenario, =
or consider one of the above unnecessary?

Regards,
Juergen


DI J=FCrgen H=F6ller
Senior System Architect
______________________________________

werk3ATS - division systementwicklung
part of werk3AT internetmedien oeg

europaplatz 4
A - 4020 linz

t.  +43 (0) 732 71 65 29 502
f.  +43 (0) 732 71 65 29 3
mailto:jue...@we...
http://www.werk3at.com
______________________________________
werk3ATS - WIR ENTWICKELN ERFOLG