Regarding hibernate, I'm not sure you could just drop in this module and
remove tapestry-hibernate with no problems. This is because
tapestry-hibernate provides a Session impl that transparently results in
the Session for the active thread. The reason this is useful is because
we can simply inject Session instances into singleton services in our
app modules, without the bother of looking them up through some other
mechanism. Of course there are probably many good reasons to use such an
integration, I just wanted to point out that the tapestry-hibernate
provided Session implementation does a little magic that may cause
breakage if replaced (it would in my apps anyway).
chris
Igor Drobiazko wrote:
On Jan 21, 2008 4:00 AM, Angelo Chen <[EMAIL PROTECTED]> wrote:
Hi,
Good news, a few questions:
1) Any tutorials on using Seam with T5? I tried Seam, up to the point of
booking example, stop when i know I have to learn something about JSF. A
'hello world' tutorial with T5 will be helpful.
You can find a simple demo here:
http://tacos.svn.sourceforge.net/viewvc/tacos/tacos-5/trunk/tacos-seam/demo/
2) if an app uses Seam, do we still need Tapestry-hibernate?
If you decide to use Seam and Tapestry together, you probably don't need the
module tapestry-hibernate.
You just need to configure hibernate and then you can inject the Session as
any other Seam component.
Well, this is what I'm going to do next. You can expect some Hibernate
examples in the next days.
Thanks,
A.C.
Igor Drobiazko wrote:
Hi all,
Seam integration with Tapestry 5 is available in Tacos 5.
http://tacos.sourceforge.net/tacos5/tacos-seam/index.html
--
Best regards,
Igor Drobiazko
--
View this message in context:
http://www.nabble.com/-ANN-%3A-Seam-for-T5-tp14988484p14990396.html
Sent from the Tapestry - User mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
