InfoQ

News

What Should be In JEE 6? Gavin King's Wish List

Posted by Scott Delap on Apr 02, 2007 11:33 PM

Community
Java
Topics
Enterprise Architecture,
JCP Standards
Tags
Java EE
Gavin King, Hibernate creator and Seam project lead, has posted the first of a series of posts containing his wish-list of features for JEE 6. The first item on Gavin's list is more concurrency modes for stateless and stateful session beans. He proposes three options:
  • No concurrency, the default, and currently supported behavior: the bean does not support concurrent clients. The container is permitted to throw a ConcurrentAccessException if two requests arrive simultaneously.
  • Bean-managed concurrency: the bean supports concurrent access by multiple threads, and is responsible for managing access to volatile data structures.
  • Container-managed concurrency: the bean supports concurrent clients, and the container is responsible for ensuring that concurrent threads are serialized before entering the bean implementation.

The second item Gavin proposes is Lightweight asynchronicity. He argues that the current options of JMS and EJB timers are not enough. In addition he advocates more than one @Timeout method per bean and enhanced scheduling options. The third item mentioned is stateful web service endpoints:

...Currently, only stateless session beans may function as web service endpoints. With some integration with WS-Contexts or WS-Addessing (or whatever WS-blahblah is appropriate), we would be able to support a stateful session bean that acts as a web service endpoint. I don't know exactly what this would look like yet, but we are trialing some stuff in Seam/WS that is probably relevant...

Gavin rounds out his wish-list with an optional business interface for EJB's, Simplified JMS/JavaMail, Enhanced Logging injection, EJB meta-annotations. He argues in respect to an optional business interface:

Currently, EJB mandates that all session beans have some @Local or @Remote interface. This was not an unreasonable requirement when session beans were understood to exist in a business tier, with a well-defined API sitting between the business logic and the client. ... Especially in an environment like Seam, where the only client of a bean might be a JSF page with EL expressions, the interface looks totally redundant! ... The interface should be optional, and when it is missing, the public methods of the bean class should be taken as the business methods of the session bean...

6 comments

Reply

Servlet API enhancements by Sean Sullivan Posted Apr 3, 2007 9:46 AM
nice by Friszart Shaucle Posted Apr 3, 2007 9:08 PM
Sounds like a wishlist to make JBoss Seam a Java EE 6 standard by O Z Posted Apr 3, 2007 11:47 PM
Re: Sounds like a wishlist to make JBoss Seam a Java EE 6 standard by Emmanuel Bernard Posted Apr 9, 2007 8:53 AM
Re: Sounds like a wishlist to make JBoss Seam a Java EE 6 standard by Gavin King Posted Apr 12, 2007 7:38 PM
Re: Sounds like a wishlist to make JBoss Seam a Java EE 6 standard by berkay NiQuiL Posted Jun 30, 2008 3:48 PM
  1. Back to top

    Servlet API enhancements

    Apr 3, 2007 9:46 AM by Sean Sullivan

    Howard Lewis Ship and others have suggested improvements to the Servlet API: http://tapestryjava.blogspot.com/2004/12/servlet-mapping-limitations.html http://tapestryjava.blogspot.com/2006/01/servlet-25-wheres-regexp.html http://weblogs.java.net/blog/gmurray71/archive/2005/07/got_servlets.html http://www.bileblog.org/?p=226

  2. Back to top

    nice

    Apr 3, 2007 9:08 PM by Friszart Shaucle

    Gavin is always insighted.

  3. Some quotes from Gavin's original post: A lot of these items have come out of our experience with Seam... Especially in an environment like Seam, where the only client of a bean might be a JSF page with EL expressions, the interface looks totally redundant! Currently, it is possible to inject a Topic or Queue using @Resource, but of course what I'm really interested in is QueueSender or TopicPublisher. This is easy to fix - indeed, we already fixed it in Seam. (Just like it is in Seam.) For example, you might have several Seam components with the following annotations: ...

  4. Yes, we hope Web Beans JSR-299 (inspired from JBoss Seam) will be included into Java EE 6, and to do that a few other spec has to be tuned up. Nothing wrong with that :-)

  5. "Sounds like a wishlist to make JBoss Seam a Java EE 6 standard" Actually the main effort to introduce (some of) the ideas in Seam into the EE 6 spec is the Web Beans spec (JSR-299). We are working in close collaboration with Sun, Google, Oracle, Apache and others on this effort. The spec will be influenced by Seam, Guice, Shale, ADF and anything else we happen to find interesting :-) The things I'm talking about in these posts are stuff that is useful and interesting even if you don't use Web Beans. Cheers

Exclusive Content

Rationalizing the Presentation Tier

Thin client paradigm characterized by web applications is a kludge that needs to be repudiated. Old compromises are no longer needed and it's time to move the presentation tier to where it belongs.

Agile Project Management: Lessons Learned at Google

In this presentation filmed during QCon 2007, Jeff Sutherland, the creator of Scrum, talks about his visit at Google to do an analysis of Google's first implementation of Scrum.

AtomServer – The Power of Publishing for Data Distribution

In this article, Bryon Jacob and Chris Berry introduce AtomServer, their implementation of a full-fledged Atom Store based on Apache Abdera, which is now available as open source.

An Introduction to Virtualization

It is easy to think that virtualization applies only to servers. In reality the recent resurgence of the concept is also being applied to networking, storage, and application infrastructure.

REST Anti-Patterns

In this article, Stefan Tilkov explains some of the most common anti-patterns found in applications that claim to follow a "RESTful" design and suggests ways to avoid them.

Choosing between Routing and Orchestration in an ESB

In this article, Adrien Louis and Marc Dutoo discuss the differences and relative merits of using orchestration vs. routing in a typical ESB setup, and discuss various implementation options.

Enterprise Batch Processing with Spring

Wayne Lund discusses batch processing, Spring Batch objectives and features, scenarios for usage, Spring Batch architecture, scaling, example code, failures and retrying, and the future roadmap.

User Story Estimation Techniques

Developer Jay Fields draws on his experiences as a ThoughtWorks consultant to describe effective user story estimation techniques.