Nabble - AspectJ - users

Annotation Style: Ways to access the target of an inter-type declaration inside the interface implementation?

2008-11-21T06:38:07Z

Hi,

I am currently implementing a lot of static cross-cutting with annotation style and have a hard time working around
the current limitations. My main problem is the inability to directly access the target object within the implementation of an interface
when making an inter-type declaration like

@DeclareParents(value="target", defaultImpl=Implementation.class)
public SomeInterface SomeInterfaceImpl;

public static Implementation implements SomeInterface
{
    //   "this" returns a reference to an object of this implementation class, not the target object
}

This topic has been already covered to some extent (like in http://dev.eclipse.org/mhonarc/lists/aspectj-users/msg05884.html),
but I couldn't find any direct hints or best practices how to implement a decent workaround for this situat

I started working with AspectJ some weeks ago, so my understanding for its internals might still be lacking,
but there seems to be no obvious way to access the target from inside the implementation class or vice versa.
(Although there is some kind of stub inside a targets class-file for each interface-method and some code that
creates the implementation object, that might indicate some field holding a reference ...)

My best "solution" so far is storing and retrieving a reference to the target object within the implementation class via get/set methods.
Setting the reference can be conveniently handled by an advice during creation of the target object. This is relatively easy to use,
but as all externally accessible methods must be declared in the interface, this approach is horribly invasive and I am not very happy with it.

sample code :

//-----defaultImpl-----
public static Implementation implements SomeInterface
{
   private Object target=null;

    public void setTarget(Object ob) {
        this.target=ob;
    }

    public Object getTarget() {
        return this.target;
    }

   public void someMethod(){
      // do something with the target object via getTarget()
   }
}

//-----Advice-----
@After(" execution( new(..)) && @target(SomeAnnotation) && target (obj))")
        public void storeReference(Object obj )
        {
            ((SomeInterface)obj).setTarget(obj);
        }

I was experimenting with awkward things like multiple interfaces on the implementation class (in order to keep the important interface clean
and "hide" the additional methods in another interface)but with no success. It either didn't compile or AspectJ generated a separate object
of the implementation class for each interface.

Are there any different/better solutions to this problem?

Regards,

Michael

Get news, entertainment and everything you care about at Live.com. Check it out!
_______________________________________________
aspectj-users mailing list
aspectj-users@...
https://dev.eclipse.org/mailman/listinfo/aspectj-users

RE: Exception ajdt

2008-11-21T00:02:22Z

Hi

I have filed a bug.

Hermod
-----Original Message-----
From: aspectj-users-bounces@...
[mailto:aspectj-users-bounces@...] On Behalf Of Andrew Eisenberg
Sent: Thursday, November 20, 2008 5:12 PM
To: aspectj-users@...
Subject: Re: [aspectj-users] Exception ajdt

This seems like a bug. Please file one under AspectJ.

Looks like the aspectj builder is trying to send a message to the
previous state, but the previous state is null because there are errors
in the program (likely a successful build has never completed) and a NPE
is thrown.

--a

On Thu, Nov 20, 2008 at 3:23 AM, <hermod.opstvedt@...> wrote:

> 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@...
> https://dev.eclipse.org/mailman/listinfo/aspectj-users
>

_______________________________________________
aspectj-users mailing list
aspectj-users@...
https://dev.eclipse.org/mailman/listinfo/aspectj-users
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *

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@...
https://dev.eclipse.org/mailman/listinfo/aspectj-users

AspectJ exam is on java black belt!

2008-11-20T16:07:37Z

Hi all,
we managed to have the exam on Java Black Belt. You can find it here :
http://www.javablackbelt.com/QuestionnaireDefDisplay.wwa?questPublicId=1630
, or arrive to it from the JavaBlackBelt home page, it's filed under the
section "Misc" together with OSGI and Java3D.

Now we have to add questions to it ... I'm adding some basic ones, but
will need your help revising them, fixing errors, voting them, and most
importantly filling with even more questions, especially the theoretical
ones.

I'd like to thanks all the people who helped on this effort.

Simone

--
Simone Gianni CEO Semeru s.r.l. Apache Committer
http://www.simonegianni.it/
_______________________________________________
aspectj-users mailing list
aspectj-users@...
https://dev.eclipse.org/mailman/listinfo/aspectj-users

Re: Exception ajdt

2008-11-20T08:11:57Z

This seems like a bug. Please file one under AspectJ.

Looks like the aspectj builder is trying to send a message to the
previous state, but the previous state is null because there are
errors in the program (likely a successful build has never completed)
and a NPE is thrown.

--a

On Thu, Nov 20, 2008 at 3:23 AM, <hermod.opstvedt@...> wrote:

> Hi
>
> Before posting a bug for ajdt, I was wondering if anybody else is
> experiencing a problem with it. The scenario is that if there is any
> kind error in my aspect (missing import, mispelled variable etc.) I get
> the following exception from ajdt when I save it:
>
> java.lang.NullPointerException
> at
> org.aspectj.ajde.core.internal.AjdeCoreBuildManager.performBuild(AjdeCor
> eBuildManager.java:121)
> at org.aspectj.ajde.core.AjCompiler.build(AjCompiler.java:88)
> at org.eclipse.ajdt.core.builder.AJBuilder.build(AJBuilder.java:228)
> at
> org.eclipse.core.internal.events.BuildManager$2.run(BuildManager.java:63
> 3)
> at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:37)
> at org.eclipse.core.internal.events.B ...
> oBuildJob.run(AutoBuildJob.java:238)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
>
> Compile error: NullPointerException thrown: null
>
>
> I am using version 1.6.1.20081104192500
>
> 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.
>
> * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
>
> _______________________________________________
> aspectj-users mailing list
> aspectj-users@...
> https://dev.eclipse.org/mailman/listinfo/aspectj-users
>

_______________________________________________
aspectj-users mailing list
aspectj-users@...
https://dev.eclipse.org/mailman/listinfo/aspectj-users

Exception ajdt

2008-11-20T03:23:59Z

Hi

Before posting a bug for ajdt, I was wondering if anybody else is
experiencing a problem with it. The scenario is that if there is any
kind error in my aspect (missing import, mispelled variable etc.) I get
the following exception from ajdt when I save it:

