Suggesting to improve EJB: move local and stateless to another spec…

I refer to my previous post (http://www.siriusict.com/2009/03/15/ejbs-memoirs-proud-and-sorry-for-my-mistakes/) in which I felt quit uncomfortable about my life, the life of an EJB. I think I found a solution to the pain I feel and the problems I gave others; others in this case means people trying to understand and grasp me. I’m especially referring the younger generation, the people that don’t know my past, my origin, my intent, my raison d’être; my childhood as a solution for distributed computing. I’m the proud offspring of CORBA 3, my young brother (CORBA components) died (my CORBA parents were only 3).

I have found a solution, a way of securing my life (for the time being). I know my days are numbered. Distributed computing will soon be a thing of the past; it will leave this software dimension and world if IT architects and developers and enter into the world of virtualisation, IT operations and infrastructure. Scalability and availability will soon be in their hands!

But yes I found a solution that will, for the time in which scalability/availability remains in the hands of IT architects and developers, prolong my life.

I, EJB, have been abused and misused. I therefore suggest the following changes to my essence, my core.

Do the following and people will understand me better, use me better and will my role in this world clearer.

As I told you in my previous post: the local aspect of me was introduced due to my bad brothers “Entity Beans”. They gave me most of the trouble I have today; the aspect introduced for them in this family makes it difficult to explain my essence. My Entity Beans brothers have died, making space for another distant relative called Entities (keep in mind these are distant relatives, coming from my mother’s site called Persistence and her grand-grand-father called Rudolph David Bradford-Macon Salerno)

The following should be done:

• My Local business interface should be removed together with my statefullness

• My new brother Entites should leave the family of EJB

• I will remain: a Stateless Session Bean with a remote client view

This will give honer to my families name of Enterprise Java Beans; I will guard the enterprise gate: I will be remote, I will be stateless, I will give life to distributed components, I will fulfil my life’s goal (helping those that enter the world of distributed computing!)

Move:

• My local business interface and statefullness to a new family, a new family only intended to work in the country, in the context of Web Applications.

• Perhaps it can join or even become a WebBean.

In the web let the local client views and statefulness of session beans be the only option, or better let it depend on the chosen scope: whether it be page, request, session, conversation or application. Let their life florish in the world of Java Web Applications (of which its importance in dynamic web applications is getting less and less )

Let me enjoy the rest of my days; let the Stateless Remove Session Bean be the only member of the EJB family together with my foreign stepsister, Message Driven bean.

The EJB family bears the name Enterprise, this can only be honered by me: a stateless remote session bean. I will do so with strength and pride, until virtualisation will make me obsolete.

Bottom line:

• Let EJBs only contain Stateless Remote Session Beans and Message Driven Beans

• Let local stateless Session Beans blend with WebBeans

• Let Entities start its own family in Java SE and get out of Java EE

• Like that I understand my role and make things clear…