BibSonomy ::  tag ::

order by ( date | folkrank )

Coming back to the above post by Anton, yes, the kind of runtime type checking exists in lots of popular Java frameworks, even today. And this is where frameworks like Guice and EasyMock really shine with their strongly typed API sets that make you feel more secure within the confines of your IDE and refactoring abilities. The Morale When you are programming in a statically typed language, use appropriate language features to make most of your type checking at compile time. This way, before you hit the run button, you can be assured that your code is well-formed within the bounds of the type system. And you have the power of easier refactoring and cleaner evolution of your codebase.

Dependency Injection has been around for a while, and many teams are refactoring their applications to use DI. But it can be a struggle. In this article, Paul Hammant explains the route to take to move an existing application from a nest-of-singletons ...

pinky is a Scala REST/MVC glue web framework built on top of Guice and Guice Servlet. Pinky provides out-of-the-box support for dealing with forms, domain objects, jdbc and rss/xml/json/html content types

Current we support: Hibernate 3.1 Java Persistence API (sometimes called JPA or EJB3 persistence) Db4Objects (a lightweight object database) It works inside a Java EE container, inside a plain Servlet environment or in a purely SE environment such as a desktop application (with obvious limitations--cant use session-per-http-request strategy outside a servlet environment for instance

AtUnit 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 @Mock or @Stub to obtain mock objects * inject your tests, and your test subjects, using your favorite IoC container Mock Objects Integration AtUnit 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 Integration AtUnit 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)