by ittayd
border:

Feature-toggle is an agile development paradigm where features are committed to the main development branch, but are turned off until ready. This avoids merging branches and helps discover conflicts between features early. Another benefit is that QA can test the feature and approve it before it officially appears in the product.

 

Many times, a feature-toggle is just an 'if' statement that wraps the entry code to the feature. E.g. 'if (formValidationFeature) validateForm()'

 

by andrew
border:

This is really impressing! They created a full application with several entites on MongoDb, and deployed it to Cloud Foundry. In less than 50 lines of Roo commands from an empty dir to the application deployed on CloudFoundry.com. Actually, in less than 40 lines, if you don't count comments and empty lines :) I don't think even Jango would allow the same with less than 40 lines of script and code combined.

 

by dmitri
border:

Spring JPA aims to significantly improve the implementation of data access layers by reducing the effort to the amount that's actually needed. As a developer you write your repository interfaces, including custom finder methods, and Spring will provide the implementation automatically.

 

Just to feel what Spring JPA is go to the getting-started tutorial at Spring Source Team Blog

 

by dmitri
border:

For a client I had to implement spring based startup module. The module's context xml file simply defines annotation-config and component-scan element and doesn't define any bean. When I add 50-th bean into the module, I reliazed I can't manage dependencies without painting them anymore.

 

The fast search had lead to 3 nice tools: SpringSource Tool Suite, BeanDoc and Maia EAP. Each one of them may analyze dependencies and may paint them. But no one of them may deal with annotations.

 

by zvika
tags:
border:

Recently, I was in need to deploy Spring's sample Travel web application on JBoss 5.1. The process of making the deployment pass mainly consisted of solving mismatches between JBoss JPA and the web-application-contained Hibernate. I hope the following description of the steps will help others (diminishing bunch?)  deploy Spring apps on JBoss 5.1.


1. Remove logj jar from your WEB-INF/lib

tags:
border:
by zvika
tags:
border:

 While reading "AspectJ In Action, 2nd Ed", I ran across the following method of accessing an advised aop proxy from within the proxied class while still activating the aspect functionality:

 

AopContext.currentProxy()

 

 

That's it. Barely worth a post, I know, but may come as great help if you ever used Spring's AOP Wrapping (transactions, caching, ...) and needed to make a self-bound call that should go through the AOP interceptors.

by zvika
border:

This is a summary of the communication methods I’ve employed in an application at one of our clients recently, methods gathered from various other sites, blogs, etc.

 

by zvika
border:

Great presentation based on a lecture given by Yoav Abrahami at Wix.com, which I went to this week - thanks for the invitation, Olga!

AspectJ, AOP, code genetation, and other really interesting & cool stuff!

 

http://www.slideshare.net/yoavwix/java-bytecode-and-classes

by ittayd
tags:
border:

http://www.infoq.com/presentations/Spring-3.0-3.1-3.2

 

"Jurgen Holler reviews the most important features that came with Spring 3.0, he previews the 3.1 version of the framework planned to have its first milestone release in late November 2010, and he takes a sneak preview at Spring 3.2 which is supposed to support Java 7."

Pages