aspectj-users

Re: [aspectj-users] Advising advice

eric.bodden@xxxxxxx (Eric Bodden) — Sat, 30 Aug 2008 15:26:04 GMT

You have to store "thisJoinPoint" using the original advice (e.g. in a
field) or you hav eto make it the argument of a "dummy" method call
which will then be advised by the second advice.

Eric

2008/8/30 Sago Djuret :
> Is there a way to access the thisJoinPoint of an advice from a second advice?
>
> The following pointcut successfully picks out interesting calls from other advice.
>
>
> pointcut breachOfContract( boolean condition ):
>                call( * require( boolean ))
>                && args( condition );
>
>
>
> How can I access the data of the original thisJoinPoint? Something like:
>
> before( boolean condition ): breachOfContract( condition ) {
>        System.out.println( thisJoinPoint.getThis().getSourceLocation() );
> }
>
>
>
>
>
>
> _______________________________________________
> 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] Advising advice

sagodjuret@xxxxxxx (Sago Djuret) — Sat, 30 Aug 2008 11:22:45 GMT

Is there a way to access the thisJoinPoint of an advice from a second advice?

The following pointcut successfully picks out interesting calls from other advice.


pointcut breachOfContract( boolean condition ):
		call( * require( boolean ))
		&& args( condition );



How can I access the data of the original thisJoinPoint? Something like:

before( boolean condition ): breachOfContract( condition ) {
	System.out.println( thisJoinPoint.getThis().getSourceLocation() );
}

[aspectj-users] Advising advice

sagodjuret@xxxxxxx (Sago Djuret) — Sat, 30 Aug 2008 11:11:41 GMT

Is there a way to access the thisJoinPoint of an advice from a second advice?

The following pointcut successfully picks out interesting calls from other advice.


pointcut breachOfContract( boolean condition ):
		call( * require( boolean ))
		&& args( condition );



How can I access the data of the original thisJoinPoint? Something like:

before( boolean condition ): breachOfContract( condition ) {
	System.out.println( thisJoinPoint.getThis().getSourceLocation() );
}

Re: [aspectj-users] Getting Ejb Sessions IDs

andrew@xxxxxxx (Andrew Eisenberg) — Sat, 30 Aug 2008 09:49:01 GMT

I've been holding of since I don't know EJB very well, but if you can
provide some code (or pseudo code), then I can give you some ideas
about aspectj.

