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

Jump to tag:

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

Filtered by Project Tags dependencyinjection ioc spring

Refine results Project Tags java (3) di (2) guice (2) inversionofcontrol (2) elementry (1) client (1) validation (1) testing (1) junit (1) compact (1) reflection (1) easymock (1)

[5 total ]

1 Users
gwtoolbox

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). ... [More] Current modulesCurrently the following modules are 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. Quick StartTo quickly create a GWToolbox based project, you can use the following link. This will redirect you to a form which will help you create an initial maven2 project using a dedicated maven archetype: http://gwtoolboxarchetype.appspot.com [Less]
Created about 1 year ago.

0 Users
ninject-contrib

A collection of community-created extensions and examples related to the Ninject dependency injection project.
Created 12 months ago.

0 Users
atunit

AtUnitAtUnit minimizes boilerplate code in unit tests and guides test development by enforcing good practices. mark exactly one field with @Unit to indicate the object under test. mark fields with ... [More] @Mock or @Stub to obtain mock objects inject your tests, and your test subjects, using your favorite IoC container Mock Objects IntegrationAtUnit integrates with JMock or EasyMock to provide mock objects: obtain a JMock context simply by declaring a field annotate fields with @Mock to obtain JMock or EasyMock mock objects annotate fields with @Stub to obtain a JMock or EasyMock stub object ... or you can use your own mock objects plug-in with two easy steps: implement the MockFramework interface annotate your tests with @MockFrameworkClass(MyMockFramework.class) Container IntegrationAtUnit integrates with Guice or Spring to take all of the work out of dependency-injected tests. With Guice: never see the Injector, never write bootstrapping boilerplate! @Inject test class fields without even defining a Module declaratively obtain mock objects with @Inject @Mock if you need more binding flexibility, simply have your test class implement Module With Spring: annotate fields with @Bean to get them from the Spring context fields annotated with @Bean which do not appear in your Spring context are added to it automatically! (This includes @Mock and @Stub fields.) AtUnit looks for a Spring XML file with the same name as your test, or you can specify the location yourself with @Context("filename") Most of the time, you don't even need a Spring XML file! You can easily plug in other containers in two steps: implement the Container interface annotate your tests with @ContainerClass(MyContainer.class) Get StartedThese Example AtUnit Tests are the quickest way to get started with AtUnit. They demonstrate most permutations of supported containers and mock frameworks, and illustrate the various ways AtUnit makes writing tests easier. [Less]
Created about 1 year ago.

0 Users
tofigurator

DescriptionThe target of this project is to build easy, reliable, flexible and universal Java Configuration Tool. This library is very good and also very compact implementation of IoC(Inversion of ... [More] Control) and DI(Dependency Injection) programming concepts. Jar is very small and is suitable even for Java Applets. Works well and for Java Clients and for Java Server Applications. Can manage very small and very large number of configuration parameters. Can inject configuration values into any reachable Java Class and/or Java Object. RequirementsThis is a library of several Java Classes packaged into jar This tool allows setting new values to Java class and instance properties This tool fits to any Java project and is generic It is simple and intuitively understandable It is XML based declarative programming style It is easily integrating with any Java project with minimum efforts and maximum use It can handle hundreds of thousands configuration parameters It supports several levels of Hierarchy. As Package, Class, Instances, Parameters, Arrays and Files Hierarchies Configuration structure could be not matching the code structure Soft code reflection. Meaning use Java reflection capabilities in soft manner avoiding performance and resources management problems Type freedom. Configuration is not dependent on code parameters types. Configuration could be even more complex and more flexible than java code(Type freedom concept is about developing configuration and code separately and then easy integrate) Interpretation is taking over interfacing Tofigurator is built on Elementry Principals Contents tofigurator Featurestofigurator package is made to configure Java Classes and Instances of Java Classes Configuration is defined in XML files Configuration files could import other configuration files. That creates a hierarchy of files. Recursive cross imports problem is resolved by allowing one time import for each file tofigurator synchronizes it's inner configuration storage with Java System Properties. That allows accessing to System Parameters through tofigurator tools. tofigurator is capable of exporting of all configuration parameters into XML files in flat and hierarchical manner. tofigurator is capable to set values to all variables of all Java primitive types with any level of access protection. Meaning even private inner members of object are configurable by tofigurator package tofigurator is capable to set values to String, Date and ParameterizedString members. Other special interpretation types could be easily added tofigurator is self-configurable and for example the syntax of configuration XML files could be changed through configuration without changing the code tofigurator is implemented as regular java class CConfigurator. Some additional functionalities are implemented in static wrapper SConfigurator Configuration and Class structure matching is not mandatory. tofigurator is complaint to Type Freedom programming concept tofigurator doesn't change value of class member if corresponding configuration parameter is not specified. So default values yet could be defined in Java classes Configuration could be silent or not. Depends on configuration parameter. Default for tofigurator is silent behavior. If silent parameter is set to false tofigurator will report every conflict and parameter missing. That could prevent configuration problems and complications while code debugging For more information click on Contents [Less]
Created about 1 year ago.

