When to use SessionBeans and when Pojos?

[hexxter]

Hi,

I'm trying to get into seam and by now I thing I'm starting to understand the JSF side code. Buts whats totally unclear to me:

For actions and supporting code I have to use some sort of whats called in JSF BackingBeans. No I do understand that I have to (do I?) use @Stateful SB for beans which store data and @Stateless for beans which don't. What I don't understand is:

When can I use Pojos? Only if I need @PersistenceContext injected? And whats going on at the server? Where is my code executed? Does it make any difference when running in a distributed environment?

Thanks,

Florian

[hexxter]

one more thing:

when do I have to specify a @Local and a @Remote interface? Is @Remote usefull in seam context anyways? As I understand it seam can use objects even without these interfaces.

more thanks,

Florian

[alexg79]

You only have to use @Remote when you plan to make the session bean available to clients outside the container JVM (for a client application).

There are a number of advantages to using EJB3 session beans instead of POJOs.
SFSB replication across the cluster is handled by the container, as is persistence context injection and transaction demarcation.
As I recall, the Seam documentation says that SFSB replication across the cluster is more efficient than that of Seam POJO components.

[wise_guybg]

Yesterday I was about to create a similar thread when I found this:
http://docs.jboss.org/seam/2.0.0.B1/reference/en/html/concepts.html

It doesn't explain all the details but is a good guide.