-
1. Re: aspects as the integration spi project
On the contrary.
I see the aspect project integration as dubious at best.
The real approach should be for each project to provide their own
aspect.
This has little to do with the "integration" module
which is about how do I integrate with JBossAS.
The more scalable problem is how do I integrate with X
to which the answer should be:
a) This requires a portable solution with alternative solutions
based on the platform
b) Use an aspect defined by project
The long term solution is definitely not to use the "aspects" project
as a dumping ground for integration code. -
2. Re: aspects as the integration spi project
We had also mentioned moving the aspects to the projects providing the api used by the aspect as well. There still is the question of where higher level abstractions reusable aspects/SPI exist. For example, the CMT interceptor on top of a pluggable JTA provider; the webservice integration layer used by the new transaction project.
-
3. Re: aspects as the integration spi project
Just looking as the aspect module currently, everything in there but the org.jboss.aop.deployment code needs to be elsewhere.
-
-
5. Re: aspects as the integration spi project
Yup, at least the AS aspects should follow the AS version rather than the AOP version