1) http://www.jboss.com/products/seam/exceptions-1.1.dtd
Its also in the Seam jar. 2) The negative consequence is that you can have multiple objects from the same persistent identity, for the same conversation. In Seam 1.1, Seam-managed persistence contexts are very efficient in a clustered environment, and I strongly recommend them. 3) Of course there is always per-request state. The diff b/w a SFSB and an SLSB is that an SLSB does not hold state between *method calls*. Which means that they can never be used as a backing bean for a JSF form, among other things. 4) anonymous wrote : What are best practices or suggestions regarding what to bind fields in the webpage to - session beans or entities? The best practice is to use a stateful session bean or an entity bean. Depends upon whether the form data is to be persistent or not. The Seam registration example does it exactly right. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3994134#3994134 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3994134 _______________________________________________ jboss-user mailing list [email protected] https://lists.jboss.org/mailman/listinfo/jboss-user
