Projects tagged ‘ioc’, ‘java’, and ‘spring’

Spring is a lightweight Java/J2EE application framework based on code published in "Expert One-on-One J2EE Design and Development" by Rod Johnson. It includes powerful JavaBeans-based configuration management applying Inversion-of-Control principles ... [More] , a generic abstraction layer for transaction management allowing for pluggable transaction managers, a JDBC abstraction layer, integration with Hibernate, JDO, Apache OJB, and iBATIS SQL Maps, AOP functionality, and a flexible MVC Web application framework with multiple view technologies. There is also a .NET port available. [Less]

A collection of modules, add-ons and integration tools for the Spring Framework.

Spring-Annotation is a library that enables the use or annotations to configure your application using spring-framework as a backend. In the next versions it will enable the use of standard Java EE annotations as an alternative way to configure your application, but without a need for a full Java EE 5 application server.

GWToolboxWelcome to the GWToolbox project. The GWToolbox project provides a collection of modules to help developers create robust web 2.0 / Ajax applications using the Google Web Toolkit (GWT). Current modulesCurrently the following modules are ... [More] provided: gwtoolbox-commons: A library with common utility classes which are used by other modules and can also be used by other GWT applications. This collection of utilities is largely based on common Java Open Source projects (e.g. Spring, apache commons, etc..) gwtoolbox-bean: A library that brings the power of Java bean programming to GWT applications. Constructs like PropertyDescriptor, BeanInfo, and PropertyChangeListeners can now be used and applied transparently on a simple GWT Java bean. This module also comes with bean binding and validation support. gwtoolbox-ioc: This module bring IoC to GWT applications. Heavily based on Spring, users can now define all object/widgets/components of their GWT application within Spring application context and wire them declaratively. This is now yet another Spring-like ioc container, but rather a container that can read actual Spring configuration files. This brings along many of the power tools Spring comes with: AspectJ-like AOP support, bean life-cycle management (including lazy/eager initialization), scopes (singleton/prototype), and even Spring namespaces. Users can now create proprietary namespaces for their GWT components. Modules in developmentThe following modules are currently in development: gwtoolbox-widget: A set of generic model based widget classes with concrete implementations of bean backed models. These widgets/models highly depend on the gwtoolbox-bean module. Getting startedTake a look at our Getting Started Guide to get started using GWToolbox to build better GWT applications. [Less]

Arid POJOs is a framework for simplifying POJO application development. Automatic Spring Bean GenerationArid POJOs provides a custom Spring/XML namespace that scans a package hierarchy and generate bean definitions for the classes or interfaces ... [More] that it finds. The classes and interfaces can be filtered by an AspectJ type pattern, which supports various criteria including name matching, annotations, and subtypes. The generated beans use autowiring. Here is a simple example. ... ... The generated bean definitions can also instantiate an entirely different class. The original interface/class is passed as a constructor argument. This is used, for example, with the dynamic Generic DAO feature. Dynamic Generic DAOsArid POJOs can also generate DAO implementations from an interface using a Grails GORM/Rails Active Record like mechanism. Here is an example interface: public interface CustomerRepository extends GenericDao { Customer findByCustomerId(String customerId); Customer findUsingSomeStrangeNamedQuery(String firstName, String lastName); }Arid POJOs will generate a proxy, which implements this interface. The findByCustomerId() method is turned into Criteria Query, which searches on the customerId property, and the findUsingSomeStrangeNamedQuery() method ends up calling a named query. This is accomplished using the following bean definitions: ... ... [Less]