1.service method returns a value no abnormalities + XML +
***************************************
1. Before advice deleteUser ...
2. Around advice ... open affairs ... deleteUser
delete a user by the above mentioned id
3. after returning advice ... deleteUser
returns: 1
4. Around advice .... commit the transaction ...
the final notice ... deleteUser
*** ***********************************
2.service method returns a value + + No abnormality annotations
**************************************
2. Around advice ... open affairs ... deleteUser
1. pre-notification ... deleteUser
delete user ID
4. surrounds notification committing the transaction .... ...
final notification deleteUser ...
3. ... rear notification deleteUser
return value: 1
**** **********************************
3.service method does not return a value no abnormalities + XML +
***************************************
1. Before advice deleteUser ...
2. Around advice ... open affairs ... deleteUser
delete users. . . .
3. Rear notice ... deleteUser
Return Value: null
4. Surround notification committing the transaction .... ...
final notification deleteUser ...
****************** *********************
The method does not return value 4.service + + No abnormality annotations
****************************************
2. ... turn around advice affairs. ..deleteUser
1. Before advice ... deleteUser
delete users. . . .
4. Around advice .... ... commit the transaction
the final notification deleteUser ...
3. ... Rear notification deleteUser
Return Value: null
***************************************
In fact little effect, as long as the large preposterous situation does not appear on the list, the big difference is that the post-notification and the final notification, the problem is the release of resources has;