lasitha wrote:
However, your post brings up an interesting question: will the
object's state be persisted even after validation fails? My first
Seems obvious that a transaction should be wrapped around the form
validation (or around the whole request) which would rollback in case of
valdation errors.
The question is - how to do it? Better yet, how to do it without
boilerplate code all around?
tapestry-ioc allows you to write interceptors on service method calls. I
don't think it allows you to write such interceptors around components
and pages.
I remember that one of the good things you'd get when you'd combine
struts 1 and spring was that allowing spring to create your actions you
had full control over when and where transactions started and ended.
I think that it might be a drawback that tapestry 5 does not allow you
to use the IoC containers AOP facilities on components and pages.
Ognen
P.S. In my Eclipse-RCP project I also use JSF's approach: values are
kept in the controls (field components) until the form is submitted (ok
pressed).
--
Ognen Ivanovski | [EMAIL PROTECTED]
phone +389 -2- 30 64 532 | fax +389 -2- 30 79 495
Netcetera | 1000 Skopje | Macedonia | http://netcetera.com.mk
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
