aspects as the integration spi project

[starksm64]

One thing we have talked about in the past is that the aspects module is a largely broken module in terms of dependencies since by definition the aspects are really integration code that is coupled to the associated subsystem the aspect integrates. We have talked about an integration project in the past, and one way this could be done would be to turn the aspect module into the integration project that houses the stable subsystem SPIs. The aspects/annotations would be part of this SPI.

[adrian.brock]

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.

[starksm64]

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.

[starksm64]

Just looking as the aspect module currently, everything in there but the org.jboss.aop.deployment code needs to be elsewhere.

[adrian.brock]

Affirmative! :-)

[kabirkhan]

Yup, at least the AS aspects should follow the AS version rather than the AOP version