static weaving and weblogic 10

[Kristof Jozsa]

Hi,

I'm using AspectJ 1.6.5 to static-weave my EJB3 beans with maven before deployment to a Weblogic 10.3.1 server. I wrote a unit test which assures that the aspect has been applied successfully, but after deploying the tested package on WLS appearently the aspect is not called at all.

I even tried to add throwing a new RTE in a before aspect and it gets thrown from the unit test but absolutely nothing happens on WLS... I even decompiled the class file which got deployed in WLS with jad and checked that the source is weaved and it is.. and I see still no runtime effect at all.

Anyone has any idea what might go on here?

thanks,
Kristof


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

[Andrew Eisenberg]

I can't say definitively what is going on, but it sounds like there might be another, unwoven, version of the jar on the classpath somewhere.

Another possibility is that you are running with load time weaving enabled as well.  And your woven class is being rewoven (or unwoven) before being run.  But, this seems unlikely as well...

I'd suggest put some println statements in the class that is being woven (somewhere close to where you expect the advice to run) and see if the statements are printed out as expected.

On Wed, Sep 2, 2009 at 5:56 AM, Kristof Jozsa <kristof.jozsa@...> wrote:

Hi,

I'm using AspectJ 1.6.5 to static-weave my EJB3 beans with maven before deployment to a Weblogic 10.3.1 server. I wrote a unit test which assures that the aspect has been applied successfully, but after deploying the tested package on WLS appearently the aspect is not called at all.

I even tried to add throwing a new RTE in a before aspect and it gets thrown from the unit test but absolutely nothing happens on WLS... I even decompiled the class file which got deployed in WLS with jad and checked that the source is weaved and it is.. and I see still no runtime effect at all.

Anyone has any idea what might go on here?

thanks,
Kristof


_______________________________________________
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

[Kristof Jozsa]

You were right, it was a user error on my side. The aspect and the unittest were fine but the ejb tested live on the server did not get weaved indeed.

Your hint helped a lot, I thought its a conceptual problem.

Thanks,
Kristof

--
This mail was sent by an Android.

On Sep 2, 2009 6:07 PM, "Andrew Eisenberg" <andrew@...> wrote:

I can't say definitively what is going on, but it sounds like there might be another, unwoven, version of the jar on the classpath somewhere.

Another possibility is that you are running with load time weaving enabled as well.  And your woven class is being rewoven (or unwoven) before being run.  But, this seems unlikely as well...

I'd suggest put some println statements in the class that is being woven (somewhere close to where you expect the advice to run) and see if the statements are printed out as expected.

On Wed, Sep 2, 2009 at 5:56 AM, Kristof Jozsa <kristof.jozsa@...> wrote:

> > Hi, > > I'm using AspectJ 1.6.5 to static-weave my EJB3 beans with maven before deployment to a ...

_______________________________________________
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