Great write-up ...
now if there was only a more 'CoC' mechanism, say
static transactional = [ calculatePrice: [readOnly: false,
propagation:Propagation.MANDATORY,
noRollbackFor:[RuntimeException.class]], methodX: [ ... ] ]
with some default values used for:
static transactional = [ 'calculatePrice', 'methodX' ]
and
def calculatorService
would just have to be set to the proxy...
just a suggesion.
-----Original Message-----
From:
[hidden email] [mailto:
[hidden email]] On Behalf
Of Graeme Rocher
Sent: Friday, January 18, 2008 2:45 PM
To:
[hidden email]
Subject: Re: [grails-user] Fine-grained transaction configuration
Wow, thanks for the detailed write-up Vaclav, I'll update the user guide
Cheers
On Jan 18, 2008 7:35 PM, Vaclav Pech <
[hidden email]> wrote:
>
> Hello Graeme,
>
> of course, here we go with the transaction configuration details. I
> decided to first explain a bit on what needs to be done to make the
> configuration actually work. I've started with Grails just recently,
> so I might have misunderstood something. Don't hesitate to tell me
> where I'm wrong and feel free to ask for more details, if needed.
>
> Fine-grained transaction configuration
>
> If the default transactional settings in Grails are not appropriate
> for a particular project or a part of it, developers can resort to the
> Spring way to configure transactions. This only affects the beans,
> which the default Grails behavior is not appropriate for. There are
> basically two ways to configure transactions on a finer granularity
> level. Let's assume we have a controller named CalculatorService with
a couple of calculation methods.
>
> class CalculatorService {
> static transactional = true
> public BigDecimal calculatePrice() {
> ...
> }
> }
>
> We need to make several minor changes before we can set transactional
> attributes.
>
> 1. As we will be creating transactional proxies around our service,
> we need an interface through which other services or controllers refer
> to our CalculatorService. So the first change is to extract an
> interface, named Calculator out of the CalculatorService and change
> type of all existing statically typed references from other beans to
> our CalculatorService to be of Calculator type.
>
> class CalculatorService implements Calculator { ...
> }
>
> 2. The next important step is to set the transactional attribute on
> the service to false, otherwise our transactional proxies will collide
> with the default Grails transaction configuration..
>
> static transactional = false
>
> 3. We also need to put the "aspectjweaver.jar" file from Spring
> distribution to the <project>/lib folder to enable aspectJ AOP in the
> project
>
> 4. Now we can start setting transaction attributes. There are two
> options to achieve this. We can configure transactions either using
> <tx:advice/> in the resources.xml file or using the @Transactional
> annotation directly in the Groovy or Java service code.
>
> Using <tx:advice/> to configure transactions from within
> resources.xml
>
> We need to define a transactional advice <tx:advice/>, which
> configures transaction attributes for methods and associate it with a
> pointcut using an advisor. This is nicely described in Spring
> documentation at
n.html#transaction-declarative.
> at
http://static.springframework.org/spring/docs/2.0.x/reference/transaction.html#transaction-declarative-annotations.
> Notice the minor change in syntax for the rollbackFor and
> noRollbackFor attribute list values when using annotations in Groovy
> in contrast with Java. The specifics of annotations in Groovy are
> described at
http://groovy.codehaus.org/Annotations+with+Groovy.
>
> class CalculatorService implements Calculator {
> static transactional = false
>
> @Transactional(readOnly = false, propagation =
> Propagation.MANDATORY,
> noRollbackFor=[RuntimeException.class])
> public BigDecimal calculatePrice() {
> ...
> }
> }
>
> The resources.xml file must be updated a bit, too, to enable
> evaluation of the transactional annotations and creating transactional
> To unsubscribe from this list please visit:
>
http://xircles.codehaus.org/manage_email--
Graeme Rocher
Grails Project Lead
G2One, Inc. Chief Technology Officer
http://www.g2one.com---------------------------------------------------------------------
To unsubscribe from this list please visit:
http://xircles.codehaus.org/manage_email---------------------------------------------------------------------
To unsubscribe from this list please visit:
http://xircles.codehaus.org/manage_email
Locked
