I've been doing a bit of aspectj work in Websphere 5.1 and Websphere 6+ and thought I would offer you all a few of my observations and all of my subsequent confusion.
But before that -- Kudos to Mr. Bodkin. WasWeavingPlugin works wonderfully on all versions of Websphere I've tried. You da man.
And now my observations and questions regarding the source link/instructions for WasWeavingPlugin:
Step 3 instructs us to add the following to Websphere's server.xml:
<systemProperties xmi:id="Property_9927324365996" name="java.rmi.server.codebase" ...
However, I've noticed that Plants By Websphere, the sample web app included with WebSphere, inexplicably throws an exception on order submission when this line was included, but remains perfectly happy without it. Leaving out this line appeared to have no affect on my other load-time weaving endeavors, which consisted primarily of pointcuts on do* methods of the HttpServlet variety, and getConnection() methods of the java JDBC Datasource variety.
Obviously I'm happy not to rock my own boat, but I'm wondering if someone can explain what that line was supposed to accomplish? Should I fear its removal? Am I asking for trouble down the road?
Ok, one last thing!
Step 4 instructs us to remove the 1.2 aspectjrt.jar included with WebSphere 6.0.2 (not 6.0 as the page suggests) and replace it with a good and nifty better one. Obviously I'm doing loadtime weaving, and I do use aspectj 1.5 at the moment (upgrade is pending). As the instructions suggest, my 1.5 aspectjweaver.jar is plugged right into the Websphere classpath. However, even if I *don't* touch the antique runtime library, my aspects all seem to work fine. Am I just lucky, or is aspectjweaver.jar blocking out the decrepit old 1.2 version? Is this step necessary, or was it listed more as a precaution? Some Advice here would be appreciated (and yes, a pun was most certainly intended).
Thanks for any response!
- Bo Zimmerman
