On Mon, 02 Sep 2013 18:01:06 -0300, Boris Horvat
<horvat.z.bo...@gmail.com> wrote:
Hi Thiago,
Hi!
sorry for continuing this thread but I was wondering is it possible to
somehow provide some automated ways in tapestry to reattach the session.
Just use Session.merge() before using an entity. Or create a session
persistence strategy that does the merge (reattaching) automatically if
that doesn't exist already. Handling this exception and somehow merge the
entity and going ahead as if the exception didn't happen, AFAIK, is
impossible due to the way Java and other languages work. Unless you're
thinking of restarting the request handling, something IMHO is too ugly of
an hack instead of doing the right thing (merging the object into the
session in some way or another).
Something like handle uncaught exceptions in normal applications.
What do you mean by normal applications?
If there is such an event I guess it should be possible to somehow have
this
automated, no?
Catching the exception is easy, trying to do something beyond reporting
and logging it it's the hardest part by far.
--
Thiago H. de Paula Figueiredo
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
For additional commands, e-mail: users-h...@tapestry.apache.org
