Mailing-List: contact users-help@myfaces.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "MyFaces Discussion" <users@myfaces.apache.org>
Received-SPF: pass (herse.apache.org: domain of gcjmu-myfaces-user@m.gmane.org
 designates 80.91.229.2 as permitted sender)
To: users@myfaces.apache.org
From: Werner Punz <werner.punz@gmail.com>
Subject: Re: Automated transaction handling
Date: Wed, 07 Feb 2007 14:25:43 +0100
Lines: 28
Message-ID: <eqck0o$h6i$1@sea.gmane.org>
References: <e75283b10702070503n1481edd3pffdc0ad5a4fa4f57@mail.gmail.com>
 <eqcitr$cfh$1@sea.gmane.org>
Reply-To: werner.punz@gmail.com
Mime-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
User-Agent: Thunderbird 1.5.0.9 (Windows/20061207)
In-Reply-To: <eqcitr$cfh$1@sea.gmane.org>
Sender: news <news@sea.gmane.org>

Werner Punz schrieb:

>> IMO, such handling would be very convenient to ensure a common and
>> safe exception handling. It would also provide a common place for
>> exception logging.

Ok another pattern, to solve this problem in an automated way.
Use Spring use automated transactions, and also use AOP.
You define beans with business methods under transactional scope
you execute them
the commit rollback is done automated.
in case of an exception add an AOP Layer around those beans
with an interceptor who does the logging.

on the ui layer add a navigation handler to the mix, which pushes in
case of the exception the user into an error page.

This should resolve most use cases without mixing the layers.

You probably get similar results in EJB3 on an app server which supports
AOP.

but things like controlled exception handling recovery/logging with
automated mechanisms probably is really a classical domain for aspect
oriented programming.

I highly recommend to take a short time of reading into the Spring
framework to get more insight and new tools for such usecases.