InfoQ Homepage Spring Content on InfoQ
-
WebLogic Real Time 1.1 Provides < 30 ms latency
BEA has released WebLogic Real Time (WLRT) Core Edition 1.1 today, their product intended to bring Java into what has traditionally the realm of C/C++ apps. Real Time claims to have 20 millisecond average latencies and 30-millisecond maximum latency on its own benchmark application. BEA is recommending Spring as the programming model for Real Time.
-
Interview: Patrick Lightbody on Project Able - A Complete Java Web Stack
WebWork committer, Patrick Lightbody, has announced Project Able: a complete Java web stack. InfoQ sat down with Patrick to discuss the philosophy behind Project Able.
-
Debates flare on the right level of abstraction over ORM and JDBC
A heated debate started a few weeks ago initiated by members of the Hibernate team, arguing that using an abstraction framework on top of an ORM is a bad idea, citing Spring's HibernateTemplate as a specific example. Along the theme of levels of abstraction, Brian McCalister also surveyed various convenience frameworks over JDBC.
-
InfoQ Article: Simplifying Enterprise Apps with Spring 2 and AspectJ
Adrian Colyer, AspectJ lead and Chief Scientist at Interface21 has contributed an excellent article which shows how to use Spring 2's new AspectJ integration features followed by a roadmap for the adoption of Aspect Oriented Programming on an enterprise project, with lots of specific examples of how and where to apply Aspects.
-
Tackling Misconceptions About Spring
Spring has transitioned from a bleeding edge project to widely used component of enterprise applications written in Java today. As with any popular project misconceptions start to arise. Steve Anglin recently blogged on oreillynet.com about 10 common misconceptions developers have about Spring.
-
Is Java EE 5 lightweight enough?
An article yesterday asked if Java's complexity is its worst enemy, quoting Richard Monson-Haefel saying "They should retire Java EE and work with the open source community to come up with a better solution. Steve Anglin distilled the the problem to a simpler question: "Is the new lightweight Java EE 5 light enough?
-
InfoQ Book Review: Agile Java Development with Spring, Hibernate and Eclipse
Matt Morton asked the question "Can Java be as Agile as the Dynamics (Ruby, Python, Groovy)?" and went to Anil Hemrajani's book to find out. He found a readable, useful book, and helps idenfity the right audience for this book.
-
First Spring 2.0 Release Candidate is Out
The first release candidate for Spring 2.0 has been released. Spring 2.0 is a major new release, some of the notable enhancements include simplified configuration, AspectJ annotation support, EJB JPA support, a task executor framework and asychronous pojo's, convention-based Spring MVC update, and more. The new Spring PetClinic showing Spring+JPA is also included.
-
Book: Java Transaction Design Strategies Published
InfoQ's first book, Java Transaction Design Strategies has been published! The book is available for free download and the published print version is available for $22.95. Written by IBM architect and nofluff speaker Mark Richards, the book is one of the very few works on transactions, and definitely one of the most practical.
-
Acegi Security System for Spring 1.0 is out
Acegi Security 1.0 has just been released, after more than two and a half years of use in large production software projects, 70,000+ downloads and hundreds of community contributions. The Acegi framework is particularly useful with Spring, it offers authentication, authorization, instance-based access control, channel security and human user detection capabilities.
-
Pitchfork: EJB 3 Interception & Injection to WebLogic using Spring
Spring 2.0 is now being used by BEA to provide EJB 3 dependency injection and interception, the result of Pitchfork, a new Spring add-on project by BEA and Interface21 that allows Spring to provide JSR 250 dependency injection and EJB style interception. WebLogic users can also use additional Spring features over the EJB spec, and Pitchfork may be used by other Java EE servers in the future.