Martin Marinschek wrote: > People were saying that Seam gets rid of a layer that was actually > said to be necessary the last years. > Well given the seam demo, yes, the demo basically meshes the ui and db layers together.
Not necessarily a bad thing for small apps where BO/DAO is overkill. But it does not really mean that you cannot use those layers. It is just that the ui layer is also pushed into the EJB session bean domain. But as soon as you hit a certain size it is pretty obvious that you start to divied the application concerns into separate domains. > Plus obviously the EJB EG had doubts that the annotation support was > properly aligned with what EJB 3.0 has to offer. > Understandable because EJB never was intended for view logic bookkeeping nevertheless the Seam approach eases things tremendously.
