Seam without EJB, AKA Seam with JavaBeans, why bother?

[grettke_spdr]

Seam without EJB, AKA Seam with JavaBeans, why bother?

The documentations suggests that you ought to use EJB because Seam was designed to run with EJB, but if you can't, you should go ahead and use JavaBeans.

Is this just marketing's take on Seam or what?

The reference manual talks about using JavaBeans and there are examples, so is using JavaBeans a good idea or what? What is the stance on this?

[christian.bauer]

Yes, it's all marketing.

Seriously though, you use whatever works for you. If you don't need EJBs, use JavaBeans. If you need EJBs, use them. Isn't it nice that both component types work with Seam?

[stu2]

Looks to me like the biggest losses when not using EJB are the conversational stuff around SFSB and the JMS tie-ins. Neither are essential though. Seam without this stuff is very much intact.

[christian.bauer]

Asynchronous processing also requires EJB (timers).

[christian.bauer]

Oh, and of course you definitely want EJBs if you have to run your conversations in a cluster, because SFSBs provide all the necessary machinery for replication of state.

[gavin.king]

Actually Seam JavaBean components are reasonably efficient in a cluster. We have built some optimized stuff on top of HttpSession replication.