Everything beta

Upgrading to Spring 3.0.0.M3 and Spring Security 3.0.0.M1

Try to use Spring Framework 3.0.2 along with Security 3.0.2, both have been released recently.

Using Spring 3.0 MVC for RESTful web services (rebuttal)

Personally I think yes, it was worth it. If nothing else, it suddenly clarified the layer separation in our app and created the opportunity for a drastic refactoring move where DTOs and controllers along with all top-level validation were consolidated into one logical tier, leaving the services tier free from any view-related logic and concerned only with the core domain.

Arguably a proper REST service implementation using RESTEasy would achieve the same goals I posted above but with our @Controllers being POJOs now, a port to any proper JAX-RS implementation means refactoring only annotations and nothing else. This newly acquired portability freedom makes the choice of any such technology being based on aspects like performance and integration options (i.e. does it support Commons HttpClient or Mina?) rather than implementation details.

Upgrading to Spring 3.0

Hi Frank,
thanks for the kind words. Check my latest Spring platform upgrade too: http://blog.newsplore.com/?p=1224

Onwards,
florin

Reviewing Google AppEngine for Java (Part 1)

Transparent bytecode enhancement is a common feature, explicit enhancement is not. With respect to AOP, if you refer to AspectJ, there’s an option to do runtime bytecode enhancement as well as through a static precompilation step. SpringAOP doesn’t require static bytecode enhancement (it uses dynamic proxying via either JDK proxies or CGLIB). But to *mandate* a precompilation step is a restriction of GAE+DN as it complicates the build and deployment.
It’s true, DN supports non-RDBMS stores and I’ve updated the post to reflect that. It’s great to hear that it’s been around from 2003 and it became “very popular”. Somewhere along the way Hibernate showed us all how ORM should be done and it become so “very popular” that it’s been adopted as a standard (after already being the de facto standard).

Evaluating EclipseLink 1.1

You forgot about my remarks re query caching. Putting cache management into the code is backwards and a bad practice.
JPA spec is JSR driven (220 for 1.0 and 317 for 3.0) so it’s not about sharing a standard, it’s about being compliant and EclipseLink will be the JPA 2.0 RI.
Regarding using Tomcat&Spring vs. JEE container there’s a ton of documentation on the internet that will tell you why the former combo is a winner.

florin

Spincloud Labs: Political boundaries overlay in Google maps (Part 2)

Wow, that fast! Glad to hear you put the tutorial to good use. It took me several days to figure it all out.