[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
RE: [aspectj-users] System.out.prinltn and advicing
|
By the way, I usually match the field get on System.err and System.out: even
if you don't call println on them, you almost always get those fields to
output to them, which is usually not what you want (e.g.,
exception.printStackTrace(System.out) is also undesirable, as is print(...)
or exception.printStackTrace()). If you match PrintStream, you might also
have false positives by matching valid uses of a PrintStream to format file
output...
-----Original Message-----
From: aspectj-users-bounces@xxxxxxxxxxx
[mailto:aspectj-users-bounces@xxxxxxxxxxx] On Behalf Of Eric Bodden
Sent: Monday, October 01, 2007 6:32 AM
To: aspectj-users@xxxxxxxxxxx
Subject: Re: [aspectj-users] System.out.prinltn and advicing
I think it's actually pretty hard to exactly match that pattern,
especially not with a single advice. The problem is that
System.out.println() actually consists of *two* joinpoints: A field
load (l = System.out) and a method call (l.println()), where l is a
stack location. For both you want to make sure that it's the same l
you are referring to.
You should be able to match this pattern with two pieces of advice
that collaborate on this pattern (or by using a tracematch
http://abc.comlab.ox.ac.uk/papers#oopsla2005 :-))
Eric
On 01/10/2007, hermod.opstvedt@xxxxxxxxx <hermod.opstvedt@xxxxxxxxx> wrote:
>
>
> Hi
>
> Albeit no - It says it advises it, but when I run the tests, it never
enters
> the around advice
>
> Hermod
>
>
> -----Original Message-----
> From: aspectj-users-bounces@xxxxxxxxxxx
> [mailto:aspectj-users-bounces@xxxxxxxxxxx] On Behalf Of
> hermod.opstvedt@xxxxxxxxx
> Sent: Monday, October 01, 2007 2:35 PM
> To: aspectj-users@xxxxxxxxxxx
> Subject: RE: [aspectj-users] System.out.prinltn and advicing
>
>
> Hi
>
> I solved it :)
>
>
>
> pointcut systemOut() : get(* System.out);
>
> pointcut systemErr() : get(* System.err);
>
> pointcut sysout() : call(void *.println(..)) && !within(SysOutLoggAspect)
&&
> (cflow(systemOut()) || cflow(systemErr()));
>
> This seems to do the trick.
>
> Hermod
>
>
> -----Original Message-----
> From: aspectj-users-bounces@xxxxxxxxxxx
> [mailto:aspectj-users-bounces@xxxxxxxxxxx] On Behalf Of
> hermod.opstvedt@xxxxxxxxx
> Sent: Monday, October 01, 2007 2:12 PM
> To: aspectj-users@xxxxxxxxxxx
> Subject: [aspectj-users] System.out.prinltn and advicing
>
>
>
> Hi
>
> I am trying to write an advice that traps calls to System.out.println and
> System.err.println.
>
> If I write the advice as follows:
>
> public aspect SysOutLoggAspect {
>
> private final Logger LOGGER =
> Logger.getLogger(SysOutLoggAspect.class);
>
> pointcut sysout() : (call(void System.out.println(..)) ||
call(void
> System.err.println(..)) ) && !within(SysOutLoggAspect);
>
> void around(Object obj) : sysout() && args(obj) {
> Level level = LOGGER.getEffectiveLevel();
>
> LOGGER.log(thisJoinPoint.getSignature().getDeclaringTypeName(),
> level,
> obj, null);
> }
> }
>
> It does not apply the advice, and issues a warning (no match for this type
> name: System.out [Xlint:invalidAbsoluteTypeName]) about it
> in Eclipse (AJDT). If I however rewrite the pointcut to:
>
> pointcut sysout() : call(void *.println(..)) &&
> !within(SysOutLoggAspect);
>
> It does apply the advice, but I have no garantee that the method resides
> with System.out or System.err
>
> What is the best way to solve this?
>
> Hermod * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
*
> * * *
>
> This email with attachments is solely for the use of the individual or
> entity to whom it is addressed. Please also be aware that the DnB NOR
Group
> cannot accept any payment orders or other legally binding correspondence
> with
> customers as a part of an email.
>
> This email message has been virus checked by the anti virus programs used
> in the DnB NOR Group.
>
> * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
*
>
> * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
*
>
> This email with attachments is solely for the use of the individual or
> entity to whom it is addressed. Please also be aware that the DnB NOR
Group
> cannot accept any payment orders or other legally binding correspondence
> with
> customers as a part of an email.
>
> This email message has been virus checked by the anti virus programs used
> in the DnB NOR Group.
>
> * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
*
>
> * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
*
>
> This email with attachments is solely for the use of the individual or
> entity to whom it is addressed. Please also be aware that the DnB NOR
Group
> cannot accept any payment orders or other legally binding correspondence
> with
> customers as a part of an email.
>
> This email message has been virus checked by the anti virus programs used
> in the DnB NOR Group.
>
> * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
*
>
>
> _______________________________________________
> aspectj-users mailing list
> aspectj-users@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/aspectj-users
>
>
--
Eric Bodden
Sable Research Group
McGill University, Montréal, Canada
_______________________________________________
aspectj-users mailing list
aspectj-users@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/aspectj-users
