>
>
> 4. Using MDB everywhere
> MDBs should not be reserved for application servers. We should have
> "message-driven POJOs" as seen in Spring JMS, by using annotations on a
> simple Java object.
>
>
> But you will need some kind of a container. IMHO it doesn't matter whether
> I'm using Spring or Weld or OSGi based EJB container. It won't work with
> Java SE...
>
>
It can work with plain Java SE, we don't need a container for that. Last
week, I've seen a project which has done its own implementation, which is a
simple thread that polls for messages every second. It could be turned on
and off, etc...
Spring JMS does exactly the same thing (it's more advanced as you plug in a
thread pool, etc, but it's the same idea). I've seen a lot of Spring Batch,
Spring Integration, and Tomcat-based projects use it.
A simple use case such as receiving messages should be available for
everyone, even if they just use plain Java SE. Of course, for more complex
use cases we could require Java EE.
>
> 5. Clustering and failover
> As the theme of JEE 7 is "the cloud", there should be some
> clustering/failover facilities in the specification.
> For instance, we should be able to configure failover as in ActiveMQ from
> the standard configuration:
> http://activemq.apache.org/failover-transport-reference.html
>
>
> So far I know clustering is not specified in other specifications. (except
> distributable in web.xml). But probably we could introduce the notion of
> clustering in Java EE 7 in general.
>
I fully agree. Clustering is a wider subject, and should be adressed at the
Java EE 7 level. I'm a bit confused here: as far as I understand, "the
cloud" is a main theme of Java EE 7, but nobody seems to be working on it...
--
Julien Dubois
Twitter: @juliendubois <http://twitter.com/#!/juliendubois>