> The only reason I still use it is the transaction management. Having time to
> implement something similar in Tapestry-IoC is in my wishlist
> (tapestry-hibernate and @CommitAfter are not enough, as they're tied to
> Hibernate), but I don't know when Santa will give me that . . .
Yes.. transacti
On Tue, Dec 15, 2009 at 1:30 PM, Kalle Korhonen
wrote:
> It's nice you mention Tynamo even though I've been rather careful
> *not* to talk about it here yet before we have our house fully in
> order. Tapestry is the enabling technology for both Tynamo and
Somebody already asked - the project site
Em Tue, 15 Dec 2009 19:30:41 -0200, Kalle Korhonen
escreveu:
to use and integrate on their so from my perspective, Spring is just
another layer of indirection that I'm campaigning to remove (and I say
that having used Spring extensively for years in multiple projects).
I agree completely. T
On Tue, Dec 15, 2009 at 1:40 AM, Alessandro Bottoni
wrote:
> Il 15/12/2009 06:43, Kalle Korhonen ha scritto:
>> Most of the Java applications today are way over-engineered for their
>> purpose - while RoR and php folks are running circles around us.
> That's true. And that brings me to another, st
Il 15/12/2009 06:43, Kalle Korhonen ha scritto:
> Most of the Java applications today are way over-engineered for their
> purpose - while RoR and php folks are running circles around us.
That's true. And that brings me to another, strictly related topic: the
learning curve of Tapestry 5.
On the N
