Sometimes we may want to apply multiple aspects to the same pointcut when using Spring AOP, keeping each aspect responsible for a single activity or concern. Below we'll discuss a business example of why we may want to order more than one aspects and how to ensure that ordering using Spring. Again, we'll be writing our code in Groovy to keep things simple.
To start our example, let's say we have a service method that takes a Purchase and returns a Shipment:
interface PurchaseProcessor {
Shipment process(Purchase)
}
Our first use of AOP may be recording some information about the Purchase for statistics purpose. Since statistics keeping is a separate concern from actually processing the Purchase, it serves as a perfect candidate for an aspect. For the purposes of this example, we will use an aspect that provides around advice instead of an alternative like before advice:
class StatRecordingAspect {
StatRecorder statRecorder
Object around(ProceedingJoinPoint joinPoint) {
Purchase purchase = joinPoint.args[0]
statRecorder.record purchase
joinPoint.proceed()
}
}
Later on, we decide we want to inform an internal process via JMS when the processed Shipment is on its way out the door. As the sending of the information could be considered another concern separate from the actual processing of the Purchase we decide it to should be done in an aspect. Additionally, this notification requires information from the statistics from the Purchase:
class NotificationAspect {
JmsShipmentNotifier notifier
StatRecorder statRecorder
Object around(ProceedingJoinPoint joinPoint) {
Purchase purchase = joinPoint.args[0]
Shipment shipment = (Shipment)joinPoint.proceed()
notifier.notifyAbout shipment, statRecord.statsFor(purchase)
shipment
}
}
The above business case requires that the stats about the Purchase be recorded before the notification. If we target both aspects at the PurchaseProcessor method via the same pointcut, how do we guarantee that the stats are recorded first?
We could opt to combine the two aspects into one, but it could be argued then the combined aspect would have one more than responsibility, record stats and sending out notifications, and have more than one concern.
A solution provided by Spring AOP is to have each aspect implement the Ordered interface provided by spring-core (Spring also provides an @Order annotation as an alternative to implemented the Ordered interface.):
class StatRecordingAspect implements Ordered { //...
Object around(ProceedingJoinPoint joinPoint) { //... }
@Override
int getOrder() {
0
}
}
class NotificationAspect implements Ordered { //...
Object around(ProceedingJoinPoint joinPoint) { //... }
@Override
int getOrder() {
1
}
}
With the above implementations, the StatRecordingAspect would be executed first as it is the aspect with the lowest order.
If the above makes you a little uneasy because the values returned are not linked to each other in any way, the values seem arbitrary, you could relate the orders to each other with an enumeration:
enum AspectOrder {
STAT_RECORDING(0),
NOTIFICATION(1)
final int value
AspectOrder(int value) {
this.value = value
}
int value() {
value
}
}
class StatRecordingAspect implements Ordered { //...
Object around(ProceedingJoinPoint joinPoint) { //... }
@Override
int getOrder() {
AspectOrder.STAT_RECORDING.value
}
}
class NotificationAspect implements Ordered { //...
Object around(ProceedingJoinPoint joinPoint) { //... }
@Override
int getOrder() {
AspectOrder.NOTIFICATION.value
}
}
Now in your unit tests you can compare the order value of one aspect to the others when testing the getOrder() method, ensuring they would in practice be ordered as you would expect.
