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

GuiceyFruit provides a number of utilities on top of the Guice 2.x to help developers work with standard Annotations for injection and lifecycles from JSR 250, Spring, EJB3 and JPA as well as ... [More] supporting Maven and improved Testing GuiceyFruit includes these features Support for @Resource injection for JSR 250 / EJB3 and @PersistenceContext injection from JPA (see Annotations) Support for Spring annotations and lifecycle interfaces Lifecycle support such as for @PostConstruct, @PreDestroy from JSR 250 & EJB3 a Guice based JNDI provider to help you make that J2EE code all Guicey underneath! :) Guicey Testing for easy injection of resources into your test classes in JUnit3, JUnit4 or TestNG with flexible mapping to the Guice Modules for your test cases a Spring XML to Java code converter to help you turn that Spring XML into Java code Maven fully mavenized for easy use from Maven builds NewsThe 2.0 release has just been performed after the Guice 2.0 release! Get it while its hot! [Less]

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

A Cool NEW Framework for Hot, Quick-Fire ( n Sure-Fire !! ;-) ) Rapid Application Development with the help of IOC containers (like Guice, Spring, etc) & ORM tools (like Hibernate, Ibatis, etc ) ... [More] Also allow for/Promote nice (?! :) ) principles like 'Loose Coupling', Testability (using Unit testing tools like JUnit, TestNG, et al..), etc..! Invite Your Comments,& Suggestions...! :) Please Feel Free to INJECT your thoughts n ideas on this..! Please Do 'Look Out' for it...!! ( And we'll 'Look Forward' to your Response too..!! :) After that, there should be no 'Looking Back'..!! ;) ) Coming Soon....! Watch this space...! :) [Less]

Use Google Guice on Android

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]