java - AspectJ vs. Spring AOP vs. JBoss AOP for exception handling -
I'm writing a webservice in an external system.
Many of my service wrapper class can throw an exception call to those methods which call all soap interfaces of the webservice, which again trigger yourself to connect to the webservice.
To handle that scenario, I would like to use AOP as if all the methods that call the SOAP interface are "wrapped", an attempt / hold block is reconnected in the catch block.
I am not using spring at this time, so I am thinking of introducing the JBoss AOP. I would like some advice if the Aspen or Spring AOP is a better option.
Thank you.
Your requirements are very basic, so either Espex, Zebaus AOP or Spring AOP will work for you. . It suggests that going with the simplest option will be the best thing to do.
- I believe that using AspectJ byte-code manipulation, either compile-time or load-time, (depending on your setup) is either simple or nightmare It's very flexible what you can do, but be a little scary.
- Spring AOP is limited (which are your problems, so there is no problem here), but it is completely run-time solution. Its lack of flexibility can be a bonus here, because it is easy to understand
- I'm not very familiar with the Jaboss AOP, but it is closer to Spring AOP than the EspecZ JP.
Comments
Post a Comment