[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [aspectj-users] AspectJ 1.5 aop.xml question
- From: Alexandru Popescu <the.mindstorm.mailinglist@xxxxxxxxx>
- Date: Sun, 6 Nov 2005 19:45:04 +0200
- Delivered-to: email@example.com
- Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=Ma9+OQB3LBmKu6EW+YAwskBRgsbo9mP3QHcjI3ocrVfZ4Ho6fRIZCknkOAh4dMPUwb5NQ3R0ux/n3kuooeZxicYAMyhMy8BrLATVGaMI6WrfnxAzLpWk9w4rb75a4ScaIYYyEk2umwj8pOgYKDXyalDJF4vD7Zor7fPjMBqyf00=
afaik you need to list all the aspects you want weaved in your
project. than include/exclude are used only to filter them.
.w( the_mindstorm )p.
On 11/4/05, Nathan McEachen <nathan@xxxxxxxxxxxx> wrote:
> I have a question about load-time weaving in AspectJ. According to the
> AspectJ 5 Development Kit Developer's Notebook, the <aspects> element
> can have an <include within="[pattern]"> child element
> However, when I include that element as a child to the <aspects> element
> in my aop.xml file, I get a SAX exception:
> org.xml.sax.SAXException: Unknown element while parsing <aspectj>
> element: include
> Is the <include> element currently supported within the <aspects>
> element? Or do I have to explicitly list every aspect I want woven at
> load time using an <aspect name="..."> for each aspect? Basically I do
> not wish to explicitly ennumerate every aspect in the aop.xml file for
> the load-time weaver. Rather, I want to use a wildcard pattern to
> capture them all.
> In theory, there is no difference between theory and practice. But, in practice, there is.
> --Jan L.A. van de Snepscheut
> aspectj-users mailing list