Imagine you entered a retail outlet to shop that just says OPEN. Now what is your reaction if something suddenly throws you out of the shop No reasons given. And then you find the retail outlet with a sign CLOSED. You will be frustrated wont you? You'd expect that the outlet lets you shop now that you have entered it before the "CLOSED" sign is put up.
Entity EJB sends shiver down my spines, I have to admit. Recently, I had to evaluate Entity EJBs (2.0) for a client of mine. I have had used propretiory Entity EJB extensions to implement persistence in enterpise applications, but the standard and portable Entity EJB of today is still dispappointing and no way a serious candidate.
Imagine a Struts 1.0 world where an ActionForm was absolutely needed even for prototyping an HTML form in JSP using Struts custom tags. Things were good until the separation of concern came into picture. In real life projects, different people play different roles.