|
|
Page 1 of 24 articles
|
|
|
|
Implementing an efficient Id generator with Spring framework / Java
Unique identity generators are heavily used in the enterprise applications. Most often applications rely on the database features, such as sequences or auto incremented columns. Unfortunately, that requite extra trips to the database and as a result have impact on performance. The good news that there are few simple optimizations that can be used to significantly reduce this overhead. Let's see how we can use Spring framework to assemble high performance id generator. I'll introduce a basic abstraction for id generator. Note a "granularity" parameter, that will be explained shortly.
|
More fun with Spring scopes / Java
Previous blog about custom scopes has shown an example of the thread-bound scopes (conversations that hold state per thread and live longer then request). This time I would like to show another interesting application for the custom bean scopes. In this case conversation is bound to the page in web application (or even to each unique set of request parameters for that page). Practical examples include per-page caching of the static data (i.e. for Ajax use), allow page visitors to interact or edit page content together and many others... Note that this post should be used as a starting point and may require some additional tweaking for more specific scenarios. Now let's look at the implementation.
|
Introduction to Spring Tutorial
Welcome to the MyEclipse Introduction to Spring tutorial. In this tutorial we are going to cover some of the basic features of the Spring framework, such as dependency injection, and demonstrate using MyEclipse to assist you while developing Spring applications.
|
Hibernate vs. Spring
So. In the previous post, I talked about integration testing. An integration test runs through Webwork, Hibernate and Spring and expects a certain amount of scaffolding to work right.
|
Migrating to Spring
Sure, everyone's been talking up Spring for the last year or so, but what if your app already uses some other framework, or if you didn't even use a framework and instead rolled your own JDBC and DAOs? Ethan McCallum has a case study showing how he took a web application written for another article and converted it to Spring, highlighting what he gained in the process.
|
A Primer on Spring's Data Access Object (DAO) Framework
The business components in J2EE applications typically use the JDBC API to access and change persistent data in relational databases. This often leads to the mixing of persistence code with business logic—a bad idea. The Data Access Object (DAO) design pattern addresses this problem by separating the persistence logic into data access classes.
This article is a primer on DAO design pattern, highlighting its merits and demerits. It then introduces the Spring 2.0 JDBC/DAO framework and demonstrates how it elegantly addresses the drawbacks in traditional DAO design.
|
Exploiting Generics Metadata
It is a common misconception that I hear when talking with clients that all information about generic types is erased from your Java class files. This is entirely untrue. All static generic information is maintained, and only generic information about individual instances is erased. So if I have a class Foo that implements List, then […]
|
Another Reason to Love Spring 2.0: Interceptor Combining
Recently I was working on a project that had a Swing client communicating via RMI to a service layer. The service layer was marked with transactions and everything seemed to work fine. However everytime we'd get an exception at the Hibernate DAO layer, Spring would turn the exception into a runtime exception and it would […]
|
AOP Configuration Choices in Spring 2.0
There are a lot of reasons to love working at Interface21, but by far the best has to be working with the leaders of the industry. For example, one of Spring 2.0's major focus points has been on improving AOP support. We've added a new configuration namespace, the AspectJ pointcut language and support […]
|
Spring Framework: The Origins of a Project and a Name
I am regularly asked about the origin of the name “Spring.”
The name goes back to late 2002. In November 2002, I published Expert One-on-One J2EE Design and Development. The book was accompanied by 30,000 lines of framework code, which had accounted for a good deal of the year full-time I put into writing the […]
|
|
Next>> |