Is implementing the Abstract Factory pattern for a spring-based project with AOP should be any different than in a normal project?
A:
Without a more concrete example, I'd have to say "no". Spring AOP is pretty good at working around your code, whatever structure it's in.
skaffman
2009-10-20 22:15:04
+1
A:
It should be simpler, all things considered; technically, Spring acts like an Abstract Factory itself, and that pattern deeply informs most things that Spring "wants" you to do with it.
McWafflestix
2009-10-20 22:28:11
This is not quite correct. Spring will not add aspects to beans that it doesn't create, so creating a factory in spring and then using the factory to create things you want to be affected by aspects will fail (assuming you're using the simple spring AOP instead of AspectJ)
Jherico
2009-10-21 00:26:58
A:
Depends on your AOP. If you're using AspectJ with load time or compile time weaving, then you don't have an issue. If you're using the spring based AOP, then you have an issue because spring will only put aspects onto beans it creates. Meaning that if your factory makes the bean, it won't have any AOP instrumentation
Jherico
2009-10-20 22:29:31