[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [aspectj-users] Describing the chattyness
|
I believe this use points to an interesting application for AOP. Warnings
could be used to measure code. In this case, the number of communication
with a certain layer could be counted by a tool that attaches to the IDE in
use and give the programmer a quantification about the code.
I already had a similar problem before. I had to create advices to tell
programmers about choices that could reflect in bad execution performance.
Programmers could have a tool that give them an overal report about code
quality so that this could guide their development. Warnings could be
classified according to it severity.
As a sugestion, warning declaration could be changed optionally to the
following:
declare warning (10, WARNING_CLASS) : within({Business});
where 10 is the severity and WARNING_CLASS is an enumeration item.
From: "Wes" <wes@xxxxxxxxxxxxxx>
Reply-To: wes@xxxxxxxxxxxxxx, aspectj-users@xxxxxxxxxxx
To: aspectj-users@xxxxxxxxxxx
Subject: Re: [aspectj-users] Describing the chattyness
Date: Thu, 28 Sep 2006 10:57:59 -0700
Calls from Business:
declare warning : within({Business}) && call({Dao}) : "business ->
DAO";
where {Business} and {Dao} depend on your system.
Similarly, callbacks from DAO:
declare warning : within({Dao}) && call({Business}) : "DAO ->
Business";
For a runtime accounting, use advice to log the same pointcuts.
Is that what you were looking for? ("reference count" typically means
the number of references to a particular object.)
(See also JDepends.)
Wes
btw, search didn't turn up any relevant definition of "AMOF"
> ------------Original Message------------
> From: Thomas SMETS - disposable add <duvelbier-tsmets@xxxxxxxxx>
> To: aspectj-users@xxxxxxxxxxx
> Date: Thu, Sep-28-2006 10:50 AM
> Subject: [aspectj-users] Describing the chattyness
>
>
> Dear,
>
> I was wondering how I could do a reference count...
> AMOF, I would like to measure the level of chattyness in my code :
>
>
> Service Layer <--> Business Layer <--> Dao <--> DB
>
>
> If I can forbid the Service to talk directly to the Dao, I woundered if
> I could also point the places where the Business was chatting too much
> with the DAO's (hence the DB).
>
> Any hint into this would be appreciated !
>
> \T,
>
>
> -- Any fool can write code that a computer can understand.
> Good programmers write code that humans can understand.
>
> Martin Fowler
>
> T. : +32 (0)2 742 05 94
> M. : +32 (0)497 44 68 12
> @ : duvelbier-tsmets@xxxxxxxxx
> Do you skype too ... (tsmets) ?
>
>
>
> _______________________________________________
> aspectj-users mailing list
> aspectj-users@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/aspectj-users
>
_______________________________________________
aspectj-users mailing list
aspectj-users@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/aspectj-users
_________________________________________________________________
あなたのPCの健康状態を無料でチェック・維持します http://safety.live.com/
