Message-ID: <1440201337.4351.1369445481763.JavaMail.firstname.lastname@example.org> Subject: Exported From Confluence MIME-Version: 1.0 Content-Type: multipart/related; boundary="----=_Part_4350_1814720233.1369445481762" ------=_Part_4350_1814720233.1369445481762 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Content-Location: file:///C:/exported.html
In AspectWerkz aspects are managed by an aspect container,= which is responsible for creating and configuring the aspects. It also gi= ves you the possiblity of writing your own custom container implementation.= This is convenient when you want to have full control of how your aspects= are instantiated and configured.
This is important when you want the aspects to work together with an IoC= (Inversion Of Control) container such as Spring, = Pico Container or HiveMind.
If you want to write your own container then AspectWerkz provides a conv=
enient abstract base class, which handles all of the nitty-gritty details. =
All you have
to do is to extend the
class and implement the
To tell the AspectWerkz system that you want to deploy a specific aspect= in your custom oaspect container you have to specifify that in the regular= aspect definition file like this:------=_Part_4350_1814720233.1369445481762--