Marius Kotsbak wrote: > ... > But jsp should NEVER (i think) call entity beans directly! If you do, > you get one transaction per call (if not turned off), and this creates > no good transactions either. Let the jsp call a session bean that does > the work (and much less calls between the session-bean and jsp, i.e. > large methods like "order", registerPerson etc.). > ...
I also agree that jsp's should never call entity beans directly, however you should be able to share one transaction for all calls by looking up java:comp/UserTransaction from your front-end controller serlvet (if you have one that dispatches to your jsp's), and beginning and committing (thus wrapping) all work done between it. Of course, this means your Entities should be marked as TX Required, Mandatory or Supports so that the already begun TX will be used by all. Using local interfaces on your Entities would be good too, but even if you use remote interfaces, I think if all your code is in the same jvm jboss should know to do pass-by-reference instead of pass-by-value (and you shouldn't ever get RemoteExceptions). David _______________________________________________________________ Don't miss the 2002 Sprint PCS Application Developer's Conference August 25-28 in Las Vegas -- http://devcon.sprintpcs.com/adp/index.cfm _______________________________________________ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user
