Message-ID: <2134485822.7807.1418876141581.JavaMail.email@example.com> Subject: Exported From Confluence MIME-Version: 1.0 Content-Type: multipart/related; boundary="----=_Part_7806_1758541348.1418876141581" ------=_Part_7806_1758541348.1418876141581 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Content-Location: file:///C:/exported.html
The Spring Aspect Container in AWare will make it possi= ble to manage your aspects using Spring, it let's you treat th= e aspects just as any other Spring bean.=20
The container will read in a Spring configuration file called
e-config.xml, this file has to be on your classpath. In this file yo=
u can define your aspects, add parameters and data structures to them, pass=
in references to other components that is being used etc. This is for exam=
ple documented briefly in the Role-Based Security section. For details see the Spring documentation.
To tell the AspectWerkz system that you want to deploy a = specific aspect in the Spring aspect container (or any other custom aspect = container) you have to specifify that in the regular aspect definition file= like this:=20 =20
aware-config.xml file you have to configure the aspe=
cts like this:
id- specifies the name of the aspect if a custom name is = define you that else use the class name of the aspect (which is the default= name). Mandatory.
class- specifies the class name of the aspect. Mandatory.=
singleton- specifies that the aspect will be instantiated= using the prototype pattern, Mandatory and needed to be set to
init-methodis the method t= hat you are using to initialize the aspect. This method will be called when= all the properties have been set. Optional.
property- the metadata that you want to pass to the aspec= t (see the Spring documentation for details on how how to defi= ne properties). Optional.
For an example on how to configure aspect using Spring see the Role-Based Security component.<= /p>