Em Thu, 20 Nov 2008 14:14:59 -0300, Howard Lewis Ship <[EMAIL PROTECTED]>
escreveu:
I think Tapestry makes it easier to separate your business logic out
as IoC services or even Spring beans. It's easier to inject a service
or bean in Tapestry than in any framework I'm aware of.
I completely agree.
My of the examples, demos or prototypes do intentionally blur the layers
a bit,
but you are anything but trapped in that simple, flat model.
As far as I know, I cannot put the @CommitAfter method in one IoC service
and have its calls wrapped in a transaction, just components and pages
methods. If I'm wrong, I'll use Tapestry-Hibernate. If not, I'm still
waiting to have time to write Tapestry-Transaction. :) And I wouldn't even
need much time, as Tapestry IoC aspect-oriented support is amazingly
simple and powerful. ;)
--
Thiago H. de Paula Figueiredo
Independent Java consultant, developer, and instructor
http://www.arsmachina.com.br/thiago
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
