Hello,
Howard M. Lewis Ship has commented on
http://tapestry.apache.org/using-tapestry-with-hibernate.html.
You can find the comment here:
http://tapestry.apache.org/using-tapestry-with-hibernate.html#comment_1323
Please note that if the comment contains a hyperlink, it must be approved
before it is shown on the site.
Below is the reply that was posted:
~~~~
Good point; Tapestry does some work to hide the fact that servlet
applications are multi-threaded; the Session object has per-thread scope; it
looks like a global, but is bound to the current thread. The actual per-thread
instance doesn't exist until you start to invoke methods on it ... so don't be
shy about injected it into your components or services.
If you don't commit the transaction, it is discarded/rolled-back. The
@CommitAfter annotation is the easiest way to do this.
~~~~
With regards,
The Apache Tapestry Project.
You are receiving this email because you have subscribed to changes for the
tapestry site.
To stop receiving these emails, unsubscribe from the mailing list that is
providing these notifications.
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