java.lang.NullPointerException
at
org.aspectj.ajde.core.internal.AjdeCoreBuildManager.performBuild(AjdeCor
eBuildManager.java:121)
at org.aspectj.ajde.core.AjCompiler.build(AjCompiler.java:88)
at org.eclipse.ajdt.core.builder.AJBuilder.build(AJBuilder.java:228)
at
org.eclipse.core.internal.events.BuildManager$2.run(BuildManager.java:63
3)
at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:37)
at org.eclipse.core.internal.events.B ...
oBuildJob.run(AutoBuildJob.java:238)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)

Compile error: NullPointerException thrown: null

I am using version 1.6.1.20081104192500

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.

* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *

_______________________________________________
aspectj-users mailing list
aspectj-users@...
https://dev.eclipse.org/mailman/listinfo/aspectj-users

Re: external concrete aspect using LTW with java 1.4

2008-11-18T11:20:56Z

Thanks for the help Andrew. I appreciate.

On Tue, Nov 18, 2008 at 8:12 PM, Andrew Eisenberg <andrew@...> wrote:

This is already logged as a bug:

https://bugs.eclipse.org/bugs/show_bug.cgi?id=131728

On Tue, Nov 18, 2008 at 9:51 AM, epro etc <epro66@...> wrote:
> Hi Andrew,
>
> Thanks for the reply.
> Regarding your questions, If MyConcreteAspect is defined outside of the
> aop.xml file
> than it works fine like all the other aspects. The problem occurs only when
> the aspect
> is defined inline in the aop.xml file.
>
> I apologize for my mistakes in the sample code. I have mistype in the
> previous email
> I have send, that is not the problem.(MyConreteAspect is actually
> MyConcreteAspect.)
>
> Regards
>
>
> On Tue, Nov 18, 2008 at 5:29 PM, Andrew Eisenberg <andrew@...>
> wrote:
>>
>> Are you saying that MyConreteAspect is the only aspect defined inline
>> in the aop.xml and it is the only one not working? What happens if
>> you pull it out and define it in its own file? Does it work then?
>>
>> Note also that you have MyConreteAspect, not MyConcreteAspect.
>> Doubtful, but that could be the problem, too.
>>
>> On Tue, Nov 18, 2008 at 8:09 AM, epro etc <epro66@...> wrote:
>> > Hi all,
>> >
>> > I have managed to successfully configure LTW using java 1.4.
>> > Now I am facing a problem when trying to define a concrete aspect
>> > using in external aop.xml file.
>> >
>> > My abstract aspect is packed in a separate jar file(this jar already
>> > contains
>> > several more aspects that are working OK).
>> > When deployed on app server I am getting:
>> > java.lang.ClassNotFoundException: com.foo.aspect.MyConreteAspect not
>> > found -
>> > unable to determine URL
>> > Please note that all of my other aspects are working correctly.
>> >
>> > sample code:
>> > 1. This is my abstract aspect:
>> >
>> > public abstract aspect MyAbstractAspect
>> > {
>> > public abstract pointcut testConcrete();
>> >
>> > before() : testConcrete(){
>> > System.err.println("Adviced ....");
>> > }
>> > }
>> >
>> > 2. This is my external aop.xml file
>> > <aspectj>
>> > <weaver options="-verbose -showWeaveInfo" ></weaver>
>> > <aspects>
>> > <aspect name="test.aspect.Aspect_1">
>> > . . . . . . . . . .
>> > <aspect name="test.aspect.Aspect_N">
>> >
>> > <concrete-aspect name="test.aspect.MyConreteAspect"
>> > extends="test.aspect.MyAbstractAspect">
>> > <pointcut name="testConcrete" expression="execution(*
>> > Test.testMethod(..))"/>
>> > </concrete-aspect>
>> >
>> > </aspects>
>> > </aspectj>
>> >
>> >
>> > Any help is appreciated.
>> > Thanks in advance
>> >
>> > _______________________________________________
>> > aspectj-users mailing list
>> > aspectj-users@...
>> > https://dev.eclipse.org/mailman/listinfo/aspectj-users
>> >
>> >
>> _______________________________________________
>> aspectj-users mailing list
>> aspectj-users@...
>> https://dev.eclipse.org/mailman/listinfo/aspectj-users
>
>

_______________________________________________
aspectj-users mailing list
aspectj-users@...
https://dev.eclipse.org/mailman/listinfo/aspectj-users

Re: external concrete aspect using LTW with java 1.4

2008-11-18T11:12:00Z

This is already logged as a bug:

https://bugs.eclipse.org/bugs/show_bug.cgi?id=131728

On Tue, Nov 18, 2008 at 9:51 AM, epro etc <epro66@...> wrote:

> Hi Andrew,
>
> Thanks for the reply.
> Regarding your questions, If MyConcreteAspect is defined outside of the
> aop.xml file
> than it works fine like all the other aspects. The problem occurs only when
> the aspect
> is defined inline in the aop.xml file.
>
> I apologize for my mistakes in the sample code. I have mistype in the
> previous email
> I have send, that is not the problem.(MyConreteAspect is actually
> MyConcreteAspect.)
>
> Regards
>
>
> On Tue, Nov 18, 2008 at 5:29 PM, Andrew Eisenberg <andrew@...>
> wrote:
>>
>> Are you saying that MyConreteAspect is the only aspect defined inline
>> in the aop.xml and it is the only one not working? What happens if
>> you pull it out and define it in its own file? Does it work then?
>>
>> Note also that you have MyConreteAspect, not MyConcreteAspect.
>> Doubtful, but that could be the problem, too.
>>
>> On Tue, Nov 18, 2008 at 8:09 AM, epro etc <epro66@...> wrote:
>> > Hi all,
>> >
>> > I have managed to successfully configure LTW using java 1.4.
>> > Now I am facing a problem when trying to define a concrete aspect
>> > using in external aop.xml file.
>> >
>> > My abstract aspect is packed in a separate jar file(this jar already
>> > contains
>> > several more aspects that are working OK).
>> > When deployed on app server I am getting:
>> > java.lang.ClassNotFoundException: com.foo.aspect.MyConreteAspect not
>> > found -
>> > unable to determine URL
>> > Please note that all of my other aspects are working correctly.
>> >
>> > sample code:
>> > 1. This is my abstract aspect:
>> >
>> > public abstract aspect MyAbstractAspect
>> > {
>> > public abstract pointcut testConcrete();
>> >
>> > before() : testConcrete(){
>> > System.err.println("Adviced ....");
>> > }
>> > }
>> >
>> > 2. This is my external aop.xml file
>> > <aspectj>
>> > <weaver options="-verbose -showWeaveInfo" ></weaver>
>> > <aspects>
>> > <aspect name="test.aspect.Aspect_1">
>> > . . . . . . . . . .
>> > <aspect name="test.aspect.Aspect_N">
>> >
>> > <concrete-aspect name="test.aspect.MyConreteAspect"
>> > extends="test.aspect.MyAbstractAspect">
>> > <pointcut name="testConcrete" expression="execution(*
>> > Test.testMethod(..))"/>
>> > </concrete-aspect>
>> >
>> > </aspects>
>> > </aspectj>
>> >
>> >
>> > Any help is appreciated.
>> > Thanks in advance
>> >
>> > _______________________________________________
>> > aspectj-users mailing list
>> > aspectj-users@...
>> > https://dev.eclipse.org/mailman/listinfo/aspectj-users
>> >
>> >
>> _______________________________________________
>> aspectj-users mailing list
>> aspectj-users@...
>> https://dev.eclipse.org/mailman/listinfo/aspectj-users
>
>

_______________________________________________
aspectj-users mailing list
aspectj-users@...
https://dev.eclipse.org/mailman/listinfo/aspectj-users

Re: external concrete aspect using LTW with java 1.4

2008-11-18T09:51:59Z

Hi Andrew,

Thanks for the reply.
Regarding your questions, If MyConcreteAspect is defined outside of the aop.xml file
than it works fine like all the other aspects. The problem occurs only when the aspect
is defined inline in the aop.xml file.

I apologize for my mistakes in the sample code. I have mistype in the previous email
I have send, that is not the problem.(MyConreteAspect is actually MyConcreteAspect.)

Regards

On Tue, Nov 18, 2008 at 5:29 PM, Andrew Eisenberg <andrew@...> wrote:

Are you saying that MyConreteAspect is the only aspect defined inline
in the aop.xml and it is the only one not working? What happens if
you pull it out and define it in its own file? Does it work then?

Note also that you have MyConreteAspect, not MyConcreteAspect.
Doubtful, but that could be the problem, too.

On Tue, Nov 18, 2008 at 8:09 AM, epro etc <epro66@...> wrote:
> Hi all,
>
> I have managed to successfully configure LTW using java 1.4.
> Now I am facing a problem when trying to define a concrete aspect
> using in external aop.xml file.
>
> My abstract aspect is packed in a separate jar file(this jar already
> contains
> several more aspects that are working OK).
> When deployed on app server I am getting:
> java.lang.ClassNotFoundException: com.foo.aspect.MyConreteAspect not found -
> unable to determine URL
> Please note that all of my other aspects are working correctly.
>
> sample code:
> 1. This is my abstract aspect:
>
> public abstract aspect MyAbstractAspect
> {
> public abstract pointcut testConcrete();
>
> before() : testConcrete(){
> System.err.println("Adviced ....");
> }
> }
>
> 2. This is my external aop.xml file
> <aspectj>
> <weaver options="-verbose -showWeaveInfo" ></weaver>
> <aspects>
> <aspect name="test.aspect.Aspect_1">
> . . . . . . . . . .
> <aspect name="test.aspect.Aspect_N">
>
> <concrete-aspect name="test.aspect.MyConreteAspect"
> extends="test.aspect.MyAbstractAspect">
> <pointcut name="testConcrete" expression="execution(*
> Test.testMethod(..))"/>
> </concrete-aspect>
>
> </aspects>
> </aspectj>
>
>
> Any help is appreciated.
> Thanks in advance
>

> _______________________________________________
> aspectj-users mailing list
> aspectj-users@...
> https://dev.eclipse.org/mailman/listinfo/aspectj-users
>
>
_______________________________________________
aspectj-users mailing list
aspectj-users@...
https://dev.eclipse.org/mailman/listinfo/aspectj-users

_______________________________________________
aspectj-users mailing list
aspectj-users@...
https://dev.eclipse.org/mailman/listinfo/aspectj-users

Re: external concrete aspect using LTW with java 1.4

2008-11-18T08:29:31Z

Are you saying that MyConreteAspect is the only aspect defined inline
in the aop.xml and it is the only one not working? What happens if
you pull it out and define it in its own file? Does it work then?

Note also that you have MyConreteAspect, not MyConcreteAspect.
Doubtful, but that could be the problem, too.

On Tue, Nov 18, 2008 at 8:09 AM, epro etc <epro66@...> wrote:

> Hi all,
>
> I have managed to successfully configure LTW using java 1.4.
> Now I am facing a problem when trying to define a concrete aspect
> using in external aop.xml file.
>
> My abstract aspect is packed in a separate jar file(this jar already
> contains
> several more aspects that are working OK).
> When deployed on app server I am getting:
> java.lang.ClassNotFoundException: com.foo.aspect.MyConreteAspect not found -
> unable to determine URL
> Please note that all of my other aspects are working correctly.
>
> sample code:
> 1. This is my abstract aspect:
>
> public abstract aspect MyAbstractAspect
> {
> public abstract pointcut testConcrete();
>
> before() : testConcrete(){
> System.err.println("Adviced ....");
> }
> }
>
> 2. This is my external aop.xml file
> <aspectj>
> <weaver options="-verbose -showWeaveInfo" ></weaver>
> <aspects>
> <aspect name="test.aspect.Aspect_1">
> . . . . . . . . . .
> <aspect name="test.aspect.Aspect_N">
>
> <concrete-aspect name="test.aspect.MyConreteAspect"
> extends="test.aspect.MyAbstractAspect">
> <pointcut name="testConcrete" expression="execution(*
> Test.testMethod(..))"/>
> </concrete-aspect>
>
> </aspects>
> </aspectj>
>
>
> Any help is appreciated.
> Thanks in advance
>
> _______________________________________________
> aspectj-users mailing list
> aspectj-users@...
> https://dev.eclipse.org/mailman/listinfo/aspectj-users
>
>