0 Users
autumnframework

This project implements Dependency Injection for C++. It supports property setter injection and constructor injection. It is compiled on multiple platform. It supports POCO (Plain Old C++ Object) and ... [More] has no constraints on the classes you create. It has no incursion to your program code. Autumn framework contains two parts: a dynamic library and a wrapper generator named AutumnGen. Autumn use a Small, simple, cross-platform, free and fast C++ XML Parser written by Frank Vanden Berghen to parse config file. 07/26/2007 Ver 0.5.0 released.This version: support multi-inheritance, including direct and indirect inheritance. Indirect inheritance should list base classes in doccomment. add namespace Autumn for Autumn framework. decorate some class member functions with const. other changes, including Issues 1~3 05/21/2007 Ver 0.4.0 released.This version: has AutumnGen, a generator for wrapper files. You needn't now write any code to use Autumn framework, you can generate wrapper files(a head file and a implementation file) from a head file with AutumnGen. bean support init-method, destroy-method and delete-method attributes. change "type" to "bean", remove "type" element in configure file. 03/26/2007 Ver 0.3.0 released.This version: needn't set property's type or constructor argument's type in configuration file. If set, it will replace the type got with wrapper. bean supports factory-method attribute and multiple factory methods, and don't support overloading. erase bean's attributes: initializable and destroyable. Bean supports init and destroy function however, it's decided by definition of bean wrapper support bean reference. unite IBasicType and ICombinedType into IAutumnType. 03/13/2007 Ver 0.2.0 released.This version supports creating bean using 'instance factory' and 'static factory method' patterns. You can find samples in test project. 03/05/2007 Ver 0.1.0 released.You can download source code here. A simple install guide is here.The code has been compiled on: WindowsXP with Visual C++ 6.0 Linux Ubuntu 6.06 with GCC 4.0.3 SunOS 5.10 i86pc with Sun C++ 5.8 AIX 5L with XL C V7.0 01/16/2007 Ver 0.1.0 beta for Windows VC6 released.You can download it here. Some docs are here. CppDoc is here. It may be very babyish now, because I don't know Spring well and do this to imitate Spring in a hurry. I will write some docs ASAP. Now, it support: Support property injection and constructor injection.Only two constructors now, one has arguments and one has no argument. The setter function name should be like setXXX where XXX is a property name. You may not obey that rule if you rewrite the file BeanWrapperMacro.h. Support following basic type: char, short, int, long, float, double, char*, string, and some docrated with unsigned. Support class injection. (A class is named as a bean in Autumn like in Spring.) Support customized type using interface IBasicType. Support pointer to above types. Support singleton. Support initialization and destroyation functions. Support property setter overloading. Supoort dependence(it may be not like Spring). Support multiple dynamic libraries and local library(bean is in main process). Support configuration of log file path and level. [Less]
Created about 1 year ago.
Popular Tags

Project Tags java python php gme framework c web javascript game linux