I can't imagine how this can be easier, I'm very anxious to see!
T5.1 will be a huge release, and I'm sure it's new functionalities
will bring more users to this community.
On Mon, Feb 2, 2009 at 5:04 PM, Howard Lewis Ship wrote:
> It's even easier in Tapestry 5.1., as you can advise a service (
It's even easier in Tapestry 5.1., as you can advise a service (or set
of services), rather than decorate.
On Mon, Feb 2, 2009 at 9:48 AM, Marcelo Lotif wrote:
> Thanks Howard! It works beautifully!
>
> Just a note: I couldn't add this functionality directly to the dispatcher.
> I've added it to
Thanks Howard! It works beautifully!
Just a note: I couldn't add this functionality directly to the dispatcher.
I've added it to the DAO instead. BTW, this is not a bad practice at all.
Thank you!
On Mon, Feb 2, 2009 at 1:12 PM, Howard Lewis Ship wrote:
> See the documentation:
>
> http://tape
See the documentation:
http://tapestry.apache.org/tapestry5/tapestry-hibernate/userguide.html
for how to decorate your service to enable @CommitAfter.
On Mon, Feb 2, 2009 at 8:06 AM, Massimo Lusetti wrote:
> On Mon, Feb 2, 2009 at 4:03 PM, Marcelo Lotif wrote:
>
>> But when we try to persist t
On Mon, Feb 2, 2009 at 4:03 PM, Marcelo Lotif wrote:
> But when we try to persist the entity into the DB, it fails because the
> annotation @CommitAfter has no effect here (I suppose). I tried to start and
> commit a transaction manually and it did well, but when tapestry-hibernate
> tried to do
