[aspectwerkz-dev] About using AspectWerkz in Weblogic
xudong <xudong-GEt6dTWxgudWk0Htik3J/[email protected]> Fri, 26 Nov 2004 10:19:11 +0800
| Newsgroups | gmane.comp.java.coconut.user,gmane.comp.java.aspectwerkz.devel |
|---|---|
| Organization | aristoga |
| Message-ID | <41A6929F.3060204__22237.1587915861$1101435605$gmane$org@aristoga.com> |
hi Background: ----------- I tried to weave some classes belong to a weblogic webapp. Yes, the simplest way is to deploy aop.xml and related aop classes at webapp level. But I tried to weave those classes by defining a JVM wide aop.xml. I thought it would be very OK. But I am wrong. Analysis: ---------- During the startup process of Weblogic, at least two JVMs will start up. According to the documents of AspectWerkz, there are three types of deployment model for aspects: perJVM, perClass, perInstance. So I think what I did just affect one of these two JVMs. But unfortunately, the target classes are running in the other JVM. More unfortunately, I cannot do anything to the latter JVM, because it is invoked by weblogic. Questions: ---------- - There is any way to find which classes are running in one specific JVM? - There is any way to define aspects across over all JVMs? Best wishes, xudong