_______________________________________________
aspectj-users mailing list
aspectj-users@...
https://dev.eclipse.org/mailman/listinfo/aspectj-users

external concrete aspect using LTW with java 1.4

2008-11-18T08:09:28Z

Hi all,

I have managed to successfully configure LTW using java 1.4.
Now I am facing a problem when trying to define a concrete aspect
using in external aop.xml file.

My abstract aspect is packed in a separate jar file(this jar already contains
several more aspects that are working OK).
When deployed on app server I am getting:
java.lang.ClassNotFoundException: com.foo.aspect.MyConreteAspect not found - unable to determine URL
Please note that all of my other aspects are working correctly.

sample code:
1. This is my abstract aspect:

public abstract aspect MyAbstractAspect
{
    public abstract pointcut testConcrete();

    before() : testConcrete(){
        System.err.println("Adviced ....");
    }
}

2. This is my external aop.xml file
<aspectj>
    <weaver options="-verbose -showWeaveInfo" ></weaver>
    <aspects>
        <aspect name="test.aspect.Aspect_1">
        . . . . . . . . . .
        <aspect name="test.aspect.Aspect_N">

   <concrete-aspect name="test.aspect.MyConreteAspect" extends="test.aspect.MyAbstractAspect">
             <pointcut name="testConcrete" expression="execution(* Test.testMethod(..))"/>
        </concrete-aspect>

    </aspects>
</aspectj>

Any help is appreciated.
Thanks in advance

_______________________________________________
aspectj-users mailing list
aspectj-users@...
https://dev.eclipse.org/mailman/listinfo/aspectj-users

Re: How to determine whether a nested class constructor is being called

2008-11-18T07:35:17Z

Okay having had a look at the Java language specification, I have
decided this is a bug and am posting it with the following summary.

thisJoinPoint.getArgs() exposes incorrect parameter when the join point
is a nested class constructor call.

Piers

Piers wrote:

> Thanks for the reply Eric.
>
> I would agree that the behaviour does not seem to make sense, can anyone
> confirm our suspicion as to whether this really is a bug?
>
> Thank you
>
> Piers
>
>
> Eric Bodden wrote:
>> I think that the current behavior does not make much sense. Usually,
>> the additional parameter holds the outer instance of the inner class.
>> It should never be null, and I am not sure why null ends up being
>> bound in the aspect in your case. I think that's a bug.
>>
>> Either AspectJ should correctly bind the outer instance, or it should
>> not expose this implicit argument at all (which is probably what one
>> actually wants).
>>
>> Just my two cents,
>> Eric
>>
>> 2008/11/15 Piers Powlesland <piers@...>:
>>> Hi
>>>
>>> I am attempting to write an aspect that checks for null arguments
>>> passed to
>>> any constructors defined in our project, the problem i am having is that
>>> calls to constructors of inner classes get passed a *secret*
>>> parameter which
>>> evaluates to null. I cannot seem to figure out a way to determine
>>> whether
>>> the constructor called belongs to a nested class and therefore cannot
>>> avoid
>>> these special cases.
>>>
>>> Here is some example code.
>>>
>>> First the aspect that i have created
>>>
>>> ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
>>>
>>>
>>> package com.historicalengineering.wwii.aspect.test;
>>>
>>> import java.lang.IllegalArgumentException;
>>>
>>> public aspect EnforceContractAspect
>>> {
>>>
>>> pointcut allMethodCallsWithParameters() :
>>> call(* com.historicalengineering..*(*,..));
>>>
>>> pointcut allConstructorCallsWithParameters() :
>>> call(com.historicalengineering..new(*,..)) ||
>>> call(private com.historicalengineering..new(*,..)) ||
>>> call(protected com.historicalengineering..new(*,..)) ||
>>> call(public com.historicalengineering..new(*,..));
>>>
>>> /*
>>> * Select all calls to any methods or constructors defined within
>>> * com.historicalengineering taking one or more parameters
>>> */
>>> pointcut allCallsWithParameters() :
>>> allConstructorCallsWithParameters() ||
>>> allMethodCallsWithParameters();
>>>
>>>
>>> before() : allCallsWithParameters()
>>> {
>>>
>>> Object[] args = thisJoinPoint.getArgs();
>>>
>>> for(int i = 0; i < args.length; i++)
>>> {
>>> if(args[i] == null)
>>> {
>>>
>>> throw new IllegalArgumentException(
>>>
>>> thisJoinPointStaticPart.getSignature()
>>> +" passed null
>>> parameter at
>>> position "+(i+1)
>>> +" of "+args.length);
>>> }
>>> }
>>>
>>> }
>>> }
>>>
>>> ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
>>>
>>>
>>> Second the test class
>>>
>>> ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
>>>
>>>
>>> package com.historicalengineering.wwii.aspect.test;
>>>
>>> public class A
>>> {
>>>
>>> public static void main(String[] args)
>>> {
>>> //A a = new A();
>>> //InnerStatic i = new InnerStatic();
>>> //a.foo();
>>> //a.bar();
>>>
>>> }
>>>
>>> protected void foo()
>>> {
>>> InnerStatic inner = new InnerStatic();
>>> }
>>>
>>> protected void bar()
>>> {
>>> Inner inner = new Inner();
>>> }
>>>
>>> static class InnerStatic
>>> {
>>> private InnerStatic()
>>> {
>>> }
>>> }
>>>
>>> class Inner
>>> {
>>> private Inner()
>>> {
>>> }
>>> }
>>>
>>> }
>>>
>>>
>>> ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
>>>
>>>
>>> Third some output
>>>
>>> ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
>>>
>>>
>>>
>>> Output when uncommenting the line: A a = new A();
>>>
>>> -None because this constructor really doesn't take any parameters.
>>>
>>>
>>>
>>> Output when uncommenting the line: InnerStatic i = new
>>> InnerStatic();
>>>
>>> Exception in thread "main" java.lang.IllegalArgumentException:
>>> com.historicalengineering.wwii.aspect.test.A.InnerStatic(A.InnerStatic)
>>> passed null parameter at position 1 of 1
>>> at
>>> com.historicalengineering.wwii.aspect.test.EnforceContractAspect.ajc$before$com_historicalengineering_wwii_aspect_test_EnforceContractAspect$1$f789a125(EnforceContractAspect.aj:45)
>>>
>>> at com.historicalengineering.wwii.aspect.test.A.main(A.java:9)
>>>
>>> - As you can see from the trace the inner static constructor was
>>> passed an
>>> "A.InnerStatic" type which has evaluated to null.
>>>
>>>
>>>
>>> Output when uncommenting the lines: A a = new A(); & a.foo();
>>>
>>> Exception in thread "main" java.lang.IllegalArgumentException:
>>> com.historicalengineering.wwii.aspect.test.A.InnerStatic(A.InnerStatic)
>>> passed null parameter at position 1 of 1
>>> at
>>> com.historicalengineering.wwii.aspect.test.EnforceContractAspect.ajc$before$com_historicalengineering_wwii_aspect_test_EnforceContractAspect$1$f789a125(EnforceContractAspect.aj:40)
>>>
>>> at com.historicalengineering.wwii.aspect.test.A.foo(A.java:17)
>>> at com.historicalengineering.wwii.aspect.test.A.main(A.java:10)
>>>
>>> - Again the null "A.InnerStatic" type has been passed to the
>>> constructor.
>>>
>>>
>>>
>>> Output when uncommenting the lines: A a = new A(); & a.bar();
>>>
>>> Exception in thread "main" java.lang.IllegalArgumentException:
>>> com.historicalengineering.wwii.aspect.test.A.Inner(A, A.Inner) passed
>>> null
>>> parameter at position 2 of 2
>>> at
>>> com.historicalengineering.wwii.aspect.test.EnforceContractAspect.ajc$before$com_historicalengineering_wwii_aspect_test_EnforceContractAspect$1$f789a125(EnforceContractAspect.aj:40)
>>>
>>> at com.historicalengineering.wwii.aspect.test.A.bar(A.java:22)
>>> at com.historicalengineering.wwii.aspect.test.A.main(A.java:11)
>>>
>>> -In the case of the non static nested class it is passed 2 hidden
>>> parameters
>>> the enclosing class "A" which does not evaluate to null and again the
>>> infuriating "A.Inner" class which is null.
>>>
>>>
>>> Your thoughts and help would be very much appreciated.
>>>
>>> Thank you
>>>
>>> Piers
>>>
>>> _______________________________________________
>>> aspectj-users mailing list
>>> aspectj-users@...
>>> https://dev.eclipse.org/mailman/listinfo/aspectj-users
>>>
>>
>>
>>
> _______________________________________________
> aspectj-users mailing list
> aspectj-users@...
> https://dev.eclipse.org/mailman/listinfo/aspectj-users

_______________________________________________
aspectj-users mailing list
aspectj-users@...
https://dev.eclipse.org/mailman/listinfo/aspectj-users

Re: set() pointcut for private fields

2008-11-18T06:13:37Z

After some experimenting I convince myself that this aspect weaves
just fine with static weaving, but for some reason does not get woven
with LTW. I guess this is a bug, so I opened a new report: https://bugs.eclipse.org/bugs/show_bug.cgi?id=255643

Jochen

On Nov 16, 2008, at 6:36 PM, Jochen Wuttke wrote:

> Hi,
>
> I have the following class and aspect structure:
>
> public abstract class A {
>
> private List<?> list;
>
> public getList() {
> if ( list == null ) {
> list = m(); //m() creates a new list implementation
> }
> return list;
> }
> }
>
> public privileged aspect AA {
>
> before(): set(* A.list) {
> //do something
> }
> }
>
> Using load time weaving the assignment to list is not getting
> advised. I tried different variants of the pointcut like set(*
> *.list), but that doesn't help. The aspect gets registered an other
> advice/pointcuts of the aspect do work as expected, so what am I
> doing wrong here?
>
>
> Jochen
>
> _______________________________________________
> aspectj-users mailing list
> aspectj-users@...
> https://dev.eclipse.org/mailman/listinfo/aspectj-users

_______________________________________________
aspectj-users mailing list
aspectj-users@...
https://dev.eclipse.org/mailman/listinfo/aspectj-users

Re: How to determine whether a nested class constructor is being called

2008-11-18T04:35:29Z

Thanks for the reply Eric.

I would agree that the behaviour does not seem to make sense, can anyone
confirm our suspicion as to whether this really is a bug?

Thank you

Piers

Eric Bodden wrote:

> I think that the current behavior does not make much sense. Usually,
> the additional parameter holds the outer instance of the inner class.
> It should never be null, and I am not sure why null ends up being
> bound in the aspect in your case. I think that's a bug.
>
> Either AspectJ should correctly bind the outer instance, or it should
> not expose this implicit argument at all (which is probably what one
> actually wants).
>
> Just my two cents,
> Eric
>
> 2008/11/15 Piers Powlesland <piers@...>:
>> Hi
>>
>> I am attempting to write an aspect that checks for null arguments passed to
>> any constructors defined in our project, the problem i am having is that
>> calls to constructors of inner classes get passed a *secret* parameter which
>> evaluates to null. I cannot seem to figure out a way to determine whether
>> the constructor called belongs to a nested class and therefore cannot avoid
>> these special cases.
>>
>> Here is some example code.
>>
>> First the aspect that i have created
>>
>> ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
>>
>> package com.historicalengineering.wwii.aspect.test;
>>
>> import java.lang.IllegalArgumentException;
>>
>> public aspect EnforceContractAspect
>> {
>>
>> pointcut allMethodCallsWithParameters() :
>> call(* com.historicalengineering..*(*,..));
>>
>> pointcut allConstructorCallsWithParameters() :
>> call(com.historicalengineering..new(*,..)) ||
>> call(private com.historicalengineering..new(*,..)) ||
>> call(protected com.historicalengineering..new(*,..)) ||
>> call(public com.historicalengineering..new(*,..));
>>
>> /*
>> * Select all calls to any methods or constructors defined within
>> * com.historicalengineering taking one or more parameters
>> */
>> pointcut allCallsWithParameters() :
>> allConstructorCallsWithParameters() ||
>> allMethodCallsWithParameters();
>>
>>
>> before() : allCallsWithParameters()
>> {
>>
>> Object[] args = thisJoinPoint.getArgs();
>>
>> for(int i = 0; i < args.length; i++)
>> {
>> if(args[i] == null)
>> {
>>
>> throw new IllegalArgumentException(
>>
>> thisJoinPointStaticPart.getSignature()
>> +" passed null parameter at
>> position "+(i+1)
>> +" of "+args.length);
>> }
>> }
>>
>> }
>> }
>>
>> ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
>>
>> Second the test class
>>
>> ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
>>
>> package com.historicalengineering.wwii.aspect.test;
>>
>> public class A
>> {
>>
>> public static void main(String[] args)
>> {
>> //A a = new A();
>> //InnerStatic i = new InnerStatic();
>> //a.foo();
>> //a.bar();
>>
>> }
>>
>> protected void foo()
>> {
>> InnerStatic inner = new InnerStatic();
>> }
>>
>> protected void bar()
>> {
>> Inner inner = new Inner();
>> }
>>
>> static class InnerStatic
>> {
>> private InnerStatic()
>> {
>> }
>> }
>>
>> class Inner
>> {
>> private Inner()
>> {
>> }
>> }
>>
>> }
>>
>>
>> ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
>>
>> Third some output
>>
>> ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
>>
>>
>> Output when uncommenting the line: A a = new A();
>>
>> -None because this constructor really doesn't take any parameters.
>>
>>
>>
>> Output when uncommenting the line: InnerStatic i = new InnerStatic();
>>
>> Exception in thread "main" java.lang.IllegalArgumentException:
>> com.historicalengineering.wwii.aspect.test.A.InnerStatic(A.InnerStatic)
>> passed null parameter at position 1 of 1
>> at
>> com.historicalengineering.wwii.aspect.test.EnforceContractAspect.ajc$before$com_historicalengineering_wwii_aspect_test_EnforceContractAspect$1$f789a125(EnforceContractAspect.aj:45)
>> at com.historicalengineering.wwii.aspect.test.A.main(A.java:9)
>>
>> - As you can see from the trace the inner static constructor was passed an
>> "A.InnerStatic" type which has evaluated to null.
>>
>>
>>
>> Output when uncommenting the lines: A a = new A(); & a.foo();
>>
>> Exception in thread "main" java.lang.IllegalArgumentException:
>> com.historicalengineering.wwii.aspect.test.A.InnerStatic(A.InnerStatic)
>> passed null parameter at position 1 of 1
>> at
>> com.historicalengineering.wwii.aspect.test.EnforceContractAspect.ajc$before$com_historicalengineering_wwii_aspect_test_EnforceContractAspect$1$f789a125(EnforceContractAspect.aj:40)
>> at com.historicalengineering.wwii.aspect.test.A.foo(A.java:17)
>> at com.historicalengineering.wwii.aspect.test.A.main(A.java:10)
>>
>> - Again the null "A.InnerStatic" type has been passed to the constructor.
>>
>>
>>
>> Output when uncommenting the lines: A a = new A(); & a.bar();
>>
>> Exception in thread "main" java.lang.IllegalArgumentException:
>> com.historicalengineering.wwii.aspect.test.A.Inner(A, A.Inner) passed null
>> parameter at position 2 of 2
>> at
>> com.historicalengineering.wwii.aspect.test.EnforceContractAspect.ajc$before$com_historicalengineering_wwii_aspect_test_EnforceContractAspect$1$f789a125(EnforceContractAspect.aj:40)
>> at com.historicalengineering.wwii.aspect.test.A.bar(A.java:22)
>> at com.historicalengineering.wwii.aspect.test.A.main(A.java:11)
>>
>> -In the case of the non static nested class it is passed 2 hidden parameters
>> the enclosing class "A" which does not evaluate to null and again the
>> infuriating "A.Inner" class which is null.
>>
>>
>> Your thoughts and help would be very much appreciated.
>>
>> Thank you
>>
>> Piers
>>
>> _______________________________________________
>> aspectj-users mailing list
>> aspectj-users@...
>> https://dev.eclipse.org/mailman/listinfo/aspectj-users
>>
>
>
>

_______________________________________________
aspectj-users mailing list
aspectj-users@...
https://dev.eclipse.org/mailman/listinfo/aspectj-users

Re: warning on wrong constructor

2008-11-17T07:51:09Z

Yes, declare warning is compile time only. You could advise this at
runtime and throw an exception if it doesn't conform to you
specifications.

On Fri, Nov 14, 2008 at 8:58 AM, Luca Ferrari <fluca1978@...> wrote:

> Hi,
> I don't know if it is possible, but I'd like to declare a warning for a
> constructor calls of objects SerializableObject+ when the constructors do not
> initialize all the Collection+ declared within the same class. My thought is
> to write a pointcut that exports the context of the object being constructed,
> so that with reflection I can see the declared collections and get their
> values (that should not be null). The problem is that declare warning works
> not at run-time, right? So I cannot get a context or execute reflection on the
> object. Is there a way to achieve this?
>
> Thanks,
> Luca
> _______________________________________________
> aspectj-users mailing list
> aspectj-users@...
> https://dev.eclipse.org/mailman/listinfo/aspectj-users
>

_______________________________________________
aspectj-users mailing list
aspectj-users@...
https://dev.eclipse.org/mailman/listinfo/aspectj-users

Re: set() pointcut for private fields

2008-11-17T02:18:37Z

To add something to this:

Following the suggestion of a colleague, I tried this on a small toy
example, and it worked fine.
So this looks like the same problem that I had with ITDs, that would
work fine on small toy examples, but on real sized applications
(Tomcat) they don't work anymore. So I was wondering if with regard to
load-time weaving, are there any extra requirements, like the order of
JAR files on the classpath or stuff like that, which could have an
influence on the weaving?

Jochen

On Nov 16, 2008, at 6:36 PM, Jochen Wuttke wrote:

