"[EMAIL PROTECTED]" wrote : This is scope to the request scope by default - so
it is stateful across the request but its *not* conversational.
|
| @Name("pojo")
| | class Pojo {}
Wait, I thought conversation scope was the default scope? It is for SFSBs,
right? If I annotate my bean with @Name @Stateful, I get a conversation-scoped
bean. If I put just @Name, it's a POJO, and you're saying it's request scoped?
This still doesn't fully answer the question. Most things can be done with
POJOs. For example most beans aren't message-driven. For many simple things
there is no performance benefit to clustering beans. So, should we be using
EJBs or POJOs? POJOs have a benefit of simplicity: no need to write an
interface.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4122961#4122961
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4122961
_______________________________________________
jboss-user mailing list
[email protected]
https://lists.jboss.org/mailman/listinfo/jboss-user