On Fri, Aug 29, 2008 at 6:34 PM, Guillaume Pothier  wrote:
>> What i was looking about getting Responses(Result) from this method calls?
>
> If I understand you (and AspectJ...) correctly, that would be either
> with an "after returning" advice
> (http://www.eclipse.org/aspectj/doc/released/progguide/semantics-advice.html),
> or with an around advice, using the result of proceed()
>
>> Most important is how can i get information like Bean Session IDs, and other
>> IDs and
>> contextual information?
>
> I know nothing about ejb, how do you get those from normal java code?
> You can probably get them in the same way in an advice.
> g
>
>>
>> Please share your ideas and experiences
>>
>> Regards
>>
>>
>> _______________________________________________
>> 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
>

Re: [aspectj-users] Getting Ejb Sessions IDs

gpothier@xxxxxxx (Guillaume Pothier) — Sat, 30 Aug 2008 01:34:34 GMT

> What i was looking about getting Responses(Result) from this method calls?

If I understand you (and AspectJ...) correctly, that would be either
with an "after returning" advice
(http://www.eclipse.org/aspectj/doc/released/progguide/semantics-advice.html),
or with an around advice, using the result of proceed()

> Most important is how can i get information like Bean Session IDs, and other
> IDs and
> contextual information?

I know nothing about ejb, how do you get those from normal java code?
You can probably get them in the same way in an advice.
g

>
> Please share your ideas and experiences
>
> Regards
>
>
> _______________________________________________
> aspectj-users mailing list
> aspectj-users@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/aspectj-users
>
>

Re: [aspectj-users] Problem with annotation based pointcut and inner classes

andrew@xxxxxxx (Andrew Eisenberg) — Fri, 29 Aug 2008 15:15:01 GMT

No problem at all.  :-)

On Fri, Aug 29, 2008 at 4:46 AM, Christian Kölle
 wrote:
> Andrew Eisenberg wrote:
>> Does this not work for you?  The call to method() in main() is where
>> the advice is applied.
>>
>
> Hi
>
> Thanks for the answer and sorry for the question in the first place.
> You're right, this works fine. My problem was the result of a build
> problem in our project. The subproject in question hasn't been weaved
> with the aspect.
>
> Sorry for wasting your time
> Christian
>

Re: [aspectj-users] Loadtime weaving of Ejb Calls

rashid_m180@xxxxxxx (rmahmood) — Fri, 29 Aug 2008 13:17:05 GMT


I didnt realize that Javax package was not included by default while
weaving.

I did it by placing weave tag inside aop.xml and included javax.ejb.* and 
now its weaving my ejb calls.

Thanx to one of previous posts.

 

rmahmood wrote:
> 
> Hi All,
> 
> I am working on an application where i have to intercept all the calls
> made by EjbHome and EjbObject interface from an existing J2EE
> Application(.jar or binary form).
> 
> How can i do it with loadtime weaving or is there any other way to do it?
> 
> Thanx for ur replies:confused:
> 
> 

-- 
View this message in context: http://www.nabble.com/Loadtime-weaving-of-Ejb-Calls-tp19161136p19219712.html
Sent from the AspectJ - users mailing list archive at Nabble.com.

Re: [aspectj-users] Problem with annotation based pointcut and inner classes

christian.koelle@xxxxxxx (Christian Kölle) — Fri, 29 Aug 2008 11:49:25 GMT

Andrew Eisenberg wrote:
> Does this not work for you?  The call to method() in main() is where
> the advice is applied.
> 

Hi

Thanks for the answer and sorry for the question in the first place.
You're right, this works fine. My problem was the result of a build
problem in our project. The subproject in question hasn't been weaved
with the aspect.

Sorry for wasting your time
Christian

[aspectj-users] Getting Ejb Sessions IDs

rashid_m180@xxxxxxx (Rashid Mahmood) — Fri, 29 Aug 2008 07:48:57 GMT

Hi All,

I am working on an application where i have to record/save Ejb invocations from an Ejb Client Application. I tried with AspectJ LoadTime Weaving and am able to get some information about these invocations like Method Name, Method Arguments etc.

What i was looking about getting Responses(Result) from this method calls?

Most important is how can i get information like Bean Session IDs, and other IDs and
contextual information?

Please share your ideas and experiences

Regards

Re: [aspectj-users] Regression from 1.5: can't find type error in AspectJ 1.6

kevinjohnhoffman@xxxxxxx (Kevin Hoffman) — Fri, 29 Aug 2008 01:50:10 GMT

Hi Andy,

Many thanks! The fix that you committed is working. I cannot reproduce
the issue with build aspectj-DEVELOPMENT-20080828133357.jar.
Everything is working properly again.

Kevin

On Wed, Aug 27, 2008 at 4:24 PM, Andy Clement  wrote:
> Hi Kevin,
>
> Thanks for trying that.  Instead of the unhelpful 'Argh!' message I now get
> a much more reasonable:
>
> Unable to pack method, jump (with opcode=167) is too far: 42205
> java.lang.IllegalStateException: Unable to pack method, jump (with
> opcode=167) is too far: 42205
>
> 	at
> org.aspectj.apache.bcel.generic.InstructionBranch.updatePosition(InstructionBranch.java:179)
> 	at
> org.aspectj.apache.bcel.generic.BranchHandle.updatePosition(BranchHandle.java:92)
> 	at
> org.aspectj.apache.bcel.generic.InstructionList.setPositions(InstructionList.java:905)
>
>
> in your ajcore file.  And I think that is enough information for me to fix
> it.
>
> Andy.
>
> 2008/8/27 Kevin Hoffman 
>>
>> Hi Andy,
>>
>> I tried with the latest development version (version string is Wed Aug
>> 27 2008 at 1:27:57 GMT) with the same results.
>>
>> Here are the new corefiles.
>>
>> http://www.cs.purdue.edu/homes/kjhoffma/ajcore.20080827.160703.630.txt
>> http://www.cs.purdue.edu/homes/kjhoffma/ajcore.20080827.160703.864.txt
>>
>> I'll email you a direct link to the zip that allows you to easily
>> reproduce. Is there indication which method is becoming too large? Let
>> me know what else I can do to help.
>>
>> Thanks,
>> Kevin
>>
>> On Tue, Aug 26, 2008 at 11:37 AM, Andy Clement 
>> wrote:
>> > Hi Kevin,
>> >
>> > I have raised:
>> >
>> > https://bugs.eclipse.org/bugs/show_bug.cgi?id=245274
>> >
>> > to look at this.
>> >
>> > The exception is thrown because the method becomes too large during
>> > weaving
>> > and cannot fit into the max method code size when we come to pack it up
>> > and
>> > write it to disk.  Why is it bigger than previously?  I'm thinking right
>> > now
>> > that it is this:
>> >
>> > https://bugs.eclipse.org/bugs/show_bug.cgi?id=243192
>> >
>> > which I only fixed a week ago.  That fix is in the latest dev builds of
>> > AspectJ (as we get ready for AspectJ 1.6.2) - can you please try it out?
>> > The
>> > dev builds are available at the top of the download page.
>> >
>> > It is possible that weaving can cause a method to become too large - and
>> > we
>> > currently do not have a solution to that (we have open bugs relating to
>> > it),
>> > but if it previously didn't get too big, there is no reason why it
>> > should
>> > now be too big.  If you try it out with a dev build and it still fails,
>> > I'll
>> > probably ask you for the extra materials to recreate it.  If nothing
>> > else
>> > I'll certainly change the exception message from 'Argh!' ;)
>> >
>> > cheers,
>> > Andy.
>> >
>> > 2008/8/25 Kevin Hoffman 
>> >>
>> >> Hello,
>> >>
>> >> I'm using the aj5 script to perform dynamic weaving on Xalan for Java.
>> >> Things were working fine when we were using AspectJ 1.5. Recently I
>> >> upgraded to version 1.6.1 and recompiled my aspects using the newer
>> >> compiler. The runtime weaving / aspects still work most of the time,
>> >> but I have encountered an important case where AspectJ core-dumps with
>> >> ajcore files when trying to dynamically weave a certain class:
>> >>
>> >> Aug 25, 2008 6:20:52 PM org.aspectj.weaver.tools.Jdk14Trace error
>> >> SEVERE: org/apache/xalan/xslt/Process
>> >> java.lang.IllegalStateException: Argh!
>> >>    at
>> >>
>> >> org.aspectj.apache.bcel.generic.InstructionBranch.updatePosition(InstructionBranch.java:178)
>> >>    at
>> >>
>> >> org.aspectj.apache.bcel.generic.BranchHandle.updatePosition(BranchHandle.java:92)
>> >>    at
>> >>
>> >> org.aspectj.apache.bcel.generic.InstructionList.setPositions(InstructionList.java:905)
>> >>    at
>> >>
>> >> org.aspectj.apache.bcel.generic.InstructionList.setPositions(InstructionList.java:826)
>> >>    at
>> >>
>> >> org.aspectj.apache.bcel.generic.InstructionList.getByteCode(InstructionList.java:931)
>> >>    at
>> >> org.aspectj.apache.bcel.generic.MethodGen.getMethod(MethodGen.java:699)
>> >>    ...
>> >>
>> >> Process is a class that has a main method. (I'm able to weave other
>> >> classes not from Xalan that have main methods just fine.) I have tried
>> >> compiling Xalan with Java 1.4 or 1.5 but it doesn't affect the result.
>> >> I haven't tried compiling with 1.6.
>> >>
>> >> I still have the JAR of my aspects that were compiled with AspectJ
>> >> 1.5. Using the JAR of aspects compiled with AspectJ 1.5 with the
>> >> AspectJ 1.6 runtime weaver produces the same error. Using the AspectJ
>> >> 1.5 runtime weaver with the aspects compiled with AspectJ 1.5 still
>> >> works fine. (and using the AspectJ 1.5 runtime with the aspects
>> >> compiled with AspectJ 1.6 isn't possible...)
>> >>
>> >> Here are links to the ajcore files (two ajcore files generated per
>> >> attempt at weaving the class):
>> >>
>> >> http://www.cs.purdue.edu/homes/kjhoffma/ajcore.20080825.182052.910.txt
>> >> http://www.cs.purdue.edu/homes/kjhoffma/ajcore.20080825.182053.153.txt
>> >>
>> >> The Java class file that it is having trouble weaving is also
>> >> available:
>> >>
>> >> http://www.cs.purdue.edu/homes/kjhoffma/Process.class
>> >>
>> >> I can provide information to download the full package with JARs and
>> >> scripts to reproduce off-list. Let me know what else I can gather to
>> >> help get this issue fixed.
>> >>
>> >> Thanks,
>> >> Kevin
>> >> _______________________________________________
>> >> 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
>> >
>> >
>> _______________________________________________
>> 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
>
>