_______________________________________________
aspectj-users mailing list
aspectj-users@...
https://dev.eclipse.org/mailman/listinfo/aspectj-users

Re: can arg names be accessed at a joinpoint?

2008-11-16T11:43:07Z

Aiieee thanks! the old "can't see my own handwriting" trick!

Now calls to DummyObject.someMethod:
public class DummyObject
{
	public int someMethod(int i, int my2ndarg)

log like this:

-7    [main] INFO  com.AjlibTest.DummyObject  - trace enter: int com.AjlibTest.DummyObject.someMethod(int, int) , this: com.AjlibTest.DummyObject@152544e, args: i = 5, my2ndarg = 9

with this adjustment to the logging aspect:
	    	Object
 arguments[] = joinPoint.getArgs();
	    	CodeSignature codeSignature = (CodeSignature) joinPoint.getSignature();
	    	String[] argNames = codeSignature.getParameterNames();
		logStr.append(", args: "+arguments(argNames, arguments));
	    }
	    return logStr.toString();
	}
	

	protected String arguments(String[] argNames, Object[] arguments) {
        StringBuffer logStr = new StringBuffer();
        for (int i = 0; i < arguments.length; i++) {
            logStr.append((i>0 ? ", ":"")+ argNames[i] + " = " + traceString(arguments[i]));
        }
        return logStr.toString();
	}

much thanks,
owen

From: Ramnivas Laddad <ramnivas@...>
To: aspectj-users@...
Sent: Saturday, November 15, 2008 2:42:55 PM
Subject: Re: [aspectj-users] can arg names be accessed at a joinpoint?


It seems that it is all working correctly. Does your method is
declared as someMethod(int i)? Is so, the output seems to correctly
print "i". You are getting "arg 0" part because you are printing "arg
"+i. Right?

-Ramnivas

On Sat, Nov 15, 2008 at 3:26 PM, Owen Corpening <owencorpening@...> wrote:
>
> Lord have mercy, ever wish you could take back a posting? I corrected my code, same results, the two lines below should have read:
> logStr.append(", args using CodeSignature: "+arguments(argNames));
> logStr.append(", args using getArgs: "+arguments(getargs));
> output is same
> darnit all
> owen
> ________________________________
> From: Owen Corpening <owencorpening@...>
> To: aspectj-users@...
> Sent: Saturday, November 15, 2008 2:00:05 PM
> Subject: Re: [aspectj-users] can arg names be accessed at a joinpoint?
>
> I not only compile with -g, I am running within the eclipse debugger and I still get "arg 0".
> Plus doesn't thisJoinPoint.getArgs() do the same thing? Seems to, sorry I didn't read the aspectj src to confirm, I am downloading that today.
>    if (joinPoint.getArgs() != null && joinPoint.getArgs().length>0) {
>     Object getargs[] = joinPoint.getArgs();
>     CodeSignature codeSignature = (CodeSignature) joinPoint.getSignature();
>     String[] argNames = codeSignature.getParameterNames();
> logStr.append(", args using CodeSignature: "+arguments(argNames));
> logStr.append(", args using getArgs: "+arguments(argNames));
>    }
> return logStr.toString();
>
 }
> protected String arguments(Object[] arguments) {
>         StringBuffer logStr = new StringBuffer();
>         for (int i = 0; i < arguments.length; i++) {
>             logStr.append((i>0 ? ", ":"")+ "arg "+i+" = "+traceString(arguments[i]));
>         }
>         return logStr.toString();
> }
> console output:
> INFO  com.AjlibTest.DummyObject  - trace enter: int com.AjlibTest.DummyObject.someMethod(int) , this: com.AjlibTest.DummyObject@152544e, args using CodeSignature: arg 0 = i, args using getArgs: arg 0 = i
> -3    [main]
> owen
> Ramnivas Laddad wrote:
> If you compile your code using ajc or javac with -g (for binary weaving purpose), you will get the original argument names.
> -Ramnivas
>
> On Fri, Nov 14, 2008 at 8:19 AM, rmahmood <rashid_m180@...> wrote:
>>
>> But
 this will give the argument names as saved in .class file, normally arg0,
>> arg1 etc.
>> not the original names as in source code.
>>
>> Is there any way to get original names as specified in source code?
>>
>>
>> Ramnivas Laddad wrote:
>> >
>> > You get get the associated CodeSignature object as follows:
>> > CodeSignature codeSignature = (CodedSignature)
>> > thisJoinPoint.getSignature();
>> > String[] argNames = codeSignature.getParameterNames();
>> >
>> > -Ramnivas
>> >
>> > On Wed, Nov 12, 2008 at 10:48 PM, Owen Corpening
>> > <owencorpening@...>wrote:
>> >
>> >> I am using a tracing aspect and it is printing the method arg values upon
>> >> entry, but without arg names:
>> >> trace enter: int com.AjlibTest.DummyObject.someMethod(int) , this:
>> >> com.AjlibTest.DummyObject@18941f7, args:
 arg 0 = 5
>> >>
>> >> using joinPoint.getArgs() - I can see in the debugger that the arg names
>> >> are not in the joinpoint - is there a way an aspect can capture that
>> >> info?
>> >>
>> >> Owen Corpening
>> >> 10911 Watchful Fox Drive
>> >> Austin, TX 78748
>> >>
>> >> 512 280-1753 Home
>> >> 512 634-5148 Office
>> >> 512 659-5300 Cell
>> >>
>> >>
>> >> _______________________________________________
>> >> aspectj-users mailing list
>> >> aspectj-users@...
>> >> https://dev.eclipse.org/mailman/listinfo/aspectj-users
>> >>
>> >>
>> >
>> > _______________________________________________
>> > aspectj-users mailing list
>> > aspectj-users@...
>> > https://dev.eclipse.org/mailman/listinfo/aspectj-users
>> >
>> >
>>
>> --
>> View this message in context: http://www.nabble.com/can-arg-names-be-accessed-at-a-joinpoint--tp20474387p20500385.html
>> Sent from the AspectJ - users mailing list archive at Nabble.com.
>>
>> _______________________________________________
>> aspectj-users mailing list
>> aspectj-users@...
>> https://dev.eclipse.org/mailman/listinfo/aspectj-users
>
>
>
>
> _______________________________________________
> aspectj-users mailing list
> aspectj-users@...
> https://dev.eclipse.org/mailman/listinfo/aspectj-users
>
_______________________________________________
aspectj-users mailing list
aspectj-users@...
https://dev.eclipse.org/mailman/listinfo/aspectj-users

_______________________________________________
aspectj-users mailing list
aspectj-users@...
https://dev.eclipse.org/mailman/listinfo/aspectj-users

set() pointcut for private fields

2008-11-16T09:36:01Z

Hi,

I have the following class and aspect structure:

public abstract class A {

private List<?> list;

public getList() {
if ( list == null ) {
list = m(); //m() creates a new list implementation
}
return list;
}
}

public privileged aspect AA {

before(): set(* A.list) {
//do something
}
}

Using load time weaving the assignment to list is not getting advised.
I tried different variants of the pointcut like set(* *.list), but
that doesn't help. The aspect gets registered an other advice/
pointcuts of the aspect do work as expected, so what am I doing wrong
here?

Jochen

_______________________________________________
aspectj-users mailing list
aspectj-users@...
https://dev.eclipse.org/mailman/listinfo/aspectj-users

Re: can arg names be accessed at a joinpoint?

2008-11-15T12:42:55Z

It seems that it is all working correctly. Does your method is
declared as someMethod(int i)? Is so, the output seems to correctly
print "i". You are getting "arg 0" part because you are printing "arg
"+i. Right?

-Ramnivas

On Sat, Nov 15, 2008 at 3:26 PM, Owen Corpening <owencorpening@...> wrote:

>
> Lord have mercy, ever wish you could take back a posting? I corrected my code, same results, the two lines below should have read:
> logStr.append(", args using CodeSignature: "+arguments(argNames));
> logStr.append(", args using getArgs: "+arguments(getargs));
> output is same
> darnit all
> owen
> ________________________________
> From: Owen Corpening <owencorpening@...>
> To: aspectj-users@...
> Sent: Saturday, November 15, 2008 2:00:05 PM
> Subject: Re: [aspectj-users] can arg names be accessed at a joinpoint?
>
> I not only compile with -g, I am running within the eclipse debugger and I still get "arg 0".
> Plus doesn't thisJoinPoint.getArgs() do the same thing? Seems to, sorry I didn't read the aspectj src to confirm, I am downloading that today.
> if (joinPoint.getArgs() != null && joinPoint.getArgs().length>0) {
> Object getargs[] = joinPoint.getArgs();
> CodeSignature codeSignature = (CodeSignature) joinPoint.getSignature();
> String[] argNames = codeSignature.getParameterNames();
> logStr.append(", args using CodeSignature: "+arguments(argNames));
> logStr.append(", args using getArgs: "+arguments(argNames));
> }
> return logStr.toString();
> }
> protected String arguments(Object[] arguments) {
> StringBuffer logStr = new StringBuffer();
> for (int i = 0; i < arguments.length; i++) {
> logStr.append((i>0 ? ", ":"")+ "arg "+i+" = "+traceString(arguments[i]));
> }
> return logStr.toString();
> }
> console output:
> INFO com.AjlibTest.DummyObject - trace enter: int com.AjlibTest.DummyObject.someMethod(int) , this: com.AjlibTest.DummyObject@152544e, args using CodeSignature: arg 0 = i, args using getArgs: arg 0 = i
> -3 [main]
> owen
> Ramnivas Laddad wrote:
> If you compile your code using ajc or javac with -g (for binary weaving purpose), you will get the original argument names.
> -Ramnivas
>
> On Fri, Nov 14, 2008 at 8:19 AM, rmahmood <rashid_m180@...> wrote:
>>
>> But this will give the argument names as saved in .class file, normally arg0,
>> arg1 etc.
>> not the original names as in source code.
>>
>> Is there any way to get original names as specified in source code?
>>
>>
>> Ramnivas Laddad wrote:
>> >
>> > You get get the associated CodeSignature object as follows:
>> > CodeSignature codeSignature = (CodedSignature)
>> > thisJoinPoint.getSignature();
>> > String[] argNames = codeSignature.getParameterNames();
>> >
>> > -Ramnivas
>> >
>> > On Wed, Nov 12, 2008 at 10:48 PM, Owen Corpening
>> > <owencorpening@...>wrote:
>> >
>> >> I am using a tracing aspect and it is printing the method arg values upon
>> >> entry, but without arg names:
>> >> trace enter: int com.AjlibTest.DummyObject.someMethod(int) , this:
>> >> com.AjlibTest.DummyObject@18941f7, args: arg 0 = 5
>> >>
>> >> using joinPoint.getArgs() - I can see in the debugger that the arg names
>> >> are not in the joinpoint - is there a way an aspect can capture that
>> >> info?
>> >>
>> >> Owen Corpening
>> >> 10911 Watchful Fox Drive
>> >> Austin, TX 78748
>> >>
>> >> 512 280-1753 Home
>> >> 512 634-5148 Office
>> >> 512 659-5300 Cell
>> >>
>> >>
>> >> _______________________________________________
>> >> aspectj-users mailing list
>> >> aspectj-users@...
>> >> https://dev.eclipse.org/mailman/listinfo/aspectj-users
>> >>
>> >>
>> >
>> > _______________________________________________
>> > aspectj-users mailing list
>> > aspectj-users@...
>> > https://dev.eclipse.org/mailman/listinfo/aspectj-users
>> >
>> >
>>
>> --
>> View this message in context: http://www.nabble.com/can-arg-names-be-accessed-at-a-joinpoint--tp20474387p20500385.html
>> Sent from the AspectJ - users mailing list archive at Nabble.com.
>>
>> _______________________________________________
>> aspectj-users mailing list
>> aspectj-users@...
>> https://dev.eclipse.org/mailman/listinfo/aspectj-users
>
>
>
>
> _______________________________________________
> aspectj-users mailing list
> aspectj-users@...
> https://dev.eclipse.org/mailman/listinfo/aspectj-users
>

_______________________________________________
aspectj-users mailing list
aspectj-users@...
https://dev.eclipse.org/mailman/listinfo/aspectj-users