There are some problems in the IBM classloader plugin approach; it
doesn’t tell the plugin what loader is being used and it also doesn’t set the
context loader correctly in some cases. I’ve seen this result in defining classes
in the wrong loader, leading to NoClassDefFoundErrors. It is also possible this
issue is leading to the lockup behavior you are seeing.
I’d suggest trying the alternative approach of generating a bootstrap
classpath jar that adds a weaving hook to ClassLoader. The Glassbox project has an automated installer
and updated version of the code based on Alex Vasseur’s blog entry and the last
Aspectwerkz release.
Ron
From:
aspectj-users-bounces@xxxxxxxxxxx [mailto:aspectj-users-bounces@xxxxxxxxxxx] On
Behalf Of Hermod Opstvedt
Sent: Sunday, December 09, 2007 7:22 AM
To: aspectj-users@xxxxxxxxxxx
Subject: [aspectj-users] AspectJ loadtime weaving on WebSphere 5
Hi
I have had
waeving on WAS 5.0.2 working with the Ron's WasWeavingPlugin, but for some
reason it stopped working (I do not know that I have doen anything to it).
WebSphere hangs on startup during initialization of the Admin application (Last
entry in log is admin: init). If I take out the Admin application it does start
however. As far as I have been able to track down looking at the logs, it seems
to be connected with Tiles. I have seen others having the same situation, but
have not seen ant entry stating that they have solved the issue.
So: Anybody
have this working?
Hermod
