Hi Hermod,
Yes Glassbox does have a few 1.4 runtime dependencies in it. But
you could still use the packaged installation script it includes on an older VM.
It generates output like this:
JAVA_OPTS="$JAVA_OPTS
-Xbootclasspath/p:$JAVA_14_HOME/java14Adapter.jar
-Xbootclasspath/a:$JAVA_14_HOME/createJavaAdapter.jar:$JAVA_14_HOME/aspectj14Adapter.jar:C:\devel\tool\apache
software foundation\apache-tomcat-4.1.34-LE-jdk14/common/lib/aspectjweaver.jar
-Xmx509m
-Daspectwerkz.classloader.preprocessor=org.aspectj.ext.ltw13.ClassPreProcessorAdapter
…"
Where it ran the command java -jar createJavaAdapter.jar to
produce aspectj14Adapter.jar
From:
aspectj-users-bounces@xxxxxxxxxxx [mailto:aspectj-users-bounces@xxxxxxxxxxx] On
Behalf Of hermod.opstvedt@xxxxxxxxx
Sent: Tuesday, December 11, 2007 3:54 AM
To: aspectj-users@xxxxxxxxxxx
Subject: RE: [aspectj-users] AspectJ loadtime weaving on WebSphere 5
The latest glassbox has 1.4 dependencies:
java.net.URLDecoder.decode(String), java.net.SocketAdress
-----Original Message-----
From: aspectj-users-bounces@xxxxxxxxxxx
[mailto:aspectj-users-bounces@xxxxxxxxxxx] On Behalf Of Ron Bodkin
Sent: Monday, December 10, 2007 9:21 PM
To: hermod@xxxxxxxxxxxx; aspectj-users@xxxxxxxxxxx
Subject: RE: [aspectj-users] AspectJ loadtime weaving on WebSphere 5
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
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
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.
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *