Hi Geoff, thanks for the response, Geoff Callender wrote: > Do any of these problems exist if you get a session bean to do the > work for you? > > For example, a page to edit the user, using a session bean called > OrderService and an entity bean (using Hibernate if you like, as I > do) called Order. [...] > No threading issues to worry about. Isn't this simpler than roll- > your-own?
You'll have to forgive my ignorance, I'm still rather a newbie when it comes to Java web apps. I'm afraid I'm not familiar with what a Session Bean is as a proper term (if that is the way you are using it). Some Googling shows me that it appears to be an EJB concept. This is my first real Java application, and I'm trying to keep it as simple as possible, so I haven't yet gotten into JEE, EJB, etc. I'm just doing a plain servlet on Tomcat. Can you tell me what is is about session beans that avoids my problem, or give me some pointers to documentation? If I place a detached object in the session bean, how is this any different from placing it in the HttpSession? Isn't it still possible that two concurrent threads will be given that same detached object? What am I missing? Thanks. ;) --